docs-writer

Inspect React component source and Storybook stories to write concise technical documentation.

3|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/keystone-ui/react --skill docs-writer-keystone-ui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-writer
Source: https://github.com/keystone-ui/react/tree/main/.cursor/skills/docs-writer
Command: npx skills add https://github.com/keystone-ui/react --skill docs-writer-keystone-ui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns source code and existing stories into concise, accurate technical documentation so contributors can publish useful component docs without guessing implementation details.

Core Features & Use Cases

  • Reads component source to verify exports, props, variants, slots, and composition patterns before writing.
  • Checks existing Storybook stories and repo conventions so new docs match Keystone UI standards.
  • Use it when you need to create a new story, update component documentation, or draft a short practical guide for a React UI package.

Quick Start

Use the docs-writer skill to inspect the target component and produce a concise Storybook-ready documentation update.

Frequently Asked Questions about docs-writer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate accurate React component documentation from source code?

Generate accurate React component documentation by inspecting source code to verify exports, props, variants, and slots before writing. This ensures the technical documentation matches actual implementation details and composition patterns.

How do I write Storybook stories that match my existing repository conventions?

Write Storybook stories that match repository conventions by checking existing story patterns and repo standards before generating new MDX documentation. This ensures new component docs align with established formatting rules and subpath import usage.

What is the best way to document React component variants and slots?

Document React component variants and slots by reading the component source to verify implementation details, then producing concise technical documentation that covers component APIs, variants, slots, and composition examples accurately.

Can I use this to create documentation for React UI package component APIs?

Yes, you can create documentation for React UI package component APIs by inspecting implementation details and existing story patterns. It produces concise practical guides and Storybook-ready docs for component libraries.

Does the documentation generation require source verification before writing?

Yes, documentation generation requires source verification before writing to ensure accurate subpath import usage and convention checks. It verifies exports, props, variants, and slots directly from the component source code.