Design Qa Checklist
Install this when implementation is done and you need a systematic design QA checklist to prove the UI matches tokens, layout, states, and accessibility specs.
Overview
Design-qa-checklist is an agent skill most often used in Ship (also Build frontend, Launch distribution) that creates systematic QA checklists to verify implementations match design specifications.
Install
npx skills add https://github.com/owl-listener/designer-skills --skill design-qa-checklistWhat is this skill?
- Six QA dimensions: Visual Accuracy, Layout, Interaction, Content, Accessibility, and Cross-Platform
- Interaction coverage for default, hover, focus, active, disabled, transitions, and 44px minimum touch targets
- Accessibility checks for WCAG AA contrast, focus order, ARIA, screen readers, and reduced motion
- Content and state checks including truncation, empty states, loading, and production copy (no lorem ipsum)
- Responsive verification at breakpoints with overflow, clipping, and min/max width rules
- 6 QA categories: Visual Accuracy, Layout, Interaction, Content, Accessibility, Cross-Platform
- 44px minimum touch target called out in Interaction checks
Adoption & trust: 597 installs on skills.sh; 1.5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You shipped or are about to ship UI work but lack a structured way to confirm colors, spacing, states, and accessibility match the design system.
Who is it for?
Indie builders and designers verifying a SaaS or marketing site implementation against Figma or token docs before release or a redesign launch.
Skip if: Projects with no design spec to compare against, or teams that only need automated unit tests with no visual or UX criteria.
When should I use this skill?
Create QA checklists for verifying design implementation accuracy; when implementations need systematic comparison to design specifications.
What do I get? / Deliverables
You get a categorized design QA checklist your team can walk through to sign off visual, layout, interaction, content, accessibility, and cross-platform fidelity.
- Structured design QA checklist organized by Visual, Layout, Interaction, Content, Accessibility, and Cross-Platform
- Sign-off oriented verification items for states, breakpoints, and accessibility
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Design QA is verification before release; Ship/testing is the canonical shelf because the skill’s job is to validate built UI against design specifications, not to invent the design. Testing subphase covers structured verification passes—visual accuracy, interaction states, and accessibility—rather than one-off visual polish during initial Build.
Where it fits
Run a pre-release pass on dashboard components for token colors, shadows, and interaction states.
After implementing a settings page, generate a layout and content checklist before opening a PR.
Verify landing page hero, typography, and cross-browser behavior before a Product Hunt push.
Re-check marketing templates when copy or imagery changes to ensure truncation and empty states still match design.
How it compares
Produces human QA checklists for design fidelity, not a replacement for Figma-to-code codegen or Lighthouse-only performance audits.
Common Questions / FAQ
Who is design-qa-checklist for?
It is for designers and solo builders who need to verify that developers—or their agent—implemented spacing, tokens, states, and accessibility as specified.
When should I use design-qa-checklist?
Use it in Ship during testing before launch; in Build when reviewing a finished screen against specs; and in Launch when polishing distribution pages for responsive and accessibility compliance.
Is design-qa-checklist safe to install?
It is checklist-generation guidance without executing your app; confirm trust via the Security Audits panel on this Prism catalog page before installing.
SKILL.md
READMESKILL.md - Design Qa Checklist
# 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