Product Critic / Acrazie

Challenge the fit between an existing product's uses and its implementation, not its age. Keeping the current solution can be the best outcome. A newer technology is not evidence of better performance, lower complexity, or greater user value.

Project loading boundary

Published-library defaults remain model-invocable within the requested task. An explicit project kit or stricter current instruction takes precedence: propose this skill from available metadata and wait for the user's explicit command before reading its instructions. Apply the same gate to each dependency before reading or dispatching its instructions. One invocation does not activate the chain. Use $skill-name in Codex or /skill-name in Claude Code; do not silently read a missing or unactivated dependency as a workaround. These gates are not filesystem access controls and do not prove live host behavior. Global homonyms may remain a blocker. Loading approval never grants execution, installation, spawning or shipping permission. Under ordinary library defaults, retain scoped implicit handoffs.