Skip to content
Back to skills

Variant

ASecurity

Build several genuinely different versions of one UI piece behind a picker on the real page. Use when the user asks which version, wants variants, alternatives, or to flip between design directions.

  • 3 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 5, 2026
designgo

Works with

  • cli

Security analysis

A100/100

Pro scans all 4 files and shows the line behind each finding

Scanned September 22, 2026

npx -y skills add twikus/claude-configuration --skill variant --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Variant?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Variant
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/twikus-variant/badge)](https://www.skillsdirectory.com/skills/twikus-variant)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: variant
description: Build several genuinely different versions of one UI piece behind a picker on the real page. Use when the user asks which version, wants variants, alternatives, or to flip between design directions.
disable-model-invocation: true
---

Build three versions of one piece of UI that differ on purpose. Host them on the real page behind a picker and stop so the user chooses.

Scope one piece. Restate what it is, where it renders, and what it must do. If the brief spans several, name the one the others hang off and offer the rest as later runs.

Read the styling system, tokens, density, voice, and the page the piece lives on. With no project, use neutral grays, one accent, and the system font stack.

Pick one primary axis and put each variant on a different position. Secondary choices follow from it:
- Structure or Density → `better-layout`
- Emphasis → `better-colors`
- Type → `better-typography`
- Voice → `better-writing`

Name each variant by its direction (`Quiet`, `Editorial`, `Dense`). Go to five only when asked or the space is genuinely wide.

Before a variant enters the picker it must clear this floor: accessible name, keyboard parity, visible focus, no clip at 320px, no meaning on color alone. Drop a direction that can only work by breaking it.

Host on the page that will contain the piece, with real chrome, neighbours, and product-shaped content. Select with `?variant=<name>`. Open `picker.md` for the picker spec. Render one variant at a time, full size. If no page can host it, one self-contained HTML file with the same picker.

Flip through every variant first. Return a tradeoffs table (axis position, right when, costs). Say where the picker is running, which key flips it, and which width you judged at. Never mark a favourite. If asked directly, answer from usage frequency and product personality. On a choice, ship that variant in place, then delete the others and the harness. Asked for another round, keep the harness and pick new positions. Until promotion, the harness never imports from production and production never imports from the harness.

Do not review existing UI; that is `better` or `interface-review`.

Files in this skill

  • SKILL.md6.1 KB
  • agents/openai.yaml345 B
  • assets/codex-icon.svg482 B
  • picker.md2.7 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…