21st-dev/skill

21st-ui-build

Build or substantially change production UI using the current project's design context, existing components, and grounded 21st inspiration.

Ver código-fonte

Como usar

  1. Copie o comando e verifique o pacote antes de instalar no seu ambiente de agente.
  2. Consulte no original as ferramentas, credenciais e ambientes necessários.
  3. Descreva os dados de entrada e a entrega esperada; confira a saída com as fontes.
npx skills add https://github.com/21st-dev/skill --skill 21st-ui-build

Antes de começar

  • A instalação não inclui assinatura de modelo, franquia API ou acesso aos seus arquivos.
  • Estrelas e instalações indicam atividade, não um teste independente de qualidade ou segurança.
Documento original do Skill

Renderizado do repositório de origem, preservando títulos, exemplos, código, tabelas, links e imagens.

Build project-aware UI

Preserve the product's identity while using 21st supply to accelerate implementation.

Workflow

  1. Read .21st/design.json and .21st/DESIGN.md. If neither exists, run

21st init --design-context.

  1. Inspect the target route, its closest components, project instructions, and

existing tokens. Treat explicit project facts as stronger than generic taste.

  1. Search before generating:
bash
   21st search "<specific UI need>" --context auto
  1. Reuse installed project primitives first. Retrieve or install a 21st result

only when it reduces duplication or materially improves the result.

  1. If no result fits, 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, generate project-aware alternatives using available AI credits:

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

Otherwise, implement alternatives 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. Implement the selected direction in the project's real framework. Do not

paste sketch HTML when the project expects React components, tokens, or established APIs.

  1. Preserve responsive behavior, keyboard interaction, visible focus,

semantics, reduced motion, loading states, empty states, and error states.

  1. Run the project's checks and 21st review <changed paths>. Apply only safe,

deterministic fixes automatically.

Design rules

  • Prefer project tokens over new arbitrary values.
  • Prefer existing components over parallel lookalikes.
  • Preserve established density, radii, typography, iconography, and layout

rhythm unless the user explicitly requests a redesign.

  • Use real product copy and states when available.
  • Avoid decorative gradients, excessive cards, glass effects, huge headlines,

and animation unless supported by the project or requested.

  • Never claim a component, token, or capability exists without inspecting it.

Handoff

Report the direction used, reused 21st/project components, files changed, and verification performed. Record a durable visual choice in .21st/design.json under decisions when the user selects a new direction.

Relacionados por tarefa

do mesmo repositório

Mais Skills

Todos os Skills
21st-dev
Comunidade

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

Instalações / 1h
3
GitHub Stars
42
Atualizado
9 de set.
21st-dev
Comunidade

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",

Instalações / 1h
3
GitHub Stars
42
Atualizado
9 de set.
21st-dev
Comunidade

21st-ui-explore

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 directi

Instalações / 1h
3
GitHub Stars
23
Atualizado
9 de set.
21st-dev
Comunidade

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

Instalações / 1h
2
GitHub Stars
23
Atualizado
9 de set.