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

domain-modeling

Skill1 starsChanged 16 days agoMITView on GitHub

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

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

Adopted by

Most recently taken up by

Used with

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

6 rules. 1 is common, 5 are distinctive, and 0 are very specific to this project.

  • 1

    Common

    Most of the 183 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before reading or writing terms, follow glossary paths for configured, mapped, legacy, and new layouts.

    line 13
  2. Distinctive:

    Check behavioral claims against the code.

    line 23
  3. Distinctive:

    Update the resolved glossary as each term is settled, using GLOSSARY-FORMAT.md for entries and layout examples.

    line 28
  4. Distinctive:

    Keep definitions about the domain.

    line 30
  5. Common:

    Only offer to create an ADR when all three are true:

    line 36
  6. Distinctive:

    If any criterion is missing, skip the ADR.

    line 42

“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

Sharpen the domain model as terms and decisions arise. Reading an existing glossary for vocabulary alone does not invoke this workflow.

Resolve the vocabulary

Before reading or writing terms, follow glossary paths for configured, mapped, legacy, and new layouts. Preserve the project's paths and one vocabulary source per context.

  • Surface conflicts with the existing glossary immediately and ask which meaning is intended before recording a resolution.
  • Replace vague or overloaded language with precise canonical terms. Distinguish concepts such as Customer and User rather than treating both as "account."
  • Probe domain relationships with concrete edge-case scenarios that clarify boundaries between concepts.
  • Check behavioral claims against the code. Surface contradictions, such as whole-order versus item-level cancellation, and ask which behavior is intended.

Record resolved terms

Update the resolved glossary as each term is settled, using GLOSSARY-FORMAT.md for entries and layout examples. Keep definitions about the domain; implementation choices, specifications, and working notes belong elsewhere. Create a glossary only when the first resolved term needs recording, and an ADR directory only when there is a decision to record.

Offer ADRs sparingly

Only offer to create an ADR when all three are true:

  1. Hard to reverse: the cost of changing your mind later is meaningful
  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 you picked one for specific reasons

If any criterion is missing, skip the ADR. For a qualifying decision, use ADR-FORMAT.md for placement, numbering, and the brief format.

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