design-system-patterns

Consolidate design tokens, theming, and component patterns into a cohesive UI system.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/emilneuraz-ai/neuraz-web --skill design-system-patterns-emilneuraz-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-system-patterns
Source: https://github.com/emilneuraz-ai/neuraz-web/tree/main/.agents/skills/.agents/skills/design-system-patterns
Command: npx skills add https://github.com/emilneuraz-ai/neuraz-web --skill design-system-patterns-emilneuraz-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Establishes a scalable foundation for UI design by centralizing design tokens, theming infrastructure, and component architecture patterns to ensure consistency across products.

Core Features & Use Cases

  • Design Tokens: Primitive, semantic, and component tokens; multi-platform outputs.
  • Theming Infrastructure: CSS custom properties, theme context/providers, dynamic switching, system preference detection, and persistent storage.
  • Component Architecture: Compound components, polymorphic components, variants, slots, and headless patterns.
  • Token Pipeline: Figma-to-code synchronization, Style Dictionary configuration, token transformation and formatting.

Quick Start

Set up a starter design system repository that defines tokens, enables theming, and includes a small component library to bootstrap usage.

Frequently Asked Questions about design-system-patterns

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

FAQPage Schema
How do I build a scalable design system with design tokens and theming?

Build a scalable design system by consolidating primitive, semantic, and component tokens into a centralized infrastructure. This approach ensures UI consistency across products by centralizing design tokens, theming, and component architecture patterns.

What is the best way to synchronize Figma design tokens to code?

Synchronize Figma design tokens to code by implementing a token pipeline using Style Dictionary. This pipeline handles token transformation and formatting to generate multi-platform outputs for web and mobile.

How do CSS variables work for dynamic theme switching in component libraries?

CSS variables enable dynamic theme switching by acting as custom properties managed through theme context providers. This infrastructure supports system preference detection, persistent storage, and dynamic switching across multiple brands.

Can I use compound and polymorphic patterns for component architecture?

Compound and polymorphic patterns are supported for component architecture. These patterns, along with variants, slots, and headless components, provide a flexible API structure for building scalable component libraries.

Does this design system approach support multiple brands and platforms?

This design system approach supports multiple brands and platforms by enforcing a token-driven pipeline. It generates multi-platform outputs and enables consistent theming across web and mobile applications for various brand contexts.

When do I need component tokens versus semantic design tokens?

Component tokens are needed for component-specific styling overrides, while semantic tokens map primitive values to contextual meanings. This hierarchical token structure ensures consistent scaling and clear governance across the design system.