visual-hierarchy-review
Skill4 starsChanged 3 months agoMITView on GitHub
Audit layout for focal point, contrast, rhythm, and CTA hierarchy. Use when visual hierarchy, does this layout read well, check contrast and rhythm, what should the eye see first, or layout review.
In this repository46 other files it gives its agents.
- accessibility-reviewSkill
- accessibility-runtime-auditSkill
- adaptive-component-behaviorSkill
- ai-feature-ux-patternsSkill
- behavioral-pricing-psychologySkill
- business-model-readingSkill
- business-model-thinkingSkill
- cognitive-load-heatmap-predictionSkill
- component-style-guideSkill
- cross-functional-reviewSkill
- dark-mode-theming-systemSkill
- dashboard-layout-patternsSkill
- dashboard-scaffolding-contractSkill
- design-drift-detectorSkill
- design-system-builderSkill
- design-to-code-handoffSkill
- design-tokensSkill
- error-boundary-resilience-designSkill
- flow-based-functional-testingSkill
- growth-impact-reviewSkill
- i18n-localization-strategySkill
- information-architectureSkill
- interactive-element-auditSkill
- kinematic-motion-choreographySkill
- micro-interaction-motion-designSkill
- module-registry-syncSkill
- mvp-scopingSkill
- perceived-performance-loadingSkill
- prd-traceability-matrixSkill
- product-discoverySkill
- product-strategySkill
- project-health-diagnosticsSkill
- qa-feedback-loop-orchestratorSkill
- responsive-breakpoint-strategySkill
- responsive-qa-auditSkill
- route-integrity-checkerSkill
- security-privacy-reviewSkill
- stakeholder-requirement-mappingSkill
- touch-gesture-interactionSkill
- typography-systemSkill
- usability-heuristics-checkSkill
- user-flow-mappingSkill
- user-research-synthesisSkill
- ux-chaos-monkeySkill
- visual-responsive-regression-testingSkill
- visual-style-extractorSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Every screen should have one primary focal point: the most important element.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Visual hierarchy is the order in which the eye processes a page. If everything is bold, nothing is bold. If everything is the same size, nothing is important. Hierarchy is created by contrast — in size, color, weight, and spacing — not by decoration.
1. Squint test
Blur the layout (mentally or literally). What stands out? The things that stand out are the visual priorities. If the wrong things stand out (decorative elements, secondary actions), the hierarchy is broken.
2. Check the focal point
Every screen should have one primary focal point: the most important element. What is it? Is it the biggest/boldest/most contrasted thing on the page? If not, fix it.
3. Verify size hierarchy
Headings > subheadings > body > captions. If two text elements are the same size but have different importance, one of them is wrong. Cross-reference with typography-system tokens.
4. Check color contrast ratios
Primary actions should be the most visually prominent color. Secondary actions should be visually subdued. Destructive actions should be visually distinct (red/warning). Disabled elements should be clearly muted.
5. Verify spacing rhythm
Spacing should create groups: related items are close together, unrelated items are far apart (Gestalt proximity). Check that section gaps > group gaps > item gaps. Consistent spacing rhythm creates a sense of order.
6. Check alignment
Everything should align to something. Ragged left edges = visual noise. Use the grid — if something breaks the grid, it should be intentional and obvious, not accidental.
7. CTA hierarchy
One primary CTA per view (filled, high-contrast). Supporting actions are secondary (outlined or text). Destructive actions are visually separated. If there are 3+ primary-styled buttons visible at once, the hierarchy is flat.
Output
Visual hierarchy audit: focal point assessment, size hierarchy check, contrast ratio check, spacing rhythm check, alignment check, CTA hierarchy check. Per-issue: observation → severity → fix recommendation.
Completion Criteria
- Squint test performed — primary focal point named explicitly
- Every screen's most important element confirmed as the visually dominant element
- Size hierarchy verified against typography-system token scale (no two elements of different importance at the same size)
- Color contrast ratios checked for primary, secondary, and destructive CTA variants
- Spacing rhythm verified: section gap > group gap > item gap at every level
- Alignment verified against grid — any grid breaks are intentional and documented
- CTA hierarchy verified: maximum 1 primary-styled CTA per view
- Every violation rated with severity (critical / major / minor) and a fix recommendation
Anti-patterns
- Treating contrast ratio issues as hierarchy issues — they are separate dimensions (accessibility vs. visual priority)
- Flagging a layout as broken when there is intentionally no single focal point (e.g., a gallery, a settings page) — flat hierarchy is sometimes correct
- Recommending font size increases as the default fix for hierarchy issues — weight, color, and spacing are often more effective
- Checking only headings and ignoring interactive element hierarchy (buttons, links, badges can break hierarchy too)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

