agentleFS
mohmaedeslam00116mohmaedeslam00116/waypower/skills/domain-glossary/SKILL.md

domain-glossary

Skill0 starsChanged 53 days agoMITView on GitHub

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

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 5 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 3

    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 contexts — the per-context layout and the rules for inferring which structure …

    line 26
  2. Distinctive:

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

    line 28
  3. Very specific:

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

    line 34
  4. Distinctive:

    When domain relationships are being discussed, stress-test them with specific scenarios.

    line 42
  5. Distinctive:

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

    line 46
  6. Very specific:

    When a term is resolved, update CONTEXT.md right there.

    line 50
  7. Distinctive:

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

    line 56
  8. Distinctive:

    If any of the three is missing, skip the ADR.

    line 62

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

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. (Merely reading CONTEXT.md for vocabulary is not this skill: that's a one-line habit any skill can do. This skill is for when you're changing the model, not just consuming it.)

This skill owns the project's CONTEXT.md. Every other waypower skill writes tests, tickets, specs, and plans in its language.

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 contexts — the per-context layout and the rules for inferring which structure applies live in CONTEXT-FORMAT.md.

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

During the session

Challenge against the glossary

When the user uses a term that conflicts with the existing language 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 vague or overloaded terms, propose a precise canonical term. "You're saying 'account': do you mean the Customer or the User? Those are different things." A rename that doesn't resolve which meaning goes where just moves the confusion — semantics first, rename second.

Discuss concrete scenarios

When domain relationships are being discussed, stress-test them with specific scenarios. Invent scenarios that probe edge cases and force the user to be precise about the boundaries between concepts.

Cross-reference with code

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

Update CONTEXT.md inline

When a term is resolved, update CONTEXT.md right there. Don't batch these up: capture them as they happen. Use the format in CONTEXT-FORMAT.md.

CONTEXT.md should be totally devoid of implementation details. Do not treat CONTEXT.md as a spec, a scratch pad, or a repository for implementation decisions. It is a glossary and nothing else.

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 of the three is missing, skip the ADR. A directory full of trivial ADRs teaches readers to ignore all of them. Use the format in ADR-FORMAT.md.

In waypower

  • seam-driven-tdd, tracer-plan, and design-interview write their tests, tickets, and specs in this glossary's language.
  • Terms resolved inside any other skill's session are captured inline here — the moment they crystallise, not batched at the end.
  • A claim that the glossary or an ADR set is complete goes through completion-gate, like any completion claim.

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.