ui-design-system

Align UI decisions with centralized design tokens, layout patterns, and component recipes.

2|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/yutna/vibe-next-template --skill ui-design-system-yutna
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui-design-system
Source: https://github.com/yutna/vibe-next-template/tree/main/.claude/skills/ui-design-system
Command: npx skills add https://github.com/yutna/vibe-next-template --skill ui-design-system-yutna

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

UI teams struggle to build and scale consistent interfaces across projects. This skill provides a centralized design system with tokens, patterns, and recipes to align layouts, motion, and components.

Core Features & Use Cases

  • Central design tokens and layout patterns to ensure consistency across pages.
  • Reusable motion and component recipes to accelerate UI implementation.
  • Real-world guidance for landing pages, dashboards, forms, and detail views.

Quick Start

Install the UI design system guides and start applying the token- and motion-driven patterns to your pages.

Frequently Asked Questions about ui-design-system

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

FAQPage Schema
How do I enforce consistent UI design across multiple projects?

To enforce consistent UI design, you can align layouts, motion, and components with centralized design tokens, layout patterns, and component recipes. This ensures reusable vocabulary and visual consistency across dashboards, landing pages, and forms.

What are design tokens and how do they drive UI patterns?

Design tokens are centralized variables stored in JSON format that drive UI patterns. They standardize visual properties like typography, motion, and layout, ensuring reusable vocabulary and consistent implementation across all product surfaces.

How do I apply reusable component recipes to dashboards and forms?

You apply reusable component recipes by referencing centralized JSON files that contain predefined composition patterns. These recipes provide real-world guidance to accelerate the UI implementation of dashboards, landing pages, and forms.

Can I use this design system to align motion and typography across different pages?

Yes, you can align motion and typography across pages by applying the centralized design tokens. The system provides specific motion recipes and token-driven guidance to ensure animations and text remain visually unified across products.

Do I need specific dependencies to use token-driven UI patterns?

No, you do not need specific dependencies to use token-driven UI patterns. The system relies solely on internal JSON files for design tokens, layout patterns, and component recipes to provide standalone guidance for your interfaces.

What is the best way to scale consistent interfaces without repeating code?

The best way to scale consistent interfaces is to centralize your design tokens and component recipes into reusable JSON definitions. This approach eliminates repeated code by providing a single source of truth for layouts, motion, and component composition.