Docs Coverage

by murphytrueman

Docs Coverage is a Quality skill for Claude Code, published by murphytrueman in design-system-ops.

176 stars7 forkson murphytrueman/design-system-opsAdded 2026/09/07+1% in starsRepository updated 2026/08/22

View source on GitHub Download repo ZIP

claude-codeclaude-code-plugindesign-systemdesign-systemsdesign-tokensfigmaskills

Install in seconds

Install Docs Coverage

Copy Docs Coverage into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/murphytrueman/design-system-ops/tree/main/skills/docs-coverage ~/.claude/skills/docs-coverage

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/murphytrueman/design-system-ops.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: skills/docs-coverage/SKILL.md in murphytrueman/design-system-ops
Installs to: ~/.claude/skills/docs-coverage
Collection: One of 25 skills cataloged from this repository
Category: Quality — 1817 skills

What Docs Coverage does

Docs Coverage audits a design system’s documentation surface against its component library. It finds undocumented components, stale docs, and orphaned pages using Storybook, local code, and optional docs integrations.

Docs Coverage is cataloged under Quality on DirSkills. Docs Coverage comes from a repository tagged claude-code, claude-code-plugin, design-system, design-systems and design-tokens.

Documentation

README

Excerpt

Docs coverage

A skill for auditing whether a design system's documentation surface keeps pace with its components. It measures the code (the source of truth for what exists) against each documentation surface and reports three things: coverage gaps (components with no documentation), staleness (documentation that predates the component's last code change), and orphaned docs (pages for components that no longer exist). Produces a severity-rated finding table with per-signal confidence labelling.

Context

Code is the source of truth for what components exist; the documentation surface is measured against it. A component in code with no docs is a coverage gap; a page for a deleted component is an orphan; a page older than the component's last change is a staleness risk.

This is the opening of the README. Read the full README on GitHub.

Commands Docs Coverage provides

Slash commands named in this skill’s SKILL.md, listed in the order they first appear.

/index
/last-modified

Frequently asked about Docs Coverage

What else does murphytrueman publish alongside Docs Coverage?
Docs Coverage is one of 25 skills that DirSkills catalogs from murphytrueman/design-system-ops, the repository it ships in. Its siblings there include AI Component Description, Accessibility Per Component and Adoption Report. Each one is a separate skill with its own page in this directory, installs the same way Docs Coverage does, and is maintained by murphytrueman in that same repository. The rest of the collection is listed on the murphytrueman/design-system-ops page.
How does Docs Coverage compare to other Quality skills?
Docs Coverage ranks #1693 by stars among the 1817 Quality skills in this catalog. The most-starred ones next to it are Benchmark, Benchmark Optimization Loop and API Design Patterns. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Docs Coverage against them. Open each page to compare what they document and how they install.