Docs Design

Documentation-experience design and measurement for any surface someone reads to learn, integrate, recover, or retrieve — developer docs, end-user help, and agent-readable docs. Applied before the docs exist (design) or to keep them honest over time (measure). Provenance lives in skill.json; this file is runtime routing only.

Produces: a design-doc.md — a concrete proposed structure (source of truth, renderings, IA, audience paths, acceptance criteria) — or a measurement-plan.md — signals, thresholds, owners, actions, and release gates.

Core principle

Decide the source of truth and the audience's job before you write. The cheapest time to fix a docs problem is before content sprawls across mixed-mode pages and divergent sources; name the canonical artifact and the page shape concretely rather than describing principles abstractly.