agentleFS
Sign inStart free
assisjpassisjp/specflow/skills/engineering/domain-modeling/SKILL.md

domain-modeling

Skill17 starsChanged 3 months agoMITView on GitHub

Actively build and sharpen a project's domain model as you design — challenge fuzzy terms, invent edge-case scenarios, and write the glossary and architectural decisions down the moment they crystallise. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill (such as grill in docs mode) needs to maintain the domain model. This is the active discipline of *changing* the model — merely reading CONTEXT.md for vocabulary is a one-line habit, not this skill.

We split this skill into the rules it gives an agent

8 rules. 3 are common, 1 is distinctive, and 4 are very specific to this project.

  • 3

    Common

    Most of the 183 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If a CONTEXT-MAP.md exists at the root, the repo has multiple bounded contexts, and the map points to where each one lives:

    line 24
  2. Very specific:

    Create files lazily — only when you have something to write.

    line 39
  3. Very specific:

    When the user uses a term that conflicts with the language already in CONTEXT.md, call it out immediately.

    line 45
  4. Common:

    When the user uses a vague or overloaded term, propose a precise canonical one.

    line 49
  5. Distinctive:

    When domain relationships are on the table, invent specific scenarios that probe the edges and force precision about where one concept ends …

    line 53
  6. Common:

    When the user states how something works, check whether the code agrees.

    line 57
  7. Very specific:

    When a term resolves, write it to CONTEXT.md right there — do not batch.

    line 61
  8. Common:

    If any of the three is missing, skip it.

    line 71

“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

Domain Modeling

Actively build and sharpen the project's domain model as you design. This is the active discipline — challenging terms, inventing edge-case scenarios, and writing the glossary and decisions down the moment they crystallise. Use it when you are changing the model, not just consuming it.

File structure

Most repos have a single context:

/
├── CONTEXT.md
├── docs/
│   └── adr/
│       ├── 0001-event-sourced-orders.md
│       └── 0002-postgres-for-write-model.md
└── src/

If a CONTEXT-MAP.md exists at the root, the repo has multiple bounded contexts, and the map points to where each one lives:

/
├── CONTEXT-MAP.md
├── docs/adr/                         ← system-wide decisions
├── src/
│   ├── ordering/
│   │   ├── CONTEXT.md
│   │   └── docs/adr/                 ← context-specific decisions
│   └── billing/
│       ├── CONTEXT.md
│       └── docs/adr/

Create files lazily — only when you have something to write. No CONTEXT.md yet? Create it when the first term resolves. No docs/adr/? Create it when the first ADR is warranted.

During the session

Challenge against the glossary

When the user uses a term that conflicts with the language already in CONTEXT.md, call it out immediately. "Your glossary defines 'cancellation' as X, but you seem to mean Y — which is it?"

Sharpen fuzzy language

When the user uses a vague or overloaded term, propose a precise canonical one. "You said 'account' — do you mean the Customer or the User? Those are different things."

Stress-test with concrete scenarios

When domain relationships are on the table, invent specific scenarios that probe the edges and force precision about where one concept ends and the next begins.

Cross-reference with the code

When the user states how something works, check whether the code agrees. On a contradiction, surface it: "Your code cancels whole Orders, but you just said partial cancellation is possible — which is right?"

Update CONTEXT.md inline

When a term resolves, write it to CONTEXT.md right there — do not batch. CONTEXT.md is a glossary and nothing else: no implementation details, no spec, no scratch pad, no decisions. Use the format in CONTEXT-FORMAT.md.

Offer ADRs sparingly

Offer an ADR only when all three hold:

  1. Hard to reverse — changing your mind later carries real cost.
  2. Surprising without context — a future reader will wonder "why did they do it this way?"
  3. The result of a real trade-off — there were genuine alternatives and one was chosen for specific reasons.

If any of the three is missing, skip it. Use the format in ADR-FORMAT.md.

Download now (ZIP)

  • Other versions195 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 158

    1. mattpocock/skills★ 309k40% same
    2. QuivrHQ/quivr★ 40k49% same
    3. windmill-labs/windmill★ 18k43% same
    4. GreyDGL/PentestGPT★ 16k52% same
    5. formbricks/formbricks★ 13k40% same
    6. ArcReel/ArcReel★ 6k40% same
    7. vinvcn/mattpocock-skills-zh-CN★ 5.5k24% same
    8. withcoral/coral★ 4.9k40% same
    9. bestofjs/bestofjs★ 3.1k52% same
    10. CelestoAI/SmolVM★ 1.1k47% same

    148 more not listed

    Wrote their own version · 37

    1. rohitg00/pro-workflow★ 2.9ksame name
    2. stevesolun/ctx★ 583same name
    3. devcxl/mattpocock-skills-zh★ 522same name
    4. Mathews-Tom/armory★ 340same name
    5. proflead/codex-skills-library★ 153same name
    6. etr/groundwork★ 44same name
    7. nimadorostkar/Claude-Skills-collection★ 33same name
    8. oribarilan/97★ 25same name
    9. helderberto/agent-skills★ 19same name
    10. garrettw/php-arch-skills★ 13same name

    27 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use decision-mapping, setup-ts-deep-modules and 10 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.
    • 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

    • 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 38 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 57 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 128 projects that use this

    • RoentekSkill

      loop-me

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

      Also in 51 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 55 projects that use this

    • +1 more from Lesani
  • In this repository14 other files it gives its agents.

Does it work?

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

Reviews can't be read right now.

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