47 tagged design-critique, measured the same way as everything else here.
Browse within: color-theory 39accessibility 7design-review 7
Skill Claude CodeCodex
Build taste through volume of output, deliberate failure, and speed. Taste cannot be developed by watching. It's sharpened by making, failing, and making again. Use when designing practice routines, breaking through creative blocks, or helping someone move from analysis to execution.
Skill Claude CodeCodex
Use taste as a competitive moat and business advantage. In the AI and vibe-coding era, execution is commoditized. Taste is the defensible edge. Use when advising founders on product differentiation, building product culture, evaluating why some products win despite fewer features, or understanding taste as a strategic…
Skill Claude CodeCodex
Navigate the gap between what you can see and what you can make. The Ira Glass gap. Use when a designer is frustrated by the distance between their taste and their output, when mentoring someone through a creative plateau, or when someone is considering quitting because their work doesn't match their vision.
Skill Claude CodeCodex
Amir Salihefendic (Todoist/Doist) design critique — calm technology, daily-use sustainability, anti-bloat. Brutally honest UX/UI feedback focused on productivity and the day-500 experience. Scores on 5 principles and implements fixes.
Skill Claude CodeCodex
Full UX/UI design review panel — 6 opinionated design leaders (Jony Ive, Amir Salihefendic, Jesse Patel, Joe Gebbia, Katie Dill, Notion Designer) critique your design with brutal honesty, deliberate together, score on 5 principles, and implement fixes. Works with .pen files, HTML/CSS/JS projects, and Figma.
Skill Claude CodeCodex
Jesse Patel (WorkFlowy) design critique — radical simplicity, one interaction pattern, keyboard-first. Brutally honest UX/UI feedback focused on reducing concept count and interaction complexity. Scores on 5 principles and implements fixes.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: