component-guidelines-docs

Component guideline documentation is generated by providing a component ID that exists in Rootage YAML. The Skill automatically extracts props and slots from `/packages/rootage/components/{component-id}.yaml`, then produces standardized MDX documentation with anatomy, guidelines, do's/don'ts, and component references in `docs/content/docs/components/{id}.mdx`.

SEED component guidelines should include extracted API props from Rootage YAML, structured anatomy sections, practical usage guidelines with do's and don'ts, image references, component comparisons, and V2-to-V3 migration guides where applicable. Output is delivered in Korean-language MDX format matching existing design patterns.

Yes, this Skill handles both creating new component documents and updating existing guidelines. It re-extracts current props from Rootage YAML and regenerates standardized sections, ensuring documentation stays aligned with component specifications and design system consistency.

The primary input is a component ID referencing an existing Rootage YAML file at `/packages/rootage/components/{component-id}.yaml`. The Skill parses this YAML to extract props, slots, and specifications, then uses that structured data to build comprehensive guideline documentation.

Yes, the Skill can generate V2-to-V3 migration guides as part of component guideline documentation. It documents API changes and guidance to help users transition between versions while maintaining consistency with SEED Design System standards.

YAML-driven documentation ensures consistency across all SEED components by automatically extracting the source of truth—props, slots, and specifications—from Rootage files. This eliminates manual errors, keeps docs synchronized with actual component APIs, and produces standardized MDX output.