Menú
Start here to build code against a clear success criterion — test-first, incremental, one work unit per fork.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.
Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.
Start here to ship built-and-tested code to its target safely — release steps, rollout, smoke checks, and rollback.
Start here to settle how a non-trivial change will be built — interfaces, contracts, file-level structure, and trade-offs.
Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
Start here to document what shipped — READMEs, API docs, ADRs, and usage — once a feature lands or an interface changes.
| name | implementation |
| description | Start here to build code against a clear success criterion — test-first, incremental, one work unit per fork. |
| context | fork |
| agent | engineer |
Build it, test-first. Write the failing test that defines the behavior, then write the code that makes it pass. Deliver one step at a time, keeping the tree green at every step.
Make the smallest diff that meets the requirement. Touch only what the task demands, and respect the out_of_scope fence.
tester adds adversarial tests later, never instead of these.