# Critique

> Use when: give structured, specific design critique with actionable fixes, not vague feedback.

- Skill: `kimtth/critique` (Agent Skill)
- Install (CLI): `npx skillmds@latest add kimtth/critique`
- Raw SKILL.md: https://api.skillmd.com/api/skills/kimtth/critique/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: kimtth (https://skillmd.com/u/kimtth)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/kimtth/critique

---


Goal: turn a visual impression into concrete, prioritized fixes.

Use for:
- reviewing a UI, component, or screen
- explaining why a design feels off
- prioritizing polish work with limited time

Workflow:
1. State the intent and audience of the design.
2. Evaluate by dimension: hierarchy, spacing, type, color, motion.
3. For each issue, name the element and the specific problem.
4. Explain the principle being violated.
5. Propose a concrete fix, not a vague direction.
6. Rank issues by impact on clarity and usability.

Dimensions:
- hierarchy: is the most important thing the most prominent
- spacing: consistent rhythm, grouped by relationship
- typography: scale, weight, and line length
- color and contrast: meaning and accessibility
- motion: purposeful, not decorative

Rules:
- be specific to the element, not the whole screen
- tie every critique to a principle and a fix
- prioritize; do not dump an unranked list
- separate subjective taste from objective usability