- name
SKILL.md
技能檔案保留在發布者的儲存庫中。
在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add arla6ka/design.how --skill ui-review -a cursor -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add arla6ka/design.how --skill ui-review -a claude-code -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add arla6ka/design.how --skill ui-review -a codex -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add arla6ka/design.how --skill ui-review -a grok -y在 Grok Bot 聊天中傳送複製的訊息。Bot 會從 GitHub 取得這個 SKILL.md,並加入你所有 Bot 共用的技能中。
Install this skill: https://github.com/arla6ka/design.how/tree/HEAD/skills/ui-review來自發布者
The render is the evidence. A description, DOM text or source code only supports it. Severity, the 13 criteria and the edge cases are in references/criteria.md. An installed design system's own rules come first and count as agreed criteria.
build-design-system installed, build-design-system/scripts/capture.mjs does this behind a guard that blocks every write and saves each capture's accessibility tree. It needs --writes <file> listing the app's writes, or --no-backend, and writes only to its --out folder (keep that under .ui-review/). Otherwise use the host's browser tool and save the tree yourself. Run the project's accessibility scanner too when it has one.PerformanceObserver on event entries, each duration under 100 ms). Do not click anything that writes to shared data.blocking, should-fix, note or dismissed, naming who raised it and giving one line of reason. A finding raised by two reviewers on their own is the strongest signal. Dismiss nitpicks, hypotheticals nobody traced to a real call site, and "I would have done it differently". Within a bucket, put surfaces that write data first, then order by places hit. Without a panel, do the same alone.button 'Save changes' (settings-1280.png)), the width, and the evidence. A finding that rests on taste is dropped to Left out.blocking finding makes the verdict no, pending <the check>.:has(:focus-visible) leaves the focused element reporting no outline.The first line answers the ask in plain words. The ship line follows: Ready to ship: no. Enter in Email cancels the invite (blocking 1, should-fix 2, 3 questions for a person). Any blocking finding makes the verdict no, an inferred one no, pending <the check>, should-fix alone yes, with fixes, only notes yes.
Then, in order:
Fix Enter in Email so that it sends 1 POST).Run on its own, save the report to .ui-review/<date>-<flow>.md with captures beside it. When a coordinator asks for captures only, return the capture paths, widths and Coverage: line, and no findings. The chat reply gives the answer and ship lines, each command with its exit code, and one prompt the person can paste to take the next step.
Every finding has a criterion, a location, evidence and only the widths where it shows. Every probe has a result or a reason. The first line, the ship line and the summary agree. The last line reads Coverage: with the routes, widths, themes and probes measured, then what was not.
Use to critique a screen, flow, prototype or running build, accessibility included, and rank what is broken, such as "check this page before I ship", "is this flow ready", "is it accessible", keyboard
---name: ui-reviewdescription: Use to critique a screen, flow, prototype or running build, accessibility included, and rank what is broken…---# skills/ui-review/SKILL.md總覽
Use to critique a screen, flow, prototype or running build, accessibility included, and rank what is broken, such as "check this page before I ship", "is this flow ready", "is it accessible", keyboard or screen-reader checks, "it feels off on my phone" or "it feels janky". Not for token compliance, which is token-mapping.
常見問題
從發布者下載 skills/ui-review/SKILL.md,或複製路徑後開啟儲存庫。PlugMCP 只收錄這項技能,不代管檔案。
發布者將它存放在 https://github.com/arla6ka/design.how。
Claude、Cursor、Codex 和 Grok Build 可以讀取你從發布者儲存庫加入的 SKILL.md。在聊天中傳送技能的 GitHub 資料夾連結,Grok Bot 就會安裝它。