api-implementation
Implement API handlers/controllers based on an existing API contract (OpenAPI spec). Generates route handlers, validation, and error handling.
30-implementation — Implementation
12 skills in this category.
cleanup
Remove noise, enforce formatting, and safely rename identifiers. A mixed-mode skill: cosmetic fixes run in Eco, renaming runs in Power.
code-generation
Generate production-ready code from specifications, templates, and domain models. Enforces language idioms, DRY principles, and project conventions.
data-access
Implement data access layers using the Repository pattern. Prevents N+1 queries, manages transactions, and optimizes reads.
error-handling
Standardize error types, logging formats, and error response structures across the project.
feature-shipping
Master workflow for shipping a feature end-to-end. Orchestrates PRD authoring, task decomposition, TDD implementation, code review, and the release pipeline as a single named sequence ending in an audit. Contains no implementation logic.
refactoring
Safely restructure code while preserving external behavior. Applies proven refactoring patterns with mandatory test verification.
refactoring-suite
Complex refactoring operations with strict test verification. Every refactor follows: Test → Refactor → Test → Revert-on-Fail.
refactoring-workflow
Master workflow for refactoring at four named depth levels — cosmetic, micro, meso, architectural — that compose as a ladder. Always runs chesterton-fence and style-conformance up front; always closes with a characterisation/test safety net, minimal-diff scope checks, and the auditor. Contains no implementation logic; orchestrates only existing category skills.
resilience-patterns
Graceful degradation when external dependencies fail. Circuit breaker state machine, retry with backoff, bulkhead isolation, fallback chains, and timeout management.
responsive-design
Make a web page work on every screen — phone to ultrawide — without text or media ever escaping its container. Invoke whenever building or changing any page/CSS that will be viewed on more than one screen size (i.e. always). Overflow and word-wrap bugs are treated as correctness bugs, not polish.
tdd-workflow
Drive implementation through the Red-Green-Refactor cycle. Write failing tests first, implement minimal code to pass, then refactor.