Skill Claude CodeCodex
Use before claiming that work is complete, fixed, passing or done — including before committing, opening a pull request or reporting a result. Requires running the checks and quoting their real output instead of asserting success.
Skill Claude CodeCodex
Use before building a feature, product or component when the problem, users or scope are not yet settled — including requests phrased as "build X", "add X" or "we need X" that have not stated who it is for or what breaks without it. Produces a scoped brief, not an implementation.
Skill Claude CodeCodex
Use when designing or reviewing a system, service, migration or cross-component feature — anything where load, failure, data shape, security boundaries or rollout matter. Produces a design with explicit non-functional requirements, capacity assumptions, failure modes, security boundaries, observability and a rollout…