generate-documentation

Generate pattern library documentation from UI component metadata.

3|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/GDSDN/kord-aios --skill generate-documentation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generate-documentation
Source: https://github.com/GDSDN/kord-aios/tree/main/src/features/builtin-skills/kord-aios/documentation/generate-documentation
Command: npx skills add https://github.com/GDSDN/kord-aios --skill generate-documentation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of comprehensive documentation for pattern libraries, making it easier to understand, use, and maintain design systems.

Core Features & Use Cases

  • Automated Documentation Generation: Creates searchable, navigable documentation from built components.
  • Component Metadata Extraction: Parses props, types, and variants for detailed documentation.
  • Use Case: A design team can use this Skill to automatically generate up-to-date documentation for their UI component library, ensuring consistency and ease of adoption for developers.

Quick Start

Use the document command to generate pattern library documentation.

Frequently Asked Questions about generate-documentation

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

FAQPage Schema
How do I generate pattern library documentation from existing UI components?

To generate pattern library documentation, this Skill parses existing UI component metadata, extracts props and types, and creates navigable pages with usage examples, accessibility notes, and token references for design system consistency.

What is the best way to document component variants and props automatically?

Automated component documentation extracts component variants and props by parsing metadata directly from built components, creating searchable, navigable pages that ensure consistency and ease of developer onboarding.

Can I use this to generate accessibility notes and token references for a design system?

Yes, design system documentation generated by this Skill includes accessibility notes and token references alongside usage examples, ensuring comprehensive coverage for maintaining consistency and onboarding developers.

Do I need a fully built component library before generating documentation?

Yes, you need existing built UI components. The Skill parses component metadata from built components to extract props, types, and variants to create the searchable, navigable documentation pages.

How does automated code generation for component documentation work?

Automated code generation for component documentation parses your built components to extract metadata, props, and types, then creates navigable pages with usage examples, accessibility notes, and token references.

When should I not use an automated documentation generator for my pattern library?

Automated pattern library documentation generation is not suitable if your UI components lack structured metadata or are not yet built, as the Skill relies on parsing existing component metadata to extract props and types.