메뉴
Review UI changes for design-system compliance, reusable component routing, token usage, and interaction consistency.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | design-system-review |
| description | Review UI changes for design-system compliance, reusable component routing, token usage, and interaction consistency. |
Use this skill after UI or component changes in projects with a shared design system.
AGENTS.md, CLAUDE.md, DESIGN.md, and DESIGN_REVIEW.md.src/design-system, src/components, src/styles, Storybook canvases, and UI tests.src/design-system/index.ts as the public component-library API.@/design-system.src/components/ui and src/components/shared stay implementation owners for primitives and shared building blocks.src/styles/global.css tokens or documented exception palettes.DESIGN.md.aria-* state, disabled behavior, tooltips, and loading/status labels stay intact after refactors.Run the narrowest relevant checks first, then the repository gate before completion:
mise run test:unit:dom
mise run test:e2e
mise run check
For browser-visible changes, also run mise run app:dev:browser and exercise the reader, settings modal, command palette, and subscriptions workspace with click and keyboard flows.
総合判定: OK | 調整推奨 | 大幅修正推奨
- Design-system routing: OK | 要修正
- Token usage: OK | 要修正
- Component reuse: OK | 要修正
- Interaction/a11y: OK | 要修正
- Storybook/tests: OK | 要修正
優先修正:
1. ...
2. ...
3. ...
Hand the current work to another agmsg agent — write a handoff doc, send its path as one line.
Use when adding, closing, or pruning entries in a repository's `TODO.md`, when moving finished work into `CHANGELOG.md`, or when setting up local task tracking for a repository that has no tracker. Do not use for entrypoint-docs drift review (`docs-entrypoint-review`), for cutting a release version section or tag (the repository's release workflow), for manager-facing work reports (`work-log-maintenance`), or for commit splitting (`atomic-commit`).
JEY workspace 固有の Linear 運用ルール: issue のプロジェクト自動ルーティング、ラベル/タイトル/取引ログの書式、Asana からの移行マッピング、ガードレール。CRUD 自体は Linear MCP tools を使い、MCP が使えない環境や MCP に無い操作のみ GraphQL スクリプトへフォールバックする。Use when creating or editing Linear tasks, choosing a project or label, migrating task notes from Asana, or appending transaction logs (date/payment/price) to an existing issue.
Curate external agent collections into this APM workspace. Use when evaluating whether an outside agent repository can be installed through APM, importing selected agents into catalog/agents, recording provenance, or refreshing curated agents from upstream.
Select and run expert review lanes for UI, forms, design specifications, accessibility, and multi-device product quality when ordinary /review or code review is too shallow.
高級モデル(Claude Fable/Opus、Codex sol)のセッションで実装作業を受けたとき、 自分で書かずに安価な Worker モデルへ委譲する Orchestrator-Worker 運用。 Use when the user asks to implement, fix, refactor, add tests, or migrate code; when a task spans multiple files or independent subtasks that could run in parallel; or when another skill needs the delegation-vs-inline decision or the model tier mapping.