Docs Coverage

Audit whether a design system's documentation surface keeps pace with its component library — coverage gaps (components with no docs), staleness (docs that predate the component's last code change), and orphaned docs. Works with zero integration from the codebase and a Storybook build; Zeroheight, Supernova, and custom docs sites are optional layers. Trigger when someone says: docs coverage, documentation audit, are our docs up to date, which components are undocumented, is our documentation keeping pace, stale docs check, documentation health, Storybook coverage, or anything about whether the documentation surface matches the components. Do NOT trigger for WRITING documentation — use usage-guidelines, pattern-documentation, token-documentation, or ai-component-description for that. Do NOT trigger for general system health (use system-health) or for documentation usage/analytics (use adoption-report).

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

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