Docs Design

Use to DESIGN or MEASURE documentation — plan or reshape a docs/help/agent-readable surface before implementation (information architecture, mode taxonomy, README/quickstart/reference structure, examples strategy, API/tool-contract docs, error-copy shape, versioning, accessibility baseline, agent context files), or define the telemetry, CI gates, sample tests, retrieval evals, feedback loops, and success metrics that keep docs true. Triggers on "design our docs IA", "how should we structure the quickstart/reference", "what should our tool descriptions look like", "how do we measure docs quality", "set up docs CI gates / freshness checks". Emits a design doc with a concrete proposed structure and acceptance criteria, or a measurement plan with signals, thresholds, owners, and actions. Do NOT use to AUDIT or debug existing docs (use docs-audit), for end-user visual UI design (use ux-audit), or for repo-level agent hardening / AGENTS.md design (use agent-experience).

mkdir -p ~/.claude/skills/docs-design
curl -L https://claudskills.com/skills/docs-design/SKILL.md \
  -o ~/.claude/skills/docs-design/SKILL.md

@misc{docs-design-2026,
  author    = {Thulr},
  title     = {Docs Design [Claude Code skill]},
  year      = {2026},
  publisher = {ClaudSkills},
  url       = {https://claudskills.com/skills/docs-design/}
}