design-system

To audit design system consistency, you check naming conventions, token usage, variants, and states across components. This process identifies discrepancies to ensure UI reliability across web and mobile projects.

Documenting UI components requires detailing their variants, states, and accessibility notes systematically. Using structured templates ensures design system documentation remains clear and standardized for all UI team members.

Yes, you can extend a design system by drafting and proposing new patterns. The process helps ensure these new additions fit existing guidelines, maintaining consistency across the expanded UI library.

Yes, the design system audit and documentation process is useful for UI teams across both web and mobile projects. It standardizes token usage and component states regardless of the target platform.

You start an audit-then-document flow by running a quick audit on a target component, checking token usage and naming. After identifying inconsistencies, you proceed to document the corrected variants and states.

To categorize skills in a design system, you need to provide frontmatter including a name and description. This metadata allows the system to properly organize and retrieve component documentation and audit commands.