design-system

You can document design system components by generating structured guidelines that detail variants, states, and accessibility considerations. This documentation process enforces frontmatter metadata like name and description to maintain consistency across product lines.

Extending a design system involves designing new components that fit the existing architecture of tokens and patterns. This ensures new UI elements maintain consistency and scalability across the product without breaking established conventions.

Yes, you can document component variants, states, and accessibility considerations during a design system audit. The system outputs structured guidelines that capture these details to ensure frontmatter metadata and accessibility standards are met.

A design system audit is specifically designed for teams maintaining tokens, components, and patterns across product lines. It checks naming conventions and generates documentation to ensure consistency and scalable architecture across different products.

The audit focuses on naming conventions, hardcoded values, and component documentation, but requires your design tokens and components to be loaded first. It outputs structured guidelines rather than automatically patching hardcoded values in source code.