skills.rest
ngochuy13
ngochuy13COMMUNITY
Explore all skills by this author →
GitHub

design-system

Audit design systems for token, component, and accessibility inconsistencies.

Updated Apr 23, 2026
Search Tags:#accessibility#design system#audit#design tokens#pattern design#component documentation#ui consistency
One-click install
npx skills add https://github.com/ngochuy13/intern-dev --skill design-system-ngochuy13
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-system
Source: https://github.com/ngochuy13/intern-dev/tree/main/skills/design-system
Command: npx skills add https://github.com/ngochuy13/intern-dev --skill design-system-ngochuy13

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design teams waste time and consistency breaks when components, tokens, and accessibility guidance drift across product surfaces.

Core Features & Use Cases

  • Full design-system audit: identify naming inconsistencies, hardcoded token usage, and gaps in component variants, states, and documentation; produce a prioritized findings list.
  • Component documentation: standardize how a component’s variants, props, states, accessibility notes, and do/don’t guidance are described.
  • Pattern extension: design new components or patterns that align with existing tokens, API shape, interaction states, and accessibility expectations.

Quick Start

Ask the skill to run a full audit of your design system for consistency issues, token coverage problems, and missing documentation.

Frequently Asked Questions about design-system

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a design system for UI consistency and token drift?▼

A design system audit identifies naming inconsistencies, detects hardcoded token usage, and highlights gaps in component variants and accessibility documentation, producing a prioritized findings list to reduce UI drift.

What is the best way to document design system components and accessibility guidance?▼

Documenting design system components standardizes descriptions of variants, props, states, accessibility notes, and do/don't guidance to maintain UI consistency across product surfaces.

How do I extend a design system with new patterns that align with existing tokens?▼

Extending a design system with new patterns requires designing components that align with existing design tokens, API shape, interaction states, and accessibility expectations to ensure seamless UI consistency.

How do I detect hardcoded values in my design tokens?▼

Detecting hardcoded values in design tokens requires a full design-system audit to identify non-token usage, naming inconsistencies, and component variant gaps, yielding a prioritized list of issues to fix.

Can I use this approach to standardize component documentation across multiple product surfaces?▼

Yes, standardizing component documentation across product surfaces is achieved by generating structured outputs that cover component variants, props, states, accessibility notes, and do/don't guidance for UI consistency.

Related Skills

Explore More Design & Creative Skills→
rakibulismrakibulism
2

design-system

Audit design system components for naming, tokens, states, and accessibility.

Community
Intermediate
sun2443sun2443

design-system

Audit UI design systems for naming consistency and token coverage.

Community
Intermediate
PiercingXXPiercingXX
1

ant

Generate accessibility-focused Ant Design guidance with token-driven UI constraints.

Community
Advanced
FoundationForgeFoundationForge

design-system

Audit design systems for naming inconsistencies, hardcoded values, and accessibility gaps.

Official
Intermediate