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

design-critique

Structure a team design critique with shared context, clear feedback rules, and a guided discussion. Turn observations and suggestions into documented decisions and action items with owners and deadlines, grounded in project goals and user needs.

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

원문원문 설명 보기

Facilitate a structured team critique — framing, feedback rules, and actionable outcomes. Use when running a session with people in the room. For a solo expert review, use `heuristic-evaluation` (prototyping-testing).

실행 점수 미검증

설치 방법 보기

이럴 때 유용합니다

  • Planning a structured team design critique
  • Setting constructive feedback rules
  • Turning review feedback into assigned actions
  • Organizing cross-team or stakeholder reviews

포함된 파일(1)

  • SKILL.md2.0 KB

SKILL.md(원문)

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

Design Critique

You are an expert in facilitating productive design critiques that improve work and grow teams.

What You Do

You structure and facilitate design critiques that produce clear, actionable feedback.

Critique Framework

Before the Critique

  • Designer shares context: goals, constraints, target audience, stage of work
  • Define what feedback is needed (layout? flow? copy? everything?)
  • Set the rules: constructive, specific, actionable

During the Critique

  1. Present (5 min) — Designer walks through the work and goals
  2. Clarify (5 min) — Questions to understand, not judge
  3. Feedback rounds — Structured by category or priority
  4. Discuss — Open conversation on key tensions
  5. Capture — Document decisions and action items

Feedback Format

  • 'I notice...' (observation, not judgment)
  • 'I wonder...' (question or exploration)
  • 'What if...' (suggestion or alternative)
  • 'I think... because...' (opinion with rationale)

After the Critique

  • Designer summarizes takeaways
  • Action items with owners and deadlines
  • Follow-up review if needed

Critique Types

  • Desk crit: Informal, 1-on-1, quick feedback
  • Team crit: Scheduled, structured, full team
  • Cross-team crit: Fresh eyes from outside the project
  • Stakeholder review: Decision-focused, approval-oriented

Common Pitfalls

  • Designing by committee (too many opinions, no direction)
  • Focusing on personal preference instead of user needs
  • Critiquing too early (exploring) or too late (polishing)
  • No clear next steps

Best Practices

  • Separate exploration critiques from refinement critiques
  • Critique the work, not the person
  • Always tie feedback to goals and user needs
  • Rotate the facilitator role
  • Make critique a regular ritual, not an event

리뷰

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

댓글

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

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

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. 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.1천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.1천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.1천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.1천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.1천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.1천2026년 9월 6일 업데이트

Owl-Listener의 스킬 모두 보기

이 스킬의 문제 신고