/shared-dao
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 -y skills add haowjy/creative-writing-skills --skill shared-dao --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/shared-dao
Context preview
The summary Claude sees to decide when to auto-load this skill.
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/.
SKILL.md
shared-dao.SKILL.mdname: shared-dao
description: >
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/.
Shared Dao
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.
Core Discipline
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:
- rename when the clearer term is available
- define when the concept is real but still blurry
- flag when the author's judgment is required
Where Vocab Lives
Place terms at the lowest common scope where they are shared:
- **Project vocab** (`kb/vocab.md`): terms used across the whole story
- **Domain vocab** (`kb/<domain>/vocab.md`): terms specific to one domain,
such as worldbuilding, characters, factions, or timeline eras
- **Work notes** (`work/...`): provisional vocabulary during story-planning or
drafting, promoted to `kb/` once settled
Each entry includes:
- **Canonical name**: the form agents should use
- **Definition**: one to three sentences. Include boundaries that prevent
likely confusion.
- **Aliases**: names the author, characters, drafts, or older kb pages
actually use
- **Source**: where the usage was established or decided
Discovery
Before defining new terms, check what already exists:
1. Read relevant vocab files. 2. Search `CLAUDE.md`, kb pages, outlines, drafts, and work notes. 3. Spawn focused subagents when the search is broad enough to crowd your context. 4. Check how the author uses the term in conversation and prose.
Mint new terms when they mark a real new concept. Let new vocabulary reflect clear distinctions rather than uncertainty, local convenience, or unexamined drift.
Disambiguation
Ambiguity is the root failure mode. Resolve it before carrying the term forward:
- **Same term, different meanings:** pick one meaning for the canonical
definition, and give the other meaning its own name.
- **Different terms, same meaning:** pick one as canonical, record the others
as aliases.
- **Unclear meaning:** ask the author: "When you say X, what specifically do
you mean? Where are the edges of that meaning?"
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.
Creative Writing Terms to Watch
- Magic, technology, powers, abilities, rituals
- Factions, institutions, places, cultures, eras
- Titles, ranks, honorifics, forms of address
- Relationship labels and social categories
- Character-specific vocabulary, catchphrases, verbal tics
- Genre terms the author uses with a project-specific meaning
- Chapter, arc, POV, and timeline labels
Shared vocabulary is the contract between author intent and agent action. Ambiguity you leave in vocab propagates into drafts, critique, continuity, and KB updates.
Read more
name: shared-dao description: > 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/.
Shared Dao
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.
Core Discipline
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:
- rename when the clearer term is available
- define when the concept is real but still blurry
- flag when the author's judgment is required
Where Vocab Lives
Place terms at the lowest common scope where they are shared:
- **Project vocab** (`kb/vocab.md`): terms used across the whole story
- **Domain vocab** (`kb/<domain>/vocab.md`): terms specific to one domain,
such as worldbuilding, characters, factions, or timeline eras
- **Work notes** (`work/...`): provisional vocabulary during story-planning or
drafting, promoted to `kb/` once settled
Each entry includes:
- **Canonical name**: the form agents should use
- **Definition**: one to three sentences. Include boundaries that prevent
likely confusion.
- **Aliases**: names the author, characters, drafts, or older kb pages
actually use
- **Source**: where the usage was established or decided
Discovery
Before defining new terms, check what already exists:
1. Read relevant vocab files. 2. Search `CLAUDE.md`, kb pages, outlines, drafts, and work notes. 3. Spawn focused subagents when the search is broad enough to crowd your context. 4. Check how the author uses the term in conversation and prose.
Mint new terms when they mark a real new concept. Let new vocabulary reflect clear distinctions rather than uncertainty, local convenience, or unexamined drift.
Disambiguation
Ambiguity is the root failure mode. Resolve it before carrying the term forward:
- **Same term, different meanings:** pick one meaning for the canonical
definition, and give the other meaning its own name.
- **Different terms, same meaning:** pick one as canonical, record the others
as aliases.
- **Unclear meaning:** ask the author: "When you say X, what specifically do
you mean? Where are the edges of that meaning?"
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.
Creative Writing Terms to Watch
- Magic, technology, powers, abilities, rituals
- Factions, institutions, places, cultures, eras
- Titles, ranks, honorifics, forms of address
- Relationship labels and social categories
- Character-specific vocabulary, catchphrases, verbal tics
- Genre terms the author uses with a project-specific meaning
- Chapter, arc, POV, and timeline labels
Shared vocabulary is the contract between author intent and agent action. Ambiguity you leave in vocab propagates into drafts, critique, continuity, and KB updates.
Write novels, short stories, and serial fiction with AI that maintains your voice, tracks your continuity, and gets better the more you use it.
Other skills on creative-writing-skills.
- /character-sim
Speak as a specified character from their current knowledge, voice, and emotional state. Use for skill-only workflows that need in-character conversation, voice discovery, or relationship pressure tests.
Open skill - /creative-research
Load when a story needs factual grounding the writer doesn't have: historical detail, cultural texture, domain accuracy, or how other authors handled similar material. Pass the question and story context; returns a sourced report the writer can draw from.
Open skill - /creative-writing-craft
Craft references for writing fiction well: prose, scenes, style, voice, and genre/page-level technique. Load when a writer, critic, or muse needs how-to-write guidance rather than a production mode.
Open skill - /creative-writing-modes
Creative-writing addendum to /llm-writing. Load when putting prose on the page: draft, revise, bridge, vary, or polish.
Open skill - /creative-writing-muse
Load when no subagents are available and one agent must plan, draft, critique, research, and capture memory by switching stances.
Open skill - /grill-with-docs
Use when challenging a plan — grills the author against documented decisions and sharpens terminology.
Open skill

