shared-dao

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 915238ec14fe · 28 Oct 2026Report an issue or request a re-scan

• Publisherhaowjy GitHub userOwner of the repository this skill is read from
• Source folderhaowjy/creative-writing-skills/plugin/claude/skills/shared-daoThe exact folder we audited
• LicenceApache-2.0As the repository states it
• Commit pinned for this verdict915238ec14feA new audit runs when the source changes
• Repository statusNot archivedPushed today
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

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

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

Shared vocabulary is a structural boundary between human intent and action.
Ambiguous, overloaded, drifting, or misleading terms corrupt reasoning early
and spread confusion through everything downstream. Treat vocabulary
problems as design problems.

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

Clear vocabulary compounds through every downstream artifact. Resolve
terminology while the meaning is still easy to sharpen.

Excerpt, first 1,699 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/haowjy/creative-writing-skills
git -C creative-writing-skills checkout 915238ec14fe

Works in

1. 2026-10-28
   ✓SAFE B 89 / 100

   first audit · source 915238ec14fe

Questions about shared-dao

• github.com/haowjy/creative-writing-skills/tree/main/plugin/claud — the audited source at commit 915238ec14fe and every finding aboveObserved · 28 Oct 2026

Spotted something wrong? Report a correction · Methodology