design-system-alignment

Inventory design system tokens, components, and naming conventions to identify gaps.

234|55|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/Owl-Listener/designpowers --skill design-system-alignment
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-system-alignment
Source: https://github.com/Owl-Listener/designpowers/tree/main/skills/design-system-alignment
Command: npx skills add https://github.com/Owl-Listener/designpowers --skill design-system-alignment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design systems sometimes drift across tokens, components, and naming, leading to inconsistent UX and accessibility gaps.

Core Features & Use Cases

  • Inventory tokens, components, and patterns; define semantic and component tokens; establish naming conventions; perform accessibility audits.
  • Use Case: Teams aligning a new component to an existing design system to ensure consistency across pages and platforms.

Quick Start

Audit an existing design system and propose aligned tokens, components, and naming conventions to improve consistency and accessibility.

Frequently Asked Questions about design-system-alignment

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

FAQPage Schema
How do I audit an existing design system for consistency and accessibility gaps?

To audit a design system for consistency and accessibility, inventory existing tokens, components, and naming conventions to identify drift, then document architectural gaps and produce aligned component specifications.

What are semantic and component tokens in a design system?

Semantic and component tokens are structured naming conventions that map raw design values to functional meanings, ensuring consistent theming and accessible UX across products while preventing design system drift.

How do I establish naming conventions for design system pattern libraries?

Establish naming conventions for pattern libraries by inventorying existing tokens and components, defining semantic token hierarchies, and documenting architecture to align naming across pages and platforms.

Can I use this to align a new component to an existing design system?

Yes, you can align new components to an existing design system by auditing current tokens and naming conventions, then producing component specifications that satisfy accessibility and consistency requirements across products.

What's the best way to document design system architecture and token inventory?

Document design system architecture by inventorying all tokens, components, and patterns, then defining semantic and component tokens with established naming conventions to produce comprehensive architecture documentation.

When do I need to perform an accessibility audit on my design system components?

Perform an accessibility audit on design system components when you observe naming drift, inconsistent theming across pages, or when aligning new initiatives to ensure tokens and components meet accessibility requirements.