variant

Builds multiple design variants of a UI component behind a switchable picker.

6.7k|239|Updated Jul 10, 2026
One-click install
npx skills add https://github.com/jakubkrehel/skills --skill variant-jakubkrehel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: variant
Source: https://github.com/jakubkrehel/skills/tree/main/skills/variant
Command: npx skills add https://github.com/jakubkrehel/skills --skill variant-jakubkrehel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Choosing between design directions for a UI component is hard when options only exist as descriptions or isolated mockups. This Skill builds three to five genuinely different variants of one component, hosts them on the real page, and puts them behind a picker so you can compare and choose. ## Core Features & Use Cases - Axis-based variants: Each variant takes a distinct position on one primary axis (structure, density, emphasis, type, or voice) so differences are attributable and meaningful. - In-context picker: Variants render full-size on the real page with real content, switched via a URL search param and a floating picker control with keyboard navigation. - Quality floor and tradeoff table: Every variant must clear accessibility and responsive baselines, and results are presented as a tradeoff table without a marked favorite. - Use Case: You are designing a metric card for a dashboard and cannot decide between a dense and an editorial layout. The Skill builds both plus a quiet option on the actual dashboard page, letting you flip between them at different viewport widths before promoting one. ## Quick Start Ask the agent to build three variants of the component you are working on and put them behind a picker on the page where it will live.

Frequently Asked Questions about variant

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

FAQPage Schema
How do I compare multiple design variants of a UI component?▼

Build each variant as a distinct position on one design axis, such as density or structure, and host them on the real page behind a picker. Switch variants with a URL search param so each option is a shareable link you can judge at different viewport widths.

How many design variants should I create for one component?▼

Default to three variants and go up to five only when the design space is genuinely wide. Beyond five, people stop comparing and start scrolling, which defeats the purpose of the exercise.

Should design variants be reviewed in isolation or on the real page?▼

Variants should be judged on the page that will actually contain the component, with real chrome, neighbors, and realistic data. Isolated renderings hide spacing and context problems, and thumbnails distort the spacing you are usually choosing between.

What makes variants meaningfully different instead of just recolored?▼

Each variant must take a different position on one primary axis such as structure, density, emphasis, type, or voice. Variants that differ only in accent color or copy teach nothing, and varying every axis at once makes results unattributable.

What accessibility requirements apply to design variants?▼

Every variant must clear the same floor before entering the picker: accessible names on controls, full keyboard reachability, visible focus, no clipping at 320px, and no meaning carried by color alone. A direction that only works by breaking this floor should be dropped.

What happens after a variant is chosen?▼

The chosen variant is rebuilt properly where it belongs following the project's own conventions, and the other variants plus the picker harness are deleted. Until promotion, the harness and production code never import from each other.