jupes/agent-forge-harness / .agents/skills/ubiquitous-language
ubiquitous-language
VerifiedExtract or refine a domain glossary from conversation and existing terminology. Use for canonical terms, aliases, and ambiguous domain language.
ubiquitous-language
Extract domain terminology from the current conversation and turn it into a concise, shared glossary.
Process
- Scan the current conversation for domain nouns, verbs, lifecycle states, roles, policies, and events.
- Exclude generic programming terms unless they carry domain meaning in this context.
- Identify terminology problems:
- One word used for multiple concepts.
- Multiple words used for the same concept.
- Vague, overloaded, or implementation-shaped names that hide the domain idea.
- Choose canonical terms. Be opinionated, but preserve important aliases as "aliases to avoid" or "also called" notes.
- Group terms by natural domain area, actor, lifecycle, or process.
- Describe relationships between canonical terms, including cardinality when it is clear.
- Include example dialogue that shows a developer and domain expert using the terms precisely.
- Flag remaining ambiguities with a recommendation or a question for the user.
Persistence
Default to inline output in the conversation. Do not create a file unless the user asks for one or asks for durable repo knowledge.
When durable knowledge is requested:
- Use the explicit target file or location the user names.
- Prefer
bd rememberfor durable agent knowledge when that is the intended persistence mechanism. - Prefer existing
knowledge/conventions for repo-level domain knowledge. - Do not create
MEMORY.md, task-list markdown files, or unrequested permanent documentation.
Output format
Return a glossary in this shape:
# Ubiquitous Language
## <Domain Area>
| Term | Definition | Aliases to avoid |
|------|------------|------------------|
| **Canonical Term** | One-sentence definition of what the concept is. | Old name, vague synonym |
## Relationships
- A **Canonical Term** belongs to exactly one **Related Term**.
- A **Process** may produce one or more **Events**.
## Example dialogue
> **Dev:** "When does a **Canonical Term** become a **Related Term**?"
>
> **Domain expert:** "Only after the **Policy** accepts it. Before that, it is still a **Draft Term**."
## Flagged ambiguities
- "account" was used for both **Customer** and **User**. Use **Customer** for the buyer relationship and **User** for authentication identity.
Canonicalization rules
- Keep definitions tight: one sentence, focused on what the concept is.
- Prefer domain language over class, module, endpoint, or UI labels.
- Use singular nouns for entities and clear verb phrases for domain actions.
- Preserve useful synonyms only as aliases; do not let them compete with the canonical term.
- Call out unresolved ambiguity instead of silently choosing when evidence is weak.
- Avoid inventing terms that are not grounded in the conversation unless clearly labeled as proposals.
Re-running
When invoked again in the same conversation, update the glossary rather than starting over:
- Reuse the previous inline glossary or the explicitly requested durable target.
- Add new terms from subsequent discussion.
- Revise definitions when the domain understanding has changed.
- Re-check aliases, overloaded terms, and ambiguous phrases.
- Refresh relationships and example dialogue so they include the latest canonical terms.
Completion
Definitions, aliases, and unresolved meanings are explicit; relationships are grounded in supplied evidence.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |