design-critique

Evaluate UI and wireframe designs against established design rules.

Updated Jun 1, 2026
One-click install
npx skills add https://github.com/j-cogburn/d3 --skill design-critique-j-cogburn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-critique
Source: https://github.com/j-cogburn/d3/tree/main/tests/project-t01/.d3/skills/design-critique
Command: npx skills add https://github.com/j-cogburn/d3 --skill design-critique-j-cogburn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design feedback is often vague and subjective ("I don't like this") instead of actionable, leading to slow, unproductive design reviews and inconsistent UI quality. This Skill enforces structured, principle-based critique that ties every finding to established UI/UX rules, so teams get clear, fixable guidance instead of unhelpful opinions.

Core Features & Use Cases

  • Principle-Led Critique Framework: Ties every design finding to established rules including visual hierarchy, Gestalt laws, reading patterns, colour theory, and spacing standards, eliminating subjective feedback.
  • Standardized Finding Format: Structures every observation as Observation → Principle → Impact → Recommendation, so every issue comes with a clear, specific, actionable fix.
  • Use Case Example: Use this Skill when reviewing a new e-commerce checkout wireframe to catch hierarchy issues, contrast failures, and spacing inconsistencies before development starts, or when auditing a shipped mobile app screen for accessibility and visual quality gaps as part of a /audit ux workflow.

Quick Start

Use the design-critique skill to evaluate the attached SaaS dashboard wireframe for visual hierarchy, colour contrast, and spacing consistency issues.

Frequently Asked Questions about design-critique

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I give actionable UI feedback instead of subjective design critique?

To give actionable UI feedback, use a structured critique framework that ties every design finding to established rules like visual hierarchy, Gestalt laws, and colour theory, structuring observations into Observation, Principle, Impact, and Recommendation formats for clear fixes.

Can I use structured design critique to evaluate wireframes before implementation?

Yes, you can use structured design critique for wireframe evaluation to catch visual hierarchy issues, contrast failures, and spacing inconsistencies before development starts, applying principle-based checklists to ensure actionable, severity-rated feedback.

What design principles are checked during a UI audit?

A UI audit checks visual hierarchy, Gestalt principles, reading patterns, colour contrast, and spacing consistency, ensuring every identified flaw references an established design rule to eliminate vague or subjective feedback.

Does this structured UX review approach work for auditing shipped mobile apps?

Yes, this structured UX review approach works for auditing shipped mobile app screens to identify accessibility and visual quality gaps, providing standardized finding formats and red flag detection as part of a comprehensive UX quality check.

What is the best way to format design findings for a wireframe evaluation?

The best way to format design findings is a standardized structure of Observation, Principle, Impact, and Recommendation, which ensures every issue comes with a specific, actionable fix tied to an established design rule rather than personal opinion.

Why does my design review lack consistent UI quality standards?

Your design review likely lacks consistent UI quality because it relies on subjective feedback, which can be fixed by enforcing principle-based design critique that requires every finding to reference established rules and provides standardized checklists for visual hierarchy and colour contrast.