agentleFS
Sign inStart free
malinskibeniaminmalinskibeniamin/skills/domain-modeling/SKILL.md

domain-modeling

Skill4 starsChanged 11 days agoMITView on GitHub

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

195 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use setup-ts-deep-modules, decision-mapping and 3 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • liufeng1976Skill

    setup-ts-deep-modules

    Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.

    Also in 43 projects that use this

  • FabienDehopreSkill

    decision-mapping

    Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.

    Also in 8 projects that use this

  • RoentekSkill

    loop-me

    Grill me about specs for the workflows I want to build, within this workspace.

    Also in 56 projects that use this

  • ryotaroh180105Skill

    claude-handoff

    Hand the current conversation off to a fresh background agent that picks up the work immediately.

    Also in 42 projects that use this

  • simo97Skill

    migrate-to-shoehorn

    Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.

    Also in 55 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 183 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When changing interfaces, types or shared state, read the Poteto adaptation.

    line 6
  2. Very specific:

    Use root GLOSSARY.md and docs/adr/ for one context.

    line 12
  3. Very specific:

    When user language conflicts with GLOSSARY.md, quote the mismatch and ask which meaning wins.

    line 18
  4. Distinctive:

    Check stated behavior against code.

    line 30

“Common” is measured: kept by at least 6 in 10 of the 183 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

When changing interfaces, types or shared state, read the Poteto adaptation.

Actively challenge, resolve, and record domain terms/decisions while designing. Merely reading GLOSSARY.md is not domain modeling.

Files

Use root GLOSSARY.md and docs/adr/ for one context. If root GLOSSARY-MAP.md exists, follow it to context-local GLOSSARY.md and ADRs; system-wide ADRs stay under root docs. Create files only when the first real term/decision exists.

During the session

Challenge the glossary

When user language conflicts with GLOSSARY.md, quote the mismatch and ask which meaning wins.

Sharpen language

Replace vague/overloaded words with a proposed canonical term, distinguishing nearby concepts explicitly.

Test scenarios

Probe relationships and boundaries with concrete edge cases until terms are precise.

Cross-reference code

Check stated behavior against code; surface contradictions for resolution.

Update GLOSSARY.md inline

Record resolved terms immediately using GLOSSARY-FORMAT.md. Do not batch. GLOSSARY.md is a glossary only: no implementation detail, spec, scratch notes, or implementation decisions.

Offer ADRs sparingly

Offer an ADR only when all hold:

  1. Hard to reverse: later change is costly.
  2. Surprising without context: a future reader would ask why.
  3. Real trade-off: genuine alternatives were rejected for reasons.

Otherwise skip. Use ADR-FORMAT.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free