design-system-doc SKILL.md skillA
design-system-doc from qa-aman/claude-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add qa-aman/claude-skills/design-system-doc@git:20260303.00c2750Pins git:20260303.00c2750 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- qa-aman/claude-skills
- Path
skills/by-role/designer/design-system-doc/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260303.00c2750, committed Mar 3, 2026
- Size
- 4,494 bytes
- Repository stars
- 21
- License
- MIT
Document a design system component. Use when the user says "design system docs", "document this for the design system", "add this to the design system", "design token", "component library docs", "style guide", "design system entry", or wants to formally document a pattern, component, or token for team-wide use - even if they don't explicitly say "design system".
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
## Overview Based on **"Atomic Design"** by Brad Frost. A design system is not a component library - it's a shared language. Frost's insight: components without documentation are just code. Documentation is what transforms a component library into a system that a whole team can use consistently without needing to ask the original designer. Design system documentation has two audiences: designers who need to use the pattern correctly, and engineers who need to implement it accurately. Write for both. ## Workflow ### Step 1: Establish the entry structure Every design system entry should follow the same structure so team members can predict where to find information: ``` 1. Overview (what this is, one paragraph) 2. When to use / when not to use 3. Anatomy (labeled diagram of all parts) 4. Variants 5. States 6. Design tokens used 7. Usage examples (correct and incorrect) 8. Accessibility 9. Related components 10. Changelog ``` ### Step 2: Write the overview One paragraph: what is this component/pattern? What job does it do in the UI? Include a simple visual (or Figma embed) showing the component in its default state. ### Step 3: When to use / when not to use …
Read the whole file at its exact version.
How to install
mdr add qa-aman/claude-skills/design-system-doc@sha256:95fae4c5bb19bb21The line at the top of this page pins the label git:20260303.00c2750, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_5umrxtjtmwqnzd7l)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Mar 3, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4494 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
qa-aman/claude-skills · 21 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_5umrxtjtmwqnzd7l GET https://markdownregistry.com/api/v1/resolve?ref=qa-aman/claude-skills/design-system-doc GET https://markdownregistry.com/api/v1/blob/95fae4c5bb19bb21199a99a661582891c9b41e539c54d46d1b1f03b680bc266f
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.