Explore and compare multiple meaningfully different UI directions grounded in the current project's design system and 21st inspiration. Use when the user wants options, variants, concepts, a redesign direction, visual experimentation, or is unsure how a new interface should look. Trigger for requests such as "show me three directions", "explore alternatives", "what could this page look like", or "generate variants". Do not use for a straightforward implementation with an already-selected direct…
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Claude CodeNot declared
CursorNot declared
CodexNot declared
GitHub CopilotNot declared
WindsurfNot declared
Gemini CLINot declared
ClineNot declared
OpenCodeNot declared
Repository health
Stars4
LicenseLICENSE
Default branchmain
Open issues0
Status
Active
Package contents
Files included with this skill beyond the listing page.
skill mdSKILL.md2,218 B
docsSUMMARY.md2,147 B
History
First recorded snapshot · 237 installs
SKILL.md
Explore grounded UI directions
Create real choices without abandoning the project's visual identity.
Workflow
Read .21st/design.json and the relevant product UI. If context is missing,
run 21st init --design-context.
Search 21st for multiple relevant references before generating:
``bash 21st search "<interface and product context>" --context auto ``
Define three named directions. Each direction must differ on at least two
meaningful axes such as hierarchy, information density, navigation model, content emphasis, interaction pattern, or composition. Color-only variants do not count.
Keep shared constraints fixed: real stack, tokens, brand assets, required
content, accessibility, and responsive behavior.
Generate or implement comparable previews. Prefer:
``bash 21st generate "<goal plus fixed constraints>" --context auto --variants 3 ``
Present the options together when the host supports a picker. Otherwise give
each option a preview/deep link and a compact comparison.
Recommend one direction with concrete tradeoffs, but let the user choose.
After selection, remove abandoned local variants and record the decision in
.21st/design.json.
Direction contract
For every direction provide:
a short, descriptive name;
the core idea and intended user effect;
the 21st/project references used;
what stays consistent with the project;
two or more meaningful differences;
accessibility or responsive risks;
the best-fit scenario.
Do not generate random style mutations. Every difference must support a product or usability hypothesis that a user can evaluate.