shared-dao · haowjy, claude — Claude Code skill: what it does, how to install
shared-dao — a Claude Code skill that enforces terminology consistency across project files. Triggers when introducing new terms, encountering overloaded words, or reconciling naming collisions.
Apache-2.0 581 installs ★ 601 updated 2026-11-16
npx skills add haowjy/creative-writing-skills --skill shared-dao -a claude-codeWhat shared-dao does
The skill instructs the agent to inspect vocabulary files, knowledge base entries, and existing code before creating new terminology. It enforces a strict principle: one name per concept, and one concept per name. Discovering a previously defined concept under a different title counts as a conflict rather than a fresh idea.
Disambiguation follows structured logic. When one term carries two distinct meanings, the agent establishes one canonical definition and assigns an independent label to the other. For concepts with multiple synonyms, it designates an official term and stores alternates as aliases. If an ambiguity cannot be untangled from project context, the agent explicitly flags it for human judgment instead of carrying competing names forward.
Execution requires loading /creative-writing-skills:qi-layer if that dependency is not already active in the environment.
What it helps with
- disambiguate overloaded terms across code and documentation
- unify competing synonyms into a single canonical identifier
- scan vocabulary files before coining new project labels
- flag unresolved terminology conflicts for developer intervention
Example prompts for the agent
- Review our terminology files and resolve duplicate names for this data model.
- Check the codebase for naming collisions before we adopt the term Workspace.
- Consolidate our vocabulary list into canonical terms with explicit aliases.
How to install shared-dao
1Skills CLI (Vercel)
npx skills add haowjy/creative-writing-skills --skill shared-dao -a claude-code2Manually: put the files in place
~/.claude/skills/shared-dao/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/shared-dao/
1Skills CLI (Vercel)
npx skills add haowjy/creative-writing-skills --skill shared-dao -a codex2Manually: put the files in place
.agents/skills/shared-dao/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add haowjy/creative-writing-skills --skill shared-dao -a cursor2Manually: put the files in place
.cursor/skills/shared-dao/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install haowjy/creative-writing-skills plugin/claude/skills/shared-dao2Manually: put the files in place
.github/skills/shared-dao/SKILL.md1Skills CLI (Vercel)
npx skills add haowjy/creative-writing-skills --skill shared-dao -a gemini-cli2Platform CLI
gemini skills install https://github.com/haowjy/creative-writing-skills --path plugin/claude/skills/shared-daoManually: put the files in place
.devin/skills/shared-dao/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add haowjy/creative-writing-skills --skill shared-dao -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about shared-dao
How to install shared-dao in Claude Code?
Run npx skills add haowjy/creative-writing-skills --skill shared-dao -a claude-code. The definition lands at ~/.claude/skills/shared-dao/SKILL.md.
What does shared-dao do?
It manages project terminology by preventing redundant labels, aligning synonyms to canonical names, and resolving conflicting definitions.
What is required for shared-dao to run?
It requires the /creative-writing-skills:qi-layer skill to be loaded in the active workspace.
Source text
SKILL.md · Apache-2.0
--- name: shared-dao description: 'Load when a concept has two names, a name has two meanings, or you are about to coin a term: resolve it early, one name per concept, in the project''s vocab files.' metadata: type: principle --- # Shared Dao Load `/creative-writing-skills:qi-layer` if it isn't already loaded. ## Core Discipline Check important terms. 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 human judgment is genuinely required ## Discovery 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. ## Disambiguation - **Same term, different meanings:** pick one meaning for canonical, give the other its own name. - **Different terms, same meaning:** pick one as canonical, record the others as aliases. - **Unclear meaning:** interview until meaning converges, then define. When terminology conflicts with existing usage and you cannot resolve it, flag explicitly rather than carrying two competing names forward.
© haowjy · Apache-2.0 · haowjy/creative-writing-skills
Similar skills
All skills for Writing and docs →shared-dao by other authors comes first.