Skip to content

leek/agent-skills / skills/domain-modeling

domain-modeling

Verified

Build and sharpen a project's domain model: its GLOSSARY.md and ADRs. Use when pinning down domain terminology or a ubiquitous language, challenging fuzzy terms, recording an architectural decision, or when another skill needs the domain model maintained.

FileKindSize
SKILL.mdskill md5.3 KB
agents/openai.yamlconfig179 B
references/adr-format.mdmarkdown3.0 KB
references/glossary-format.mdmarkdown2.5 KB

references/glossary-format.md

View on GitHub
# GLOSSARY.md Format

## Structure

```md
# {Context Name}

{One or two sentence description of what this context is and why it exists.}

## Language

**Order**:
{A one or two sentence description of the term}
_Avoid_: Purchase, transaction

**Invoice**:
A request for payment sent to a customer after delivery.
_Avoid_: Bill, payment request

**Customer**:
A person or organization that places orders.
_Avoid_: Client, buyer, account
```

## Rules

- **Be opinionated.** When multiple words exist for the same concept, pick the best one and list the others under `_Avoid_`.
- **Keep definitions tight.** One or two sentences max. Define what it IS, not what it does.
- **Only include terms specific to this project's context.** General programming and framework concepts (jobs, middleware, caching, error types) don't belong even if the project uses them extensively. Before adding a term, ask: is this a concept unique to this context, or a general concept? Only the former belongs.
- **Group terms under subheadings** when natural clusters emerge. If all terms belong to a single cohesive area, a flat list is fine.
- **The canonical term should be the code's term.** In a Laravel repo the term and the Eloquent model/enum name should agree; when they can't yet (a rename is pending), note the code's current name in the definition so readers can navigate.

## Single vs multi-context repos

**Single context (most repos):** One `GLOSSARY.md` at the repo root.

**Multiple contexts:** A `GLOSSARY-MAP.md` at the repo root lists the contexts, where they live, and how they relate:

```md
# Context Map

## Contexts

- [Ordering](./app/Domain/Ordering/GLOSSARY.md), receives and tracks customer orders
- [Billing](./app/Domain/Billing/GLOSSARY.md), generates invoices and processes payments
- [Fulfillment](./app/Domain/Fulfillment/GLOSSARY.md), manages warehouse picking and shipping

## Relationships

- **Ordering → Fulfillment**: Ordering fires `OrderPlaced` events; Fulfillment listens to start picking
- **Fulfillment → Billing**: Fulfillment fires `ShipmentDispatched`; Billing listens to generate invoices
- **Ordering ↔ Billing**: shared value objects for `CustomerId` and `Money`
```

The skill infers which structure applies:

- If `GLOSSARY-MAP.md` exists, read it to find contexts
- If only a root `GLOSSARY.md` exists, single context
- If neither exists, create a root `GLOSSARY.md` lazily when the first term is resolved

When multiple contexts exist, infer which one the current topic relates to. If unclear, ask.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall