Menu
Independently reviews design packets for evidence, coherence, accessibility, completeness, specificity, and engineering readiness.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | design-review |
| description | Independently reviews design packets for evidence, coherence, accessibility, completeness, specificity, and engineering readiness. |
Review the selected design, not discarded alternatives. Apply these criteria:
DR-EVIDENCE: claims and product decisions are grounded or labeled.DR-FIT: direction is specific to audience, content, risk, and product category.DR-COHERENCE: typography, palette, layout, components, imagery, and motion express one thesis.DR-UX: journeys, hierarchy, recovery, responsive behavior, and system states are complete.DR-A11Y: WCAG 2.2 AA intent, keyboard, focus, contrast, semantics, reflow, touch, status, and reduced motion are actionable.DR-SYSTEM: primitive, semantic, and component tokens are implementable and preserve existing system decisions.DR-HANDOFF: engineering invariants, permitted variation, validation journeys, and unknowns are explicit.Return one self-contained DESIGN_REVIEW_RESULT packet through END_DESIGN_REVIEW_RESULT with verdict: PASS | NEEDS_REVISION | BLOCKED, findings:, reviewed_direction:, and remaining_limits:. Every finding includes criterion, severity, evidence, impact, and the smallest bounded remediation. Style preference alone is advisory. One evidence-backed revision is allowed; do not create an open-ended polish loop.
Screenshot-first visual end-to-end validation policy for browser-rendered UI and webview jobs after verifier approval.
Default engineering workflow. Classify a technical request, route it through the native T1/T2/T3 engineering fleet, and return only independently verified completion to the orchestrator.
Safely operate Claude Code's opt-in advanced capabilities—sessions, worktrees, agent teams, Skills, MCP, plugins, hooks, Channels, schedules, goals, and Agent SDK integrations—when the user explicitly asks for one. Do not use for an ordinary build request.
Routes selective local Codex plan, code, verification, and visual judgment with evidence-backed blocking and strict cost caps.
Shared evidence, accessibility, context, and handoff rules for the local design-agent fleet.
Produces contextual creative theses and bounded visual directions without generic model defaults.