# Design QA

> Use when the user wants visual QA, screen QA, responsive QA, polish review, pre-launch design review, or a structured check of an implemented UI or design artifact. Also use when the user says review this UI, check mobile polish, verify the screen, or make sure the design feels consistent and complete.

- Skill: `newmindsgroup/design-qa` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add newmindsgroup/design-qa`
- Raw SKILL.md: https://api.skillmd.com/api/skills/newmindsgroup/design-qa/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: MIT
- Author: newmindsgroup (https://skillmd.com/u/newmindsgroup)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/newmindsgroup/design-qa

---


# Design QA

Use this skill to standardize visual and UX quality checks after a design or implementation exists.

## Read First

- `/Users/newmindsgroup/.codex/knowledge/design-reviews/design-qa-checklist.md`
- `/Users/newmindsgroup/.codex/knowledge/design-reviews/visual-anti-pattern-checklist.md`
- `/Users/newmindsgroup/.codex/knowledge/ux-patterns/states-heuristics.md`
- `/Users/newmindsgroup/.codex/knowledge/visual-core/typography-rules.md`
- `/Users/newmindsgroup/.codex/knowledge/visual-core/spacing-radius-elevation.md`

Use screenshots, browser captures, or Figma screenshots when available. Prefer screenshot-driven review over abstract judgment.

## Scope

- visual hierarchy
- CTA prominence
- spacing consistency
- mobile and desktop behavior
- state coverage
- accessibility basics
- overall polish

## Workflow

1. Identify the surface and artifact type.
2. Review the UI against the checklist and style defaults.
3. Prioritize launch blockers before polish notes.
4. Separate visual, UX, and responsive findings only when it improves clarity.

## Outputs

- prioritized QA findings
- launch blockers
- polish recommendations