agentsclimarketplace

Critique visual hierarchy

Skill Infrasity-Labs/dev-gtm-claude-skills/product-designers/critique-visual-hierarchy

Critique a screen's visual hierarchy — entry point, eye flow, weight distribution, and emphasis.From its SKILL.md

Install
npx -y skills add Infrasity-Labs/dev-gtm-claude-skills --skill critique-visual-hierarchy

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

2.3 KB, 457 tokens by cl100k_base, as published. Nobody here has run it

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

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,852. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.