Skip to main content
skill CX Codex

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

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add haowjy/creative-writing-skills --skill shared-dao -a claude-code
Open on GitHub

What 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-code

2Manually: put the files in place

~/.claude/skills/shared-dao/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/shared-dao/

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.

From the same set32

The whole set →
project-setup The project-setup Claude Code skill gathers details about a creative writing project and prepares its working files. The author starts it once at the beginning of a project. CX Codex +1 608installs project-setup project-setup is a Claude Code skill that interviews the author, collects writing samples, and creates AGENTS.md with project conventions. It runs during initial project setup. CX Codex +1 608installs story-memory The story-memory Claude Code skill preserves and retrieves information from a fiction project. It comes into play when passing context between writing tasks or maintaining persistent story notes. CX Codex +1 606installs intent-modeling intent-modeling — a skill that makes an AI agent work out what you meant before it acts on what you literally said. CX Codex +1 586installs shared-dao shared-dao keeps story terms consistent across lore files and drafts, organizing them inside kb/. It eliminates drifting names, ambiguous factions, and conflicting magic systems. CX Codex +1 581installs creative-writing-muse The creative-writing-muse skill turns the agent into a co-author: discusses the plot, writes drafts in your voice, critiques and revises the text, keeps project memory in one conversation. CX Codex +1 568installs creative-research The creative-research skill gathers grounded material for a story question: history, culture, daily detail, how a trade actually works. You get back a sourced report. CX Codex +1 557installs grill-with-docs grill-with-docs challenges concepts and decisions by grounding every critical inquiry strictly in local repository documents. CX Codex +1 556installs

Project sponsors

Companies that keep this analytics open