Use whenever the screens, UX, wording, feedback after actions, accessibility, or layout of frontend/ come up, even without the word "review" — delegates to the frontend-ux-reviewer agent, which runs the dev screens against the Lean CLI with Playwright and reports with evidence. Not for reviewing the domain model itself (that is the ddd skill's review).
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
レビュー本体は専任サブエージェント frontend-ux-reviewer。あなたは対象の確定 → 起動 → 中継だけ。
なし = 現在のブランチの frontend/ の差分とその画面の流れ / all = 全体 / a11y = アクセシビリティに寄せる / static = 画面を立てない / それ以外 = 画面名・観点の指定。
<default> は git symbolic-ref refs/remotes/origin/HEAD（無ければ main → master）。git merge-base <default> HEAD、git diff <base> --stat -- frontend/、git status --short frontend/。既定ブランチ上なら作業ツリーだけ。差分が空でも終わらない（UX は差分で完結しない）。cradle.json の ports（発行者・Lean CLI サーバ・dev 画面）が動いているか（ss -ltn）。動いているポートがこのプロジェクトのものか確かめる。
相手は Lean CLI（pnpm dev の既定）。REST を相手にしない（レビューの操作が実データを動かす）。backend も DB も要らない。
playwright の道具（mcp__plugin_playwright_playwright__*）が無ければ、その旨を伝えて静的レビューに落とす。frontend-ux-reviewer を起動（バックグラウンド可）。渡すのは: ルートの絶対パス、範囲（基点 SHA とブランチ）、作業ツリーの未コミット変更も対象、変更ファイル一覧、画面を立てて触ること（static なら立てない）、すでに動いているポート。
コードや diff の全文は貼らない。ss -ltn で確かめ、残っていれば止める。git status に lean/ frontend/ の差分が出ていないか確かめる。documents/ai-notes/（冒頭に「規約ではない」）。No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when adding or changing REST endpoints or the OpenAPI contract — deriving endpoints from the Lean commands and views, writing documents/codebase/openapi.yaml first, then regenerating the backend controller interfaces and the frontend client.
The English summary is being prepared. Showing the original description.
Use after a backend build succeeds or whenever authentication, authorization, actor/identity handling, external service calls (IdP, JWKS, DB, clock), logging, observability, configuration or error contracts are in play — delegates to the backend-design-reviewer agent for a design-quality review of the current branch.
The English summary is being prepared. Showing the original description.
Use when it is time to make the backend follow the Lean model — regenerate Kotlin from Lean, implement the generated interfaces (UseCase, QueryService, Repository, Entity), wire every generated contract test, make the build green, then run the design and SQL reviews. Backend comes after the human confirmed the screens.
The English summary is being prepared. Showing the original description.
Use when you need the current position in the Lean spec-driven pipeline, or any deterministic check of a Cradle project — status, golden regression, Lean layer walls, regeneration impact, unslop lint, ddd cleanup. Runs the scripts under scripts/ and reports their output verbatim.
The English summary is being prepared. Showing the original description.
Use to start a new product on Cradle or to add the Cradle skeleton to an existing repository — writes cradle.json, the project-facts instruction (.apm/instructions/project.instructions.md), documents/{ddd,ai-notes,infra-design,codebase} templates, CI, and a compiling Lean executable-spec scaffold with a minimal example domain, mockup and CLI.
The English summary is being prepared. Showing the original description.
Use when the product owner asks where the project stands, what to do next, or which phase of the Lean spec-driven pipeline is current — runs cradle status and proposes exactly one next step.
The English summary is being prepared. Showing the original description.