AGENT SKILL

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).

License 许可
MIT
最近更新
2026-11-04
Stars
★ 0
Forks
0

01 前言 Front Matter

name
critique-visual-hierarchy
description
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).
disable-model-invocation
true

02 资源文件 3

03 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

04 同仓库更多 Skills

jorgesolerrr
jorgesolerrr/skills

explainroo

Make an explainer video (MP4) with a voice-over using explainroo. The voice is made on this computer and no API key is needed. Use when the user asks for an explainer, how-to, walkthrough, launch or tutorial video, an animated diagram with a voice-over, or a short for YouTube, Reels or TikTok.

★ 0
jorgesolerrr
jorgesolerrr/skills

unslop

Cut AI tells from prose a human will read. Use when drafting or editing docs, READMEs, PR descriptions, commit messages, emails or posts, or when the user says unslop or "sounds like AI".

★ 0
jorgesolerrr
jorgesolerrr/skills

technical-writing

Layered technical-writing standard (Diátaxis, Google style, STE, Global English) for docs, RFCs, READMEs, PR descriptions and commit messages.

★ 0
jorgesolerrr
jorgesolerrr/skills

no-comments

Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.

★ 0
jorgesolerrr
jorgesolerrr/skills

ponytail

Lazy senior dev mode: the smallest change that fully solves the task, and a reply a busy human understands in one read. Use on any coding task (writing, fixing, refactoring, reviewing, choosing dependencies) and when the user says "ponytail", "be lazy", "simplest solution", "yagni", or complains about over-engineering or bloat. Levels: lite, full (default), ultra.

★ 0
jorgesolerrr
jorgesolerrr/skills

ponytail-review

Quality review of a change: is the logic right, is it safe, does it hold under real load, is risky code tested, is it fast enough, and is every line needed. Reads the connected code, not only the diff. Each finding is explained in plain English. Use for "review this", "code review", "review the last commit", "review my PR", "is this over-engineered", /ponytail-review.

★ 0