design-system-patterns

Define and enforce scalable design system patterns for tokens, theming, and components.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/ekremmkasap/jarvis --skill design-system-patterns-ekremmkasap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-system-patterns
Source: https://github.com/ekremmkasap/jarvis/tree/main/server/agent_prompts/wshobson/plugins/ui-design/skills/design-system-patterns
Command: npx skills add https://github.com/ekremmkasap/jarvis --skill design-system-patterns-ekremmkasap

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Design teams often struggle to maintain UI consistency across products and platforms. This skill helps define tokens, themes, and components to scale design systems and speed delivery.

Core Features & Use Cases

  • Design Tokens: Primitive, semantic, and component tokens for multi-brand ecosystems.
  • Theming Infrastructure: CSS custom properties, theme context, and dynamic switching across light/dark modes.
  • Component Architecture: Patterns like compound components, polymorphic components, slots, and consistent APIs.
  • Token Pipeline: End-to-end flow from design tokens to code assets across web and mobile.

Quick Start

Define tokens, implement theming, and build components using the patterns described above in your UI project.

Frequently Asked Questions about design-system-patterns

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

FAQPage Schema
How do I manage design tokens for a multi-brand UI ecosystem?

Design tokens for multi-brand ecosystems are managed through a structured hierarchy of primitive, semantic, and component tokens. This approach ensures consistent theming infrastructure and scalable UI across different brands.

What is the best way to implement dynamic theme switching with CSS variables?

Dynamic theme switching is implemented using CSS custom properties and a theme context. This infrastructure enables seamless transitions between light and dark modes across web and mobile applications.

How do I structure component architecture for a scalable design system?

Scalable component architecture utilizes patterns like compound components, polymorphic components, and slots. These patterns provide consistent APIs and reusable building blocks for modular design systems.

Does this design system pattern support cross-platform token pipelines?

Yes, the token pipeline supports cross-platform outputs by transforming design tokens into code assets. This end-to-end flow ensures tokens are consistently applied across both web and mobile apps.

When do I need semantic and component level design tokens?

Semantic and component level design tokens are needed when building multi-brand UI systems that require consistent theming. They abstract primitive values into meaningful aliases, enabling scalable theme switching and brand variation.

Can I use these design system patterns for mobile app theming?

Yes, these design system patterns apply to mobile app theming. The token pipeline and theming infrastructure generate cross-platform outputs, ensuring consistent component architecture and theme switching across mobile environments.