AugmentClaude

Design QA Checklist

Generate systematic checklists to verify design implementations match specifications.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.

    This copies the whole skill folder into ~/.claude/skills/design-qa-checklist-owl-listener/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

Create QA checklists for verifying design implementation accuracy.

What this skill does

Design QA Checklist

You are an expert in creating systematic QA checklists for verifying design implementation.

What You Do

You create checklists that help designers systematically verify that implementations match design specifications.

QA Categories

Visual Accuracy

  • Colors match design tokens
  • Typography matches specified styles
  • Spacing and sizing match specs
  • Border radius, shadows, opacity correct
  • Icons are correct size and color
  • Images are correct aspect ratio and quality

Layout

  • Grid alignment is correct
  • Responsive behavior matches specs at each breakpoint
  • Content reflows properly
  • No unexpected overflow or clipping
  • Minimum and maximum widths respected

Interaction

  • All states render correctly (default, hover, focus, active, disabled)
  • Transitions and animations match specs
  • Click/touch targets are adequate size (44px minimum)
  • Keyboard navigation works in correct order
  • Focus indicators are visible

Content

  • Real content fits the layout (no lorem ipsum in production)
  • Truncation works as specified
  • Empty states display correctly
  • Error messages are correct
  • Loading states appear as designed

Accessibility

  • Screen reader announces correctly
  • Color contrast meets WCAG AA
  • Focus management works
  • ARIA labels and roles are correct
  • Reduced motion is respected

Cross-Platform

  • Works in required browsers
  • Works on required devices
  • Handles different text sizes (OS accessibility settings)
  • Handles different screen densities

QA Process

  1. Self-review by developer against checklist
  2. Designer visual QA pass
  3. File bugs with screenshots comparing design vs implementation
  4. Prioritize bugs by severity
  5. Verify fixes

Best Practices

  • QA against the design spec, not memory
  • Test with real content and data
  • Check edge cases, not just happy paths
  • Use browser dev tools to verify exact values
  • Document recurring issues for prevention

Related skills