shared-dao

Included with Lifetime

$97 forever

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/.

Writing & Docs

What this skill does


# 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 brainstorming 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.

Files: 1

Size: 3.4 KB

Complexity: 7/100

Category: Writing & Docs

Source: https://github.com/haowjy/creative-writing-skills/tree/main/cw/skills/shared-dao

Related in Writing & Docs

jax-development

Included

Use this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.

Writing & Docsscripts

nature-article-writer

Included

Drafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.

Writing & Docsscripts

deckrd

Included

Document-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.

Writing & Docsscripts

clinical-decision-support

Included

Generate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.

Writing & Docsscripts

handling-sf-data

Included

Salesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).

Writing & Docsscripts

accelint-ac-to-playwright

Included

Convert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.

Writing & Docsscripts