generate-component-documentation

To auto-generate UI component documentation, this Skill applies established documentation templates from your docs folder to new components, ensuring structural consistency across your project. It leverages existing styles and story implementations to keep docs and code synchronized without manual writing.

Keeping component docs in sync with story implementations is achieved by mirroring the same-named story implementation found in crates/story/src/stories. The Skill automatically aligns the generated documentation with these story files to prevent drift between code and written references.

Including API references from docs.rs in generated component documentation is handled automatically by the Skill. It incorporates prop and API details from docs.rs into the final output, applying pattern-based styles to ensure the API reference integrates seamlessly with the rest of the docs.

Yes, you can use pattern-based templates to document components across the docs folder, story implementations, and API references. The Skill leverages documentation styles already established in these locations to generate consistent component documentation that matches your project's existing format.

No external dependencies are required to use this documentation generation approach. The Skill operates independently by reading existing templates, story implementations in crates/story/src/stories, and API references from docs.rs to produce the final component documentation output.