All skills
domain-modeling
Build and sharpen a project's domain model by writing GLOSSARY.md terms and ADRs as decisions crystallize.
- Part of mattpocock/skills
- 1M installs
- Developer Tools · Code review
When to use it
You're designing a feature and keep using overloaded terms like "account" or "cancellation" without a shared definition, and no glossary exists yet.
For example
You say
Use domain-modeling on our ordering service. We keep saying "account" for both the Customer and the User, and we just decided to allow partial order cancellation. Help me pin down the terms and record the decision.
You get
- Updated GLOSSARY.md entries
- New ADR for partial cancellation
- Flagged code/term conflicts
How it works
- Challenges terms that conflict with the existing glossary and proposes precise canonical names for fuzzy language.
- Checks stated behavior against the code and surfaces contradictions before writing anything down.
- Only suggests an ADR when a decision is hard to reverse, surprising, and a real trade-off.
More Code review skills
See all- requesting-code-review289kRequests a code review after tasks or major features to verify the work meets requirements.
- receiving-code-review247kChecks code review feedback for technical soundness before acting on it, instead of agreeing blindly.
- golang-security45.1kReviews Go code for injection, crypto, SSRF and secrets issues, and suggests threat modeling and fuzzing.
- golang-safety43kChecks Go code for nil panics, integer overflow, slice aliasing and other accidental bugs.
Also in this pack
- grill-me1.6MInterviews you relentlessly to sharpen a plan or design before you commit to it.
- grill-with-docs1.4MInterviews you hard about a plan while also writing decision records and a glossary as you go.
- improve-codebase-architecture1.3MScans a codebase for structural improvement opportunities, shows them in an HTML report, then digs into your pick.
- tdd1.3MBuilds features and fixes bugs test-first, writing failing tests before code and refactoring after.