All skills
Principles load automatically when the agent touches code they govern. Workflows and profiles are invoked in the AI chat with a slash command.
Principles
| Skill |
What it does |
api-contracts |
Design and evolve the contracts that cross a service boundary — synchronous APIs and published events — specification first. |
api-protocols |
Choose the right protocol for an interface and use it the way it was designed to be used. |
clean-architecture |
Place code in the right layer and keep dependencies pointing inward, inside a single service. |
collaborative-judgment |
Surface genuine architectural trade-offs as structured options with consequences instead of silently picking one. |
config-and-dependencies |
Keep a service's configuration and its dependency graph under control. |
contract-testing |
Prove that a consumer and a provider still agree, without deploying them together. |
cqrs-and-consistency |
Decide how reads are served, how far they may lag behind writes, and who owns each piece of data. |
data-access |
Write the persistence layer so it is correct under concurrency and fast under load. |
design-first |
Facilitate design before code through progressive disclosure: climb from context to components to interactions to contracts, asking questions and stopping for approval at each level instead of emitting a finished design. |
domain-modelling |
Design the classes that carry business meaning, using tactical domain-driven design. |
idempotency-and-immutability |
Make operations safe to repeat and data safe to share. |
infrastructure-adapters |
Write the adapter layer that connects a service to everything outside it. |
resilience-patterns |
Make a service behave predictably when its dependencies are slow, failing, or duplicating work. |
secure-service |
Apply security controls at every trust boundary of a service. |
service-boundaries |
Decide where a service ends and the next one begins, using domain-driven strategic design. |
test-strategy |
Choose the right test level for each behaviour and write tests that fail only for real reasons. |
Workflows
| Skill |
What it does |
/design-service |
Run a design session before code exists, producing an approved blueprint the implementation workflow can build from. |
/implement-service |
Turn an approved design into working code and tests, built inside-out one layer at a time, with every principle's checklist run before anything is presented. |
/refactor-safely |
Change the structure of existing code without changing its behaviour, in verified steps small enough to abandon. |
/review-service |
Audit service code against every microservices principle and report severity-ranked findings, each anchored to a file, a line, and the rule it breaks. |
Profiles
| Skill |
What it does |
/stack-profile |
Record this project's technology choices once, so every other skill speaks the team's actual language instead of generic pattern names. |