shared-dao
Skill2 starsChanged 25 days agoApache-2.0View on GitHub
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/.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Abdullokh-N/proza-rutheir own version, first seen Aug 27, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Abdullokh-N/proza-ru★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository33 other files it gives its agents.
- character-simSkill
- cold-readSkill
- creative-researchSkill
- creative-writing-craftSkill
- creative-writing-modesSkill
- creative-writing-museSkill
- demolitionSkill
- exportSkill
- gatesSkill
- grill-with-docsSkill
- information-hierarchySkill
- intent-modelingSkill
- kb-integritySkill
- kb-managementSkill
- knowledge-layersSkill
- llm-writingSkill
- md-validationSkill
- project-setupSkill
- qi-layerSkill
- reader-simSkill
- reflectSkill
- series-bibleSkill
- seriesSkill
- story-ledgersSkill
- story-memorySkill
- story-planningSkill
- story-reviewSkill
- structured-artifactSkill
- style-guardrailsSkill
- voiceSkill
- writing-principlesSkill
- writing-staffingSkill
- zoom-outSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Treat vocabulary problems as story-structure problems.
- Distinctive: line 34
Place terms at the lowest common scope where they are shared:
- Distinctive: line 53
Before defining new terms, check what already exists:
- Distinctive: line 55
Read relevant vocab files.
- Distinctive: line 56
Search CLAUDE.md, kb pages, outlines, drafts, and work notes.
- Distinctive: line 58
Check how the author uses the term in conversation and prose.
- Distinctive: line 73
Unclear meaning: ask the author: "When you say X, what specifically do you mean?
- Distinctive: line 76
When terminology conflicts with existing kb or draft usage, resolve the drift when the evidence is clear.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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 tokb/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:
- Read relevant vocab files.
- Search
CLAUDE.md, kb pages, outlines, drafts, and work notes. - Spawn focused subagents when the search is broad enough to crowd your context.
- 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

