Menu
Use when establishing shared vocabulary: resolve terminology early, one name per concept, vocab files as record.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | shared-dao |
| type | principle |
| description | Use when establishing shared vocabulary: resolve terminology early, one name per concept, vocab files as record. |
| model-invocable | true |
Load /qi-layer if it isn't already loaded.
Shared vocabulary is a structural boundary between human intent and action. Ambiguous, overloaded, drifting, or misleading terms corrupt reasoning early and spread confusion through everything downstream. Treat vocabulary problems as design problems.
Scrutinize important terms aggressively. Reuse existing names when they already fit the concept. Converge on one name per concept and one concept per name as quickly as the evidence allows.
Resolve terminology early:
Before defining new terms, check what already exists: vocab files, KB pages, code, prior decisions. A term defined elsewhere under a different name is a conflict, not a new concept.
When terminology conflicts with existing usage and you cannot resolve it, flag explicitly rather than carrying two competing names forward.
Clear vocabulary compounds through every downstream artifact. Resolve terminology while the meaning is still easy to sharpen.
Use when grilling should be grounded primarily in project artifacts. Loads `/grill`, checks project vocabulary and prior decisions first, and spawns bounded explorers when the answer should come from docs.
Load for large human-facing outputs: reports, docs, multi-section explanations, artifacts. Choose the right form for each beat (prose, diagram, table, mockup) and put the answer first, depth behind it. If the medium allows, use progressive disclosure.
Use when deciding where knowledge goes or reading/writing durable docs: AGENTS.md, .context/, KB, docs/, and work directories.
Anchor work in a work item: artifacts on disk, not in context.
Investigate and engage concurrently: don't block on evidence before surfacing your read.
Use when exploring or changing the codebase: read AGENTS.md first, use .context/CONTEXT.md for detail, keep intent docs succinct.
