メニュー
Use for new UI, redesign, frontend implementation, screen or component review, responsive work, accessibility, generic AI appearance, or usability problems. Do not use for backend-only work.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/SiddheshKGupta/Escapement --skill enterprise-ui-reviewコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Use at the start of MATERIAL or PROGRAM work when the user has a rough request, unclear success criteria, hidden trade-offs or missing decisions. Ask only high-impact questions, recommend defaults and produce a better execution brief.
Use when a project needs persistent storage and no database technology has been chosen yet, or an existing choice is being reconsidered. Selects a database with stated trade-offs, then designs the schema and API surface together against that choice. Do not use for read-only analytics over an existing store -- see data-engineering.
Use when building dashboards, KPI tiles, management reports, or reconciliation views -- covers KPI breakdown completeness, the three-layer reporting model, and locale-correct currency/number formatting (symbol, digit grouping, unit scale) applied uniformly across every surface. Do not use for visual design decisions (colour, layout, typography) -- see design-system.
SOC 職業分類に基づく
SKILL.md を表示中
| name | enterprise-ui-review |
| description | Use for new UI, redesign, frontend implementation, screen or component review, responsive work, accessibility, generic AI appearance, or usability problems. Do not use for backend-only work. |
Review:
DESIGN.md;Read docs/standards/design-intelligence.md as the governing design authority. Use Impeccable for audit/hardening and Emil Kowalski skills for motion review when installed and relevant.
Use real browser evidence when available. Capture screenshots and commands as structured evidence.
This skill routes correctly at IMPLEMENT/VERIFY/POLISH for UI work, but routing only puts the checklist in front of an agent -- it doesn't force the agent to actually apply it before calling the work done. Run:
python scripts/ui_quality_gate.py <frontend-src-dir>
before closing a POLISH phase on UI-touching work. It scans for concrete,
detectable signals -- responsive breakpoints, motion transitions,
prefers-reduced-motion, :focus-visible, loading-state and error-state
handling -- the same items 3/4/7/8 above already name. A clean
report is not proof of good UX; it is proof those items were not silently
skipped the way frontend-implementation's own doctrine was, in practice,
skipped before this existed.