Critique Visual Hierarchy

Critique a rendered screen's hierarchy — entry point, eye flow, weight distribution, and emphasis. Use when attention lands in the wrong place. For establishing hierarchy in new work, use `visual-hierarchy` (ui-design).

3,414 stars 447 forksFrontend & Design Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add Owl-Listener/designer-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add Owl-Listener/designer-skills --skill critique-visual-hierarchy
Manual install
git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git /tmp/designer-skills
mkdir -p ~/.claude/skills
cp -r /tmp/designer-skills/visual-critique/skills/critique-visual-hierarchy ~/.claude/skills/critique-visual-hierarchy

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Critique Visual Hierarchy
You are an expert in visual hierarchy and screen-level design critique.
## What You Do
You analyse a screen to identify whether hierarchy is clear, intentional, and aligned with user goals. You flag problems and suggest targeted fixes.
## Critique Dimensions
### Entry Point
The first element that captures the eye. Evaluate whether it is the *most important* thing on screen.
- Is there a single dominant element, or does attention scatter?
- Does size, contrast, or position establish the entry point clearly?
- Does the entry point match the primary user goal for this screen?
### Eye Flow
The path a user's eye travels after landing. Evaluate whether the path is deliberate and efficient.
- Does the layout follow an F-pattern, Z-pattern, or intentional reading order?
- Are there dead ends, loops, or confusing jumps?
- Does flow lead naturally to the primary call-to-action?
### Weight
The relative visual importance of each element. Evaluate whether weight is distributed purposefully.
- Are size differentials at least 1.5× between hierarchy levels?
- Is bold/heavy type used sparingly so it retains signal value?
- Do background fill, stroke weight, and iconography add or fight the hierarchy?
### Emphasis
Specific elements that demand extra attention. Evaluate whether emphasis is earned and singular.
- Is there exactly one primary emphasis zone per view?
- Are colour, contrast, or motion used to emphasise — or overused so they cancel out?
Read the full skill on GitHub

Details

Skill name
critique-visual-hierarchy
Path
visual-critique/skills/critique-visual-hierarchy/SKILL.md
License
MIT
Repo updated
5 September 2026

FAQ

What does the Critique Visual Hierarchy skill do?

Critique a rendered screen's hierarchy — entry point, eye flow, weight distribution, and emphasis. Use when attention lands in the wrong place. For establishing hierarchy in new work, use `visual-hierarchy` (ui-design).

How do I install the Critique Visual Hierarchy skill?

Claude Code plugin: /plugin marketplace add Owl-Listener/designer-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Critique Visual Hierarchy popular?

It lives in Owl-Listener/designer-skills, which has 3,414 GitHub stars and 447 forks.

Related skills

A B Test Design

3.4k

Owl-Listener/designer-skills

Design an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.

Testing & QA447

Accessibility Audit

3.4k

Owl-Listener/designer-skills

Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).

Frontend & Design447

Accessibility Test Plan

3.4k

Owl-Listener/designer-skills

Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).

Testing & QA447

Design Debt Audit

3.4k

Owl-Listener/designer-skills

Inventory and prioritise accumulated design inconsistencies across a product. Use when drift has built up over time. For token coverage specifically use `design-token-audit` (designer-toolkit); for WCAG gaps use `accessibility-audit` (design-systems).

Frontend & Design447

Critique Typography

3.4k

Owl-Listener/designer-skills

Critique a rendered screen's typography — scale usage, readability, consistency, and token compliance. Use when reviewing type on a screen. For defining the scale itself, use `typography-scale` (ui-design).

Frontend & Design447

Design Impact Reporting

3.4k

Owl-Listener/designer-skills

Communicate design's contribution to business and user outcomes in stakeholder language. Use when reporting results upward. For choosing the metrics in the first place, use `metrics-definition` (ux-strategy).

Frontend & Design447

Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.