01
It starts by itself
you start design session. Runs in Claude Code.
- ↻ you start design session
manual: domain modeling session
Your team uses the same words.
Install the Domain Modeling skill and make it a habit: follow https://gethabit.dev/skills/pandoscope/domain-modeling.md
2K installs1 starsMIT licenceSource on GitHub ↗

Domain Modeling
by pandoscope · 2K installs
The skill
Gives each idea in your project one clear name.
Only when you ask.
Fewer mix-ups
Your team uses the same words. Fewer mix-ups and wrong guesses.
↻ Runs by itselfwhen you start a design session
When does it start? How does it check its work? What does it remember?
Stops after ten resolved terms per session, with one lint retry.
Point out when the user's word conflicts with docs/glossary/.
Ask the user to pick a precise term for vague or overloaded words.
Invent edge-case scenarios that force clear concept boundaries.
Compare the user's claims with the code and surface contradictions.
Write the resolved term as its own file, using writing-prose if available.
Offer an ADR through writing-adrs only when its three-part bar is met.
Run uvx disambiguate --lint after editing.
It writes only in its own folder and asks you before anything goes out.
Read both lists. If the left one sounds like you, the Domain Modeling skill helps.
No. The skill keeps it free of implementation details.
No. Terms live as one file each in docs/glossary/.
Copy the prompt at the top into your agent. It installs the skill from pandoscope/skills and sets up the habit. Or run npx skills add pandoscope/skills --skill domain-modeling.
Yes. It is published under MIT. Habit is free too.
Install the Domain Modeling skill and make it a habit: follow https://gethabit.dev/skills/pandoscope/domain-modeling.md
All pandoscope skills →More docs skills →
Works in
Made by pandoscope, published under MIT. Habit links to the original and never changes it. Is this your skill?