variant

Builds multiple UI variants of one component behind a URL-driven picker for comparison.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/squidllee/skills --skill variant-squidllee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: variant
Source: https://github.com/squidllee/skills/tree/main/variant
Command: npx skills add https://github.com/squidllee/skills --skill variant-squidllee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Choosing between design directions for a UI component often stalls on vague opinions or trivial differences like accent color. This Skill produces three genuinely different variants of one piece of UI, hosts them on the real page behind a picker, and hands the decision back to you with stated tradeoffs. ## Core Features & Use Cases - Axis-based variation: Each variant takes a distinct position on one primary axis (structure, density, emphasis, type, or voice) so differences are attributable and learnable. - Real-page hosting with picker: Variants render full-size in the actual page with real content, switched via a URL search param and a fixed picker control defined in picker.md. - Accessibility floor and promotion workflow: Every variant must clear accessibility triggers before entering the picker, and once you choose, the winner is built properly and the harness is deleted. - Use Case: You are redesigning a metric card on a dashboard. The Skill builds Quiet, Editorial, and Dense versions on the live page, lets you flip between them at 375px and 1440px, then presents a tradeoff table so you can pick one. ## Quick Start Build three variants of the dashboard metric card with a picker so I can compare them and choose one.

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 axis such as structure or density, host them on the real page, and switch between them with a URL search param like ?variant=quiet. A fixed picker control steps through the set so every variant is a shareable link.

How many UI variants should I generate for a design decision?▼

Default to three variants and go to five only when asked or when the design space is genuinely wide. Past five, people scroll instead of comparing, and the variants stop teaching anything.

Why should UI variants differ on only one axis?▼

Varying every axis at once produces unattributable results where you learn which you liked but not what made it work. Picking one primary axis, such as structure or density, lets secondary choices follow coherently so the next piece benefits from the lesson.

Can I judge UI variants in isolation or as thumbnails?▼

No, variants should render full-size on the page that will actually contain the piece, with real chrome, neighbours, and realistic data. Isolation and thumbnails distort spacing and scale, which are usually the properties being chosen between.

What accessibility requirements apply to design variants?▼

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

What happens after I pick a winning UI variant?▼

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 never imports from production and production never imports from the harness.