21st-dev/skill

21st-ui-explore

Explore and compare multiple meaningfully different UI directions grounded in the current project's design system and 21st inspiration.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/21st-dev/skill --skill 21st-ui-explore

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

Explore grounded UI directions

Create real choices without abandoning the project's visual identity.

Workflow

  1. Read .21st/design.json and the relevant product UI. If context is missing,

run 21st init --design-context.

  1. Search 21st for multiple relevant references before generating:
bash
   21st search "<interface and product context>" --context auto
  1. 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.

  1. Keep shared constraints fixed: real stack, tokens, brand assets, required

content, accessibility, and responsive behavior.

  1. Create comparable previews. Check MCP get_usage.aiGenerationEnabled or

run 21st usage and read the 21st AI generation line. CLI 1.17.1+ also supports 21st usage --json. Only when AI is explicitly enabled, use hosted generation with available AI credits:

bash
   21st generate "<goal plus fixed constraints>" --context auto --variants 3

Otherwise, implement the previews with your own coding agent, grounded in 21st search and 21st get (MCP: search and get_component). Do not call or suggest hosted generate or iterate_generation without AI access.

  1. Present the options together when the host supports a picker. Otherwise give

each option a preview/deep link and a compact comparison.

  1. Recommend one direction with concrete tradeoffs, but let the user choose.
  2. 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.

Related by task

from this repository

More skills

All skills
21st-dev
Community

21st-cli-use

Search, install and pull code from the 21st.dev catalog with the 21st CLI (@21st-dev/cli): find React/shadcn components, themes and templates, print a component's code or a theme's CSS, install an item into the project, or generate a new component with 21st AI. Use whenever the user says "search/find a component/theme on 21st", "install our team's Button", "add @user/slug", "pull that component's code", "найди компонент на 21st", "поставь наш компонент", or wants to script catalog access from th

1h installs
3
GitHub stars
42
Updated
Sep 9
21st-dev
Community

21st-registry

Publish your own work to 21st.dev and manage it from the terminal with the 21st CLI (@21st-dev/cli): publish a React component to a team library, publish a CSS theme or a template listing, edit / unpublish / delete your published items, list and reopen existing component work, and read/replace your public profile page (bento board). Triggers when the user says "publish/share/upload this to 21st", "залей в наш регистр", "опубликуй компонент/тему/темплейт", "share with team", "make this reusable",

1h installs
3
GitHub stars
42
Updated
Sep 9
21st-dev
Community

21st-ui-build

Build or substantially change production UI using the current project's design context, existing components, and grounded 21st inspiration. Use when implementing a page, section, component, responsive redesign, or visual polish in an existing web project. Trigger for requests such as "build this UI", "implement this screen", "make this page production-ready", or "use 21st to create the interface". Use 21st-ui-explore first when the visual direction is intentionally undecided, and 21st-ui-review

1h installs
2
GitHub stars
26
Updated
Sep 9
21st-dev
Community

21st-ui-review

Review existing UI against the project's design context, accessibility expectations, responsive behavior, interaction quality, and high-confidence production rules. Use for UI audits, design QA, frontend review, accessibility review, consistency checks, or requests to find and safely fix visual defects. Trigger for requests such as "review this UI", "audit this page", "find design issues", "check responsiveness", or "fix obvious UX problems". Use 21st-ui-build when the request is primarily to cr

1h installs
2
GitHub stars
23
Updated
Sep 9