component-docs
100 / 100 · Low risk
Fine to try.
Use to write one component's documentation entry from its code, stories and real call sites, such as "document the button", "write docs for Select", "what states does Toast have", or usage rules for a new or changed component. Not for foundations or pages that span components, which no skill here writes, nor for changing the component, which is build-design-system.
What this skill can do
We found nothing in the files we read that matches our rules. That does not prove the skill is safe: see the limits of static scanning.
Install
Paste this into your terminal. It downloads exactly the version we scanned, not whatever is newest.
if [ -e ~/.agents/skills/'component-docs' ] || [ -L ~/.agents/skills/'component-docs' ]; then echo 'A skill folder named component-docs already exists — not replacing it' >&2; false; else d=$(mktemp -d) && git clone --quiet --filter=blob:none --no-checkout 'https://github.com/arla6ka/design.how' "$d" && git -C "$d" checkout --quiet '419fa5af1721eebfab9e0062a630de36ffd0b342' -- 'skills/component-docs' && mkdir -p ~/.agents/skills && cp -R "$d"/'skills/component-docs' ~/.agents/skills/'component-docs' && rm -rf "$d"; fi
Codex reads ~/.agents/skills directly. For Claude Code, Cursor, Copilot, Gemini CLI, Antigravity or OpenCode, also link it. For Claude Code: ln -s ~/.agents/skills/'component-docs' ~/.claude/skills/'component-docs' (other agents: ~/.cursor/skills, ~/.copilot/skills, ~/.gemini/skills, ~/.gemini/config/skills, ~/.config/opencode/skills). Or install through the finder skill, which does both.
Badge for your README
[](https://zalavijaysinh.github.io/skilltrust/repos/arla6ka/design.how/)
Score history
| Date | Version | Score |
|---|---|---|
| 2026-11-07 | 419fa5a | 100 |