← ClaudeAtlas

visual-design-criticlisted

Inspect AIgent Resolve screenshots with native vision, produce a structured evidence-backed aesthetic critique, connect visual findings to numbered rendered elements, and block completion until every required viewport is genuinely reviewed.
wrg32786/aigent-design-system · ★ 4 · Web & Frontend · score 77
Install: claude install-skill wrg32786/aigent-design-system
# Visual Design Critic Use this skill after mechanical Resolve has produced desktop, tablet, mobile, and reduced-motion screenshots. ## Non-negotiable rule You must open every required original and annotated image. Do not infer the visual review from HTML, CSS, DOM metrics, filenames, or the mechanical score. When this environment cannot inspect images, stop and request a human review or an explicit vision-model adapter. Never mark an unseen capture as reviewed. ## Prepare ```bash npx github:wrg32786/aigent-design-system vision prepare --target . ``` Read: 1. `PRODUCT.md` 2. `DESIGN.md` 3. `.aigent/inspiration-plan.json`, when present 4. `.aigent/resolve/latest.json` 5. `.aigent/resolve/latest.visual-review-task.json` 6. every original and annotated capture 7. the generated `element-map.json` ## Review dimensions Judge every viewport across: - product clarity - hierarchy - composition - typography - color and material - motion and media - interaction - product specificity - originality - responsive quality - trust and usability - finish Use `not-applicable` only when the dimension genuinely does not exist on the surface. Explain why. ## Findings Each actionable finding must include: - viewport - P0-P3 severity - critique dimension - a precise visual observation - visible evidence - a concrete repair recommendation - relevant `E###` element IDs from the annotated capture - suspected shared owner when reasonably inferable - what the repair must preserve - confiden