generate-documentation

Generates pattern library documentation from built design system components.

3|Updated Feb 7, 2026

Search Tags:#typescript #documentation #accessibility #design system #components #generate #pattern library

Ready to run

npx skills add https://github.com/gabrielnsmnto/kord-aios --skill generate-documentation-gabrielnsmnto

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: generate-documentation
Source: https://github.com/gabrielnsmnto/kord-aios/tree/main/src/features/builtin-skills/kord-aios/documentation/generate-documentation
Command: npx skills add https://github.com/gabrielnsmnto/kord-aios --skill generate-documentation-gabrielnsmnto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually writing documentation for every component in a design system is slow and quickly becomes outdated. This Skill automates the creation of a searchable, navigable pattern library directly from built components. ## Core Features & Use Cases - Component Scanning and Parsing: Finds all atoms, molecules, and organisms, then extracts props, types, and variants from TypeScript definitions. - Structured Doc Generation: Produces an index page, per-component pages, token reference, accessibility guide, and getting-started guide. - Multiple Execution Modes: Choose YOLO (autonomous), Interactive (default, with checkpoints), or Pre-Flight Planning for ambiguous work. - Use Case: After building 15 design system components, run the skill to generate a complete pattern library with prop tables, usage examples, and WCAG accessibility notes under design-system/docs/. ## Quick Start Ask the agent to generate pattern library documentation for all built design system components.

Frequently Asked Questions about generate-documentation

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

FAQPage Schema

How do I generate documentation for a design system component library?▼

Run the generate-documentation skill after building components. It scans atoms, molecules, and organisms, parses TypeScript props and variants, and outputs an index page, per-component pages, token reference, and accessibility guide.

What files does pattern library documentation generation produce?▼

It produces index.md as the library homepage, components/{Component}.md pages per component, tokens.md for token reference, accessibility.md for WCAG guidelines, and getting-started.md for setup instructions.

What prerequisites are needed before generating component documentation?▼

You need at least one built component, a completed design system setup, and existing component markdown files. Without these, the scan and parsing steps have nothing to document.

What are the differences between YOLO, Interactive, and Pre-Flight modes?▼

YOLO runs autonomously with minimal prompts for simple tasks. Interactive (the default) adds decision checkpoints and explanations. Pre-Flight Planning resolves all ambiguities upfront before execution, suiting critical or unclear work.

Does the generated documentation stay up to date when components change?▼

Yes, documentation auto-generates from TypeScript types and updates when components change. It also supports live Storybook links if Storybook integration is enabled.