design

Generates intent-driven UI design systems and components with persisted design tokens.

6|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/greglas75/zuvo --skill design-greglas75
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design
Source: https://github.com/greglas75/zuvo/tree/main/skills/design
Command: npx skills add https://github.com/greglas75/zuvo --skill design-greglas75

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building UI without a documented design rationale leads to inconsistent components, hardcoded values, and generic-looking interfaces that drift across sessions. This Skill enforces traceable design decisions by capturing user intent, exploring the product domain, and persisting a reusable design system in .interface-design/system.md and system.json. ## Core Features & Use Cases - Design System Generation: Runs intent questions, domain exploration, and direction selection to produce system.md plus a machine-readable system.json with tokens, motion, and patterns. - Component Construction & Improvement: Builds new components with mandatory per-component checkpoints, improves existing UI in place, or extracts implicit design patterns from existing code into a proposed system. - Craft Validation: Applies four tests (Swap, Squint, Signature, Token) to verify every visual value traces back to a design token before persisting results. - Use Case: A developer starting a new SaaS dashboard runs init to define a calm-authority direction, then builds each component against saved tokens so future sessions stay visually consistent. ## Quick Start Ask the AI to run the design skill in init mode to explore intent and generate a design system for your project.

Frequently Asked Questions about design

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

FAQPage Schema
How do I create a design system for a new UI project?

Run the skill in init mode, which is the default. It asks three intent questions about users, tasks, and feel, explores the product domain, proposes a design direction with tokens, then saves system.md and system.json to .interface-design/.

How to extract a design system from existing UI code?

Use the extract mode with a path argument. It scans all UI files, catalogs colors, spacing, radius, font sizes, and motion values, maps findings to the closest design direction, and proposes a system.md based on actual usage.

Does this work with Tailwind CSS and React projects?

Yes. The prerequisite check detects Tailwind v3 or v4, styled-components, and CSS modules, and adapts token format accordingly. It also detects React, Next, Vue, Svelte, and Angular from package.json dependencies.

What is the difference between design and design-review?

The design skill creates and improves UI and produces the system.md and system.json artifacts. design-review is a separate skill that audits existing UI against DX1-DX20 checks, consuming those artifacts for token matching when present.

When should I use the --quick mode?

Use --quick with a component name when a design system already exists and you want a fast build. It loads system.md, builds the component, and auto-saves, skipping craft validation but still enforcing token usage and 44px touch targets.

What happens if craft validation tests fail?

If fewer than 3 of the 4 tests pass after iteration, the run continues but the output is marked PROVISIONAL with a BELOW-BAR notice in the craft validation report. The report is saved to .interface-design/ with per-test evidence.