variant

Generates multiple UI component variants behind a URL-driven picker for comparison.

Updated Jun 28, 2026
One-click install
npx skills add https://github.com/AO-HyS/aohys.com --skill variant-ao-hys
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: variant
Source: https://github.com/AO-HyS/aohys.com/tree/main/.agents/skills/variant
Command: npx skills add https://github.com/AO-HyS/aohys.com --skill variant-ao-hys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Choosing between UI design directions is hard when options only exist as abstract ideas or isolated mockups. This Skill builds several genuinely different versions of one UI piece directly into the real page, so you can flip between them with real content and pick one based on evidence. ## Core Features & Use Cases - Axis-Based Variants: Builds three variants that each take a distinct position on one primary axis (structure, density, emphasis, type, or voice) instead of superficial color tweaks. - URL-Driven Picker: Hosts variants on the real page with a floating picker controlled by a ?variant= search param, arrow keys, and number keys, making every variant a shareable link. - Accessibility Floor: Requires every variant to pass escalation triggers (accessible names, keyboard reachability, visible focus, no clipping at 320px) before entering the picker. - Use Case: You are unsure whether a dashboard metric card should be quiet, editorial, or dense. The Skill builds all three into the actual dashboard page with realistic data, presents a tradeoff table, and promotes your choice while deleting the harness. ## Quick Start Ask the AI to build three variants of the metric card component on the dashboard page so you can compare them with the picker.

Frequently Asked Questions about variant

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

FAQPage Schema
How do I compare multiple UI design variants in a real page?▼

Build each variant into the page that will actually contain the component and switch between them with a URL search param like ?variant=quiet. A fixed picker control sets the param, so every variant becomes a shareable link judged in real context.

How many UI variants should I build for one component?▼

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

What makes UI variants meaningfully different from each other?▼

Each variant should 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 produces unattributable results.

Can a UI variant skip keyboard navigation or focus states?▼

No. Every variant must clear an accessibility 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 the floor gets 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.