cw/skills/shared-dao/SKILL.md
Shared vocabulary for creative writing projects. Load when establishing canonical story terms, resolving ambiguous names, checking term consistency, or deciding where vocabulary belongs in kb/.
npx skillsauth add haowjy/creative-writing-skills shared-daoInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Shared vocabulary is the contract between the author's intent and agent action. Ambiguous, overloaded, drifting, or misleading terms corrupt drafts early: magic systems get renamed, factions blur together, genre terms mean different things in different prompts, and characters speak with vocabulary the author never intended.
Treat vocabulary problems as story-structure problems. Resolve terminology while the meaning is still easy to sharpen.
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:
Place terms at the lowest common scope where they are shared:
kb/vocab.md): terms used across the whole storykb/<domain>/vocab.md): terms specific to one domain,
such as worldbuilding, characters, factions, or timeline eraswork/...): provisional vocabulary during story-planning or
drafting, promoted to kb/ once settledEach entry includes:
Before defining new terms, check what already exists:
CLAUDE.md, kb pages, outlines, drafts, and work notes.Mint new terms when they mark a real new concept. Let new vocabulary reflect clear distinctions rather than uncertainty, local convenience, or unexamined drift.
Ambiguity is the root failure mode. Resolve it before carrying the term forward:
When terminology conflicts with existing kb or draft usage, resolve the drift when the evidence is clear. When author judgment is needed, flag the conflict explicitly in your report so competing names stay visible.
Shared vocabulary is the contract between author intent and agent action. Ambiguity you leave in vocab propagates into drafts, critique, continuity, and KB updates.
tools
Use when orienting in an unfamiliar area — fans out exploration across structure, knowledge, and history, then synthesizes one orientation map.
development
Load when building a static HTML artifact — single page or multi-page site — to make structured information explorable through layout and navigation.
testing
User-invoked pause before reporting to check intent vs literal completion, surface adjacent wins, and route knowledge capture.
development
Use when exploring or changing the codebase: read AGENTS.md first, use .context/CONTEXT.md for detail, keep intent docs succinct.