21st-dev/skill

21st-ui-review

Review existing UI against the project's design context, accessibility expectations, responsive behavior, interaction quality, and high-confidence production rules.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/21st-dev/skill --skill 21st-ui-review

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Review UI with evidence

Separate deterministic defects from subjective design recommendations.

Workflow

  1. Read .21st/design.json, project instructions, and the relevant source.
  2. Run the deterministic review first:
bash
   21st review <path>
   21st review <path> --json
  1. Inspect the actual component composition and runtime states. Validate claims

against code rather than inferring behavior from names.

  1. Group findings into:
  • deterministic defects;
  • design-system drift;
  • accessibility and interaction defects;
  • responsive risks;
  • subjective product/design recommendations.
  1. Prioritize by user impact and include exact file and line attribution.
  2. Use 21st review <path> --fix only for deterministic, low-ambiguity fixes.

Never silently redesign, change brand identity, or alter product behavior.

  1. Run relevant project tests after fixes and rerun review to prove resolution.

Review priorities

  • semantic controls and accessible names;
  • keyboard access, focus visibility, and dialog/menu behavior;
  • image alternatives and meaningful labels;
  • touch target size and disabled/loading states;
  • responsive overflow and fixed-width assumptions;
  • reduced-motion handling;
  • hardcoded visual values that conflict with project tokens;
  • duplicate primitives instead of existing components;
  • inconsistent typography, radius, spacing, shadows, and icons;
  • fake data, placeholder copy, or missing empty/error states.

Output

Lead with actionable findings ordered by severity. Keep subjective suggestions clearly labeled. If no issue is proven, say so and state what was inspected.

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
21st-dev
コミュニティ

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

1時間の導入数
3
GitHub Stars
42
更新日
9月9日
21st-dev
コミュニティ

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

1時間の導入数
3
GitHub Stars
42
更新日
9月9日
21st-dev
コミュニティ

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

1時間の導入数
2
GitHub Stars
26
更新日
9月9日
21st-dev
コミュニティ

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

1時間の導入数
3
GitHub Stars
23
更新日
9月9日