Audit UI component naming, token usage, and documentation coverage.
npx skills add https://github.com/ilove323/comlan-skills --skill design-system-ilove323
Please help me install this Agent Skill. Skill: design-system Source: https://github.com/ilove323/comlan-skills/tree/main/design/skills/design-system Command: npx skills add https://github.com/ilove323/comlan-skills --skill design-system-ilove323
Design teams struggle with inconsistent component naming, undocumented variants, scattered token usage, and missing accessibility notes; this Skill centralizes auditing and documentation so teams can standardize and scale their UI library.
Run the design-system skill to audit component naming, token usage, and documentation coverage across your UI library.
High-intent search queries and answers about installing and using this skill.
To audit design system consistency, run this Skill to evaluate naming conventions, token coverage, variant completeness, and documentation gaps across your UI components. It requires access to component metadata and optional design tool integrations to extract variant definitions and produce structured remediation reports.
A design token inventory centralizes UI styling variables. You need to audit token usage when your team struggles with scattered token application, inconsistent component naming, or undocumented variants that hinder scaling your component library.
Document component accessibility and variants by applying documentation templates that describe props, states, accessibility notes, usage guidelines, and code examples to generate updated component docs for engineering handoff.
Yes, you can extract variant definitions and token usage from Figma. This Skill features connector-aware workflows that pull component data from design tools like Figma when integrations are available to inform the audit.
The best way to propose new patterns is using this Skill to design component extensions with defined APIs, variants, states, token usage, and accessibility considerations, ensuring alignment with your existing design system.
No, a knowledge base integration is not required, but connector-aware workflows allow you to publish structured reports and component documentation directly to a knowledge base when integrations are available.
codesour-designReconnects existing Figma designs to published design system components.
JongsixGenerate technical documentation from source code and API definitions.
14790897Audit component libraries for naming inconsistencies and missing documentation.
FoundationForgeAudit design systems for naming inconsistencies, hardcoded values, and accessibility gaps.
