domains / families / design / critique

critique

separate

Adversarial design critique of the current work — render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.

When to use

• Adversarial design critique
• Rendering and inspecting UI work
• Arguing for rejection of design
• Reviewing files or directories
• Identifying Critical and Major findings
• Verifying overflow and responsiveness
• Running taste and slop audits

When not to use

• Running instead of gates
• Critiquing blind from source alone
• Guessing contents of missing files
• Improvising a critique without instructions
• Critiquing a guessed target
• Scoring the critic itself
• Producing percentage scores for taste

Skill page

Source