docs-curator

Review Keystone UI Storybook stories against component source and exports.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps keep Keystone UI documentation aligned with the real component implementation, preventing stale examples, missing coverage, and misleading guidance.

Core Features & Use Cases

  • Story Review: Checks Storybook stories against the actual component source, exports, variants, and state handling.
  • Documentation Curation: Improves descriptions, examples, and composition guidance so documentation is practical and consistent.
  • Conventions Validation: Verifies import paths, icon usage, argTypes, data-slot conventions, and Keystone UI-specific patterns before publishing.
  • Use Case: Use it when a component story needs a quality audit, when new variants are added, or when documentation must be updated to reflect implementation changes.

Quick Start

Ask the skill to review the selected Keystone UI story after checking the component source and matching the documentation to the current API.

Frequently Asked Questions about docs-curator

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

FAQPage Schema
How do I audit Storybook stories against the actual React component source?

To perform a Storybook story review, inspect the component source code to verify exports, variants, and state handling, then align argTypes and examples with the actual implementation. This ensures documentation matches the real API.

What is documentation curation for React component libraries?

Documentation curation for React component libraries is the process of reviewing and improving descriptions, examples, and composition guidance so docs remain accurate and consistent with the actual implementation. It prevents stale examples and misleading guidance.

How do I verify subpath imports and argTypes alignment in Keystone UI?

Verify subpath imports and argTypes alignment by inspecting the component source to check import paths, icon usage, and data-slot conventions. Validate that argTypes match the actual component props before publishing documentation.

When do I need to run a docs audit for component stories?

You need a docs audit for component stories when new variants are added, when a component story needs a quality check, or when documentation must be updated to reflect implementation changes. This keeps coverage complete and consistent.

Does Keystone UI documentation review work with Fumadocs MDX pages?

Keystone UI documentation review supports Fumadocs MDX pages for coverage checks, composition review, and consistency validation across variants, states, and examples. It applies the same source inspection and rule-based formatting to MDX content.

Why does my Storybook documentation show missing coverage for component states?

Storybook documentation shows missing coverage when stories are not updated to reflect new variants or state handling added to the component source. A documentation audit matches the stories against the implementation to identify and fill these gaps.