Find your next open-source project

Search by name, purpose, or keyword — or paste a GitHub repository URL
All skills

domain-modeling

Build and sharpen a project's domain model by writing GLOSSARY.md terms and ADRs as decisions crystallize.

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.