agentleFS
wilbeibiwilbeibi/wilbeibi-skills/skills/domain-modeling/SKILL.md

domain-modeling

Skill2 starsChanged 2 months agoMITView on GitHub

Keeps a project's vocabulary and decision records honest by challenging overloaded terms against the code and recording canonical terms and hard-to-reverse decisions where the repo already keeps them. Use when a term, status, or field means two things, when naming a new concept or state, or when editing a glossary, GLOSSARY.md, or ADR. Do NOT use to interview the user about a plan (use grill-me) or to write a design doc.

195 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use setup-ts-deep-modules, decision-mapping and 9 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

  • LesaniSkill

    writing-beats

    Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.

    Also in 62 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

  • AWSSkill

    wizard

    Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.

    Also in 134 projects that use this

  • LesaniSkill

    writing-shape

    Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.

    Also in 60 projects that use this

  • +1 more from Lesani

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 185 edited versions we read keep these.

  • 6

    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:

    Read the repo's agent guide (AGENTS.md, CLAUDE.md) for where docs live.

    line 12
  2. Distinctive:

    Search for an existing glossary and decision record:

    line 13
  3. Very specific:

    Use the home you found, in its format.

    line 19
  4. Distinctive:

    Probe each suspect term: ask what it means to each reader (the code that writes it, each code path that reads it, the user).

    line 25
  5. Very specific:

    Check the code: when someone states how a term behaves, find the path:line that agrees or contradicts, and surface a contradiction at once.

    line 26
  6. Distinctive:

    Ask naming choices as decisions: When the canonical name is the user's call, ask it in a grill-me round.

    line 28
  7. Distinctive:

    Record each term when it resolves: Do not batch them.

    line 29
  8. Distinctive:

    Decisions: only when hard to reverse, surprising without context, and a real tradeoff.

    line 36

“Common” is measured: kept by at least 6 in 10 of the 185 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

domain-modeling

Give each term one meaning, check that meaning against the code, and record it in the repo's existing home.

1. Find the home (REQUIRED)

  1. Read the repo's agent guide (AGENTS.md, CLAUDE.md) for where docs live.
  2. Search for an existing glossary and decision record:
    rg -n -i '^#+ .*(glossary|vocabulary|terminology)' -g '*.md'
    fd -H 'GLOSSARY(-MAP)?\.md|^adr$'
    Numbered decisions in design docs (D1., **D3.**) are a decision record too.
  3. Use the home you found, in its format. Create GLOSSARY.md or docs/adr/ only when none exists: lazily, in the docs location the guide names.

Done when you can name the one place each new term and decision goes.

2. Sharpen the language

  • Probe each suspect term: ask what it means to each reader (the code that writes it, each code path that reads it, the user). Two answers mean two concepts: propose a name for each.
  • Check the code: when someone states how a term behaves, find the path:line that agrees or contradicts, and surface a contradiction at once.
  • Test the boundary with one concrete scenario: "a failed row that later becomes deleted: is failed terminal?"
  • Ask naming choices as decisions. When the canonical name is the user's call, ask it in a grill-me round.
  • Record each term when it resolves. Do not batch them.

Done when every term the current decision uses has one recorded meaning, with its aliases under _Avoid_.

3. Record

  • Terms: GLOSSARY-FORMAT.md for a new glossary. An existing glossary keeps its format.
  • Decisions: only when hard to reverse, surprising without context, and a real tradeoff. Use ADR-FORMAT.md, or the repo's own decision format.
  • A status value is a term: define the one fact it records. If two writers set it for different reasons, it names two concepts.

Notes

  • A glossary holds terms, not specs, status, or plans.
  • Ported from mattpocock/skills (MIT), adapted to this repo's conventions and voice.

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.