- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add arla6ka/design.how --skill component-docs -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add arla6ka/design.how --skill component-docs -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add arla6ka/design.how --skill component-docs -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add arla6ka/design.how --skill component-docs -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/arla6ka/design.how/tree/HEAD/skills/component-docsFrom the publisher
A draft entry for one component, built only from what its sources say. Gaps are marked, not filled. It does not judge the design and it publishes nothing. The heading order and a worked example are in references/doc-format.md.
references/doc-format.md into the draft, empty.rule/<component>-<slug>, a condition, an action, a reason, its evidence (two call sites, a measurement with its path, a named principle, or the person's words), and a Don't: line with real code that breaks it. A rule you cannot break with a snippet is cut.The entry, then Sources, Conflicts, Guessed at, and Gates (a question with its default) only where a rule adds one. Run on its own, it saves to docs/system/<name>.md with a draft comment on line 1 and writes each missing example file. The reply opens with the path, what the entry covers and its status, then up to three questions with defaults and one prompt the person can paste to take the next step.
A props type with no variant prop is an empty list. Variants reads "None" and the run goes on. One real use, planned uses and a deprecated predecessor are marked as such, not stopped on. A stopped run returns the stop, the facts sourced so far by section, and the smallest reply that unblocks it ("one screen name, what put the component there, and which variant showed").
Defect: line to the owner with what goes wrong for the user and the smallest fix.### Parts subsection under Description. A compound component (Tabs with Tab) is one entry.grep -o on the saved file, below the draft comment.Every variant, prop, token and example has a Sources line. Every Usage rule has evidence and a Don't: line. Every conflict is shown. The nine headings are present in order, and a section with nothing sourced reads Not applicable: <reason>.
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
---name: component-docsdescription: Use to write one component's documentation entry from its code, stories and real call sites, such as "document…---# skills/component-docs/SKILL.mdOverview
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.
FAQ
Download skills/component-docs/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/arla6ka/design.how.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.