21st Ui Build

21st-dev/skill/skills/21st-ui-build

by 21st-dev15c7436c41dcNo license12 starsListed Oct 9, 2026Updated Oct 9, 2026Repository updated 4 weeks ago

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 for critique-only work.

Instructions only

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.

  2. Inspect the target route, its closest components, project instructions, and existing tokens. Treat explicit project facts as stronger than generic taste.

  3. Search before generating:

    bash
    21st search "<specific UI need>" --context auto
  4. Reuse installed project primitives first. Retrieve or install a 21st result only when it reduces duplication or materially improves the result.

  5. 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.

  6. 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.

  7. Preserve responsive behavior, keyboard interaction, visible focus, semantics, reduced motion, loading states, empty states, and error states.

  8. 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.

Source and attribution

Source:21st-dev/skillinskills/21st-ui-buildat commit15c7436

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

More from 21st-dev/skill

21st Ui Review

21st-dev

Reviews existing UI for accessibility, responsiveness, and design-system defects, with safe deterministic fixes.

Design & Creative12updated 4 weeks ago

21st Ui Explore

21st-dev

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 direction.

Awaiting classification12updated 4 weeks ago

21st Registry

21st-dev

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", "unpublish/edit/delete my component", "change its visibility", "find/open my old component or draft", "найди/открой мой старый компонент или драфт", "add this to my 21st profile/bento", "update my profile page", "обнови мой профиль на 21st", "добавь блок в бенто", "add controls/knobs to my demo", "сделай демо с контролами". For finding and installing existing items use `21st-cli-use`; for turning a project's design tokens into a theme use `21st-design-sync`.

Awaiting classification12updated 4 weeks ago

21st Design Sync

21st-dev

Reads a project's shadcn/Tailwind design tokens and publishes them as a public theme on 21st.dev.

Design & Creative12updated 4 weeks ago

21st Cli Use

21st-dev

Guides use of the 21st CLI to search, install, and pull React/shadcn components, themes, and templates from the 21st.dev catalog.

Software Development12updated 4 weeks ago

21st Ai

21st-dev

Generate and iterate on UI with 21st AI from the terminal via the `21st` CLI (`@21st-dev/cli`): sketch a UI from a prompt, preview the variants in the browser, edit any variant in place with a natural-language change, and pull the final code into the project. Use whenever the user wants to BUILD / SKETCH new UI ("sketch a pricing page", "generate a hero with 21st", "make me a <X> section"), ITERATE on a generated draft ("edit the third variant", "add a toggle to that take"), or GRAB the code of a draft ("pull that variant's code", "сгенери UI на 21st", "поправь третий вариант", "забери код того наброска"). For finding/installing existing components use the `21st-cli-use` skill; to publish your own, `21st-registry`.

Awaiting classification12updated 4 weeks ago