メニュー
Use for platform-agnostic UI/UX design or review work that needs a deterministic UIUX Pack. Also use for web, iOS, or Android UIUX work with the matching platform adapter.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
| name | uiux-core |
| description | Use for platform-agnostic UI/UX design or review work that needs a deterministic UIUX Pack. Also use for web, iOS, or Android UIUX work with the matching platform adapter. |
| metadata | {"short-description":"UI/UX core contract + deterministic review bundle"} |
Define a UI/UX contract and review workflow that always produces a deterministic UIUX Pack.
references/uiux-core.md.references/uiux-platform-adapters.md and apply only the matching platform section(s).uiux/YYYYMMDD-<slug>/ (or uiux/.config output_dir override when present).ui_contract.yaml first (constraints, rules, and any platform_overrides).ui_spec.json.auto_review.json, including platform-prefixed checks when applicable.diff_summary.md.The UIUX Pack exists with all four artifacts, and auto_review.json separates machine checks and human review items with explicit pass/warn/fail/unknown results.
Use when finishing a branch or PR after verification and review, including merge, PR publication, keep, discard, cleanup, local sync, and reporting merge or PR URLs with current git state.
Use when handling received code-review feedback on a PR or diff, including requested changes, inline comments, approvals, non-blocking notes, and disputed suggestions. Separates accepted fixes, refutations, deferrals, clarification needs, and merge handoff.
Use when preparing a focused code-review request for a PR or diff after implementation evidence exists, especially to package scope, reviewer focus, PR URL, verification, known risks, and deferred work without deciding final submit readiness.
Use before every submission to decide whether required checks, artifacts, and branch evidence are complete enough to submit.
Use when work is complex, long-running, multi-step, cross-boundary, likely to span multiple PRs/sessions, or needs handoff-ready planning under plans/.
Use when adding or changing Agent-facing workflows, generated prompts, collect plans, executable handoff artifacts, CLI workflows, controller/target-local workflow chains, or validation artifacts consumed by downstream reports. Do not use for ordinary code changes without an Agent-facing workflow or generated instruction surface.