skilly. Buy ad slot
All skills
Design · Frontend / AGENT SKILL

critique-visual-hierarchy

owl-listener/designer-skills
1.6K installs 2.7K GitHub stars
0

Review screen hierarchy through entry points, eye flow, visual weight, and emphasis.
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).

BEFORE YOU INSTALL

Understand the trade-offs.

SECURITY REVIEW

Not yet assessed

Review the original instructions and requested permissions before installing.

No security review is available for this catalog entry yet.

SKILL QUALITY

Not yet assessed

How clearly the skill guides your agent, how complete its workflow is, and how you can check the outcome.

No quality assessment is available for this catalog entry yet.

The full skill.

Original instructions from the publisher’s 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?
- Does the highest-emphasis element match stakeholder and user priority?
## Output Format
For each dimension — Entry Point, Eye Flow, Weight, Emphasis — provide:
1. **Observation** — what you see (neutral, factual)
2. **Problem** — what is broken and why it matters
3. **Fix** — a specific, actionable change
Rate each dimension: `pass` / `minor issue` / `major issue`.
## Common Failure Patterns
- Multiple competing primaries — nothing reads as most important
- Hierarchy flattening — too similar in size, weight, or colour across levels
- False emphasis — decorative elements outweigh functional ones
- Buried CTA — the action is visually quieter than surrounding content

Skill folder

Files included alongside SKILL.md in the publisher’s repository.