본문으로 건너뛰기
cccskills
무료GitHub에 공개

design-qa-checklist

Create a checklist for checking whether an implemented interface matches its design specifications. Cover visual details, responsive layouts, interactions, content, accessibility, and required devices, then organize issue reporting, severity priorities, and verification of fixes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Build a QA checklist for verifying that a build matches the design. Use at implementation review. For the spec engineers build from, use `handoff-spec`.

실행 점수 미검증

설치 방법 보기

이럴 때 유용합니다

  • Preparing a developer's design self-review
  • Checking layouts across screen sizes
  • Reviewing keyboard access and assistive technology support
  • Documenting design differences and verifying fixes

포함된 파일(1)

  • SKILL.md2.1 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Plan A/B experiments to measure the effect of a design change. Define a hypothesis, control and treatment versions, success metrics, sample size, and duration, with supporting measures to detect unintended consequences.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Planning a comparison between current and proposed designs
  • Defining success metrics for a change
  • Estimating sample size and test duration
Owl-Listener/designer-skills3천2026년 9월 6일 업데이트

Assess an existing interface against WCAG 2.2 accessibility guidelines. Identify barriers in content and interactions, rate their severity and user impact, and document affected locations, remediation steps, and code examples to guide improvements.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Reviewing accessibility in an existing design or build
  • Checking keyboard access and assistive technology compatibility
  • Prioritizing fixes by severity and user impact
Owl-Listener/designer-skills3천2026년 9월 6일 업데이트

Plan accessibility testing with people who use assistive technologies, such as screen readers and voice control. Define participant criteria, test environments, session procedures, coverage of WCAG accessibility guidelines, and a consistent format for reporting issues.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Planning test sessions with assistive technology users
  • Defining participant recruitment criteria
  • Mapping key user flows to test environments
Owl-Listener/designer-skills3천2026년 9월 6일 업데이트

Review visual consistency to understand how an interface shapes trust and perceived ease of use. Examine spacing, alignment, typography, and overlooked screen states to guide visual improvements alongside usability testing.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Investigating poor feedback on a functional interface
  • Checking visual consistency before launch
  • Reviewing error, empty, and loading states
Owl-Listener/designer-skills3천2026년 9월 6일 업데이트

Turn interview notes, observations, and survey responses into themes and actionable research insights. Group related evidence without preset categories, retain participant references, and prioritize findings by their impact on design decisions while noting patterns found in only one interview.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Synthesize findings across multiple interviews
  • Organize observation notes and survey responses
  • Prioritize research insights for design decisions
Owl-Listener/designer-skills3천2026년 9월 6일 업데이트

Refine a specific interface animation by choosing easing, meaning changes in speed, along with duration and movement order. Use it to tune buttons, modals, transitions, or loading indicators so motion guides attention and communicates changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Tune how a modal enters and exits
  • Adjust button and toggle animations
  • Coordinate the order of related movements
Owl-Listener/designer-skills3천2026년 9월 6일 업데이트

Owl-Listener의 스킬 모두 보기

이 스킬의 문제 신고