Windsurf rules

1---
2name: define-language
3model: sonnet
4description: "Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to specs/UBIQUITOUS_LANGUAGE_LATEST.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions \"domain model\" or \"DDD\"."
5---
6 
7# Define Language
8 
9Extract and formalize domain terminology from the current conversation into a consistent glossary, saved to `specs/UBIQUITOUS_LANGUAGE_LATEST.md`.
10 
11**Distinct from `model-domain` and `deepen-architecture`:** Use this skill to produce a canonical glossary of terms (words and definitions). Use `model-domain` to stress-test a plan through an interview that resolves domain model decisions. Use `deepen-architecture` to find module-level refactoring opportunities in the codebase.
12 
13> **HARD GATE** — Ubiquitous language is NOT optional. Every term in the domain that could be misunderstood must be glossed. Ambiguity = rework.
14 
15## Process
16 
171. **Scan the conversation** for domain-relevant nouns, verbs, and concepts
182. **Identify problems**:
19   - Same word used for different concepts (ambiguity)
20   - Different words used for the same concept (synonyms)
21   - Vague or overloaded terms
223. **Propose a canonical glossary** with opinionated term choices
234. **Write to `specs/UBIQUITOUS_LANGUAGE_LATEST.md`** in the working directory using the format below
245. **Output a summary** inline in the conversation
25 
26## Output Format
27 
28Write a `specs/UBIQUITOUS_LANGUAGE_LATEST.md` file with this structure:
29 
30```md
31# Ubiquitous Language
32 
33## Order lifecycle
34 
35| Term        | Definition                                              | Aliases to avoid      |
36| ----------- | ------------------------------------------------------- | --------------------- |
37| **Order**   | A customer's request to purchase one or more items      | Purchase, transaction |
38| **Invoice** | A request for payment sent to a customer after delivery | Bill, payment request |
39 
40## People
41 
42| Term         | Definition                                  | Aliases to avoid       |
43| ------------ | ------------------------------------------- | ---------------------- |
44| **Customer** | A person or organization that places orders | Client, buyer, account |
45| **User**     | An authentication identity in the system    | Login, account         |
46 
47## Relationships
48 
49- An **Invoice** belongs to exactly one **Customer**
50- An **Order** produces one or more **Invoices**
51 
52## Example dialogue
53 
54> **Dev:** "When a **Customer** places an **Order**, do we create the **Invoice** immediately?"
55> **Domain expert:** "No — an **Invoice** is only generated once a **Fulfillment** is confirmed."
56 
57## Flagged ambiguities
58 
59- "account" was used to mean both **Customer** and **User** — these are distinct concepts.
60```
61 
62## Rules
63 
64- **Be opinionated.** When multiple words exist for the same concept, pick the best one and list the others as aliases to avoid.
65- **Flag conflicts explicitly.** If a term is used ambiguously, call it out in "Flagged ambiguities" with a clear recommendation.
66- **Only include terms relevant for domain experts.** Skip names of modules or classes unless they have domain meaning.
67- **Keep definitions tight.** One sentence max. Define what it IS, not what it does.
68- **Show relationships.** Use bold term names and express cardinality where obvious.
69- **Group terms into multiple tables** when natural clusters emerge. One table is fine if terms are cohesive.
70- **Write an example dialogue.** 3–5 exchanges between a dev and domain expert showing terms used precisely.
71 
72## Re-running
73 
74When invoked again in the same conversation:
75 
761. Read the existing `specs/UBIQUITOUS_LANGUAGE_LATEST.md`
772. Incorporate any new terms from subsequent discussion
783. Update definitions if understanding has evolved
794. Re-flag any new ambiguities
805. Rewrite the example dialogue to incorporate new terms
81