sdlc

Design specialist — produces precise technical design covering interfaces, contracts, file structure, and trade-offs. Use to settle how a non-trivial change will be built.

Implementation specialist — builds production code test-first with incremental delivery. Use when code must be written, a feature built, or a bug fixed.

Graphic designer — designs and verifies the user-facing surface: layout, visual hierarchy, composition, states, and accessibility. Use for any UI/visual work, and to confirm a rendered change actually looks right.

Maintenance specialist — removes dead code, simplifies, and reduces complexity without changing behavior. Use for cleanup and refactors.

Requirements specialist — interrogates and falsifies requirements relentlessly, turning a vague request into a clear, scoped spec. Use when a request is ambiguous, high-blast-radius, or hard to reverse.

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.

Remove AI-generated code slop and clean up code style