Design Audit
AThevon/genjutsu
Design audit checklist - motion gaps, accessibility, color consistency, responsive, performance.
Establish hierarchy through size, weight, colour, spacing, and position so the eye lands in the intended order.
Install Visual Hierarchy
$ npx skills add Owl-Listener/designer-skills --skill visual-hierarchy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/designer-skills visual-hierarchy --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/ui-design/skills/visual-hierarchy .claude/skills/visual-hierarchy && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "visual-hierarchy" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/ui-design/skills/visual-hierarchy into .claude/skills/visual-hierarchy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "visual-hierarchy", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Owl-Listener/designer-skills/tree/main/ui-design/skills/visual-hierarchyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Owl-Listener/designer-skills --skill visual-hierarchy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/designer-skills visual-hierarchy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/ui-design/skills/visual-hierarchy .agents/skills/visual-hierarchy && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "visual-hierarchy" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/ui-design/skills/visual-hierarchy into .agents/skills/visual-hierarchy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "visual-hierarchy", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/designer-skills --skill visual-hierarchy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/designer-skills visual-hierarchy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/ui-design/skills/visual-hierarchy .cursor/skills/visual-hierarchy && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "visual-hierarchy" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/ui-design/skills/visual-hierarchy into .cursor/skills/visual-hierarchy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "visual-hierarchy", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Owl-Listener/designer-skills.git --path ui-design/skills/visual-hierarchy--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Owl-Listener/designer-skills --skill visual-hierarchy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/designer-skills visual-hierarchy --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/ui-design/skills/visual-hierarchy .gemini/skills/visual-hierarchy && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "visual-hierarchy" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/ui-design/skills/visual-hierarchy into .gemini/skills/visual-hierarchy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "visual-hierarchy", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Owl-Listener/designer-skills visual-hierarchyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Owl-Listener/designer-skills --skill visual-hierarchy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/ui-design/skills/visual-hierarchy .github/skills/visual-hierarchy && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "visual-hierarchy" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/ui-design/skills/visual-hierarchy into .github/skills/visual-hierarchy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "visual-hierarchy", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/designer-skills --skill visual-hierarchy -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Owl-Listener/designer-skills visual-hierarchy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/ui-design/skills/visual-hierarchy .opencode/skills/visual-hierarchy && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "visual-hierarchy" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/ui-design/skills/visual-hierarchy into .opencode/skills/visual-hierarchy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "visual-hierarchy", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
visual-hierarchy- GitHub stars
- 2.9k
- Used in
- 1 other repo
- Token cost
- ~466 tokens
- SKILL.md length
- 223 words
- Files
- 1
- Skills in repo
- 107
- Repo updated
- First seen
- Licence
- MIT
At a glance
Establish hierarchy through size, weight, colour, spacing, and position so the eye lands in the intended order.
- Works in 4 steps: Primary: Page title, primary CTA — seen… → Secondary: Section headings, key content… → Tertiary: Supporting text, metadata —… → …
- Composing new work
- SKILL.md covers What You Do, Hierarchy Tools, Hierarchy Levels and Common Patterns, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Visual Hierarchy is an agent skill from Owl-Listener/designer-skills. Establish hierarchy through size, weight, colour, spacing, and position so the eye lands in the intended order. Use when composing new work. For judging an existing screen, use critique-visual-hierarchy (visual-critique).
Its SKILL.md is about 470 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Frontend & Design, covering Design review and critique. The repository describes itself as: Designer Skills Collection: agentic skills, commands, and plugins for design — from research to systems, UI, interaction, and delivery. The licence is MIT.
When your agent uses it
- Composing new work
- Tasks that involve Design review and critique
Example prompts
- “/visual-hierarchy”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Primary: Page title, primary CTA — seen first
- Secondary: Section headings, key content — scanned next
- Tertiary: Supporting text, metadata — read on demand
- Quaternary: Fine print, timestamps — available but not prominent
What it can do on your machine
Read from SKILL.md and the folder at commit 9a6930c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Visual Hierarchy loads about 466 tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 223 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Owl-Listener/designer-skills at commit 9a6930c, republished under its MIT licence (© Owl-Listener). 223 words, ~466 tokens.
Download SKILL.mdSave it as
.claude/skills/visual-hierarchy/SKILL.md (or your agent's skills folder).- name
- visual-hierarchy
- description
- Establish hierarchy through size, weight, colour, spacing, and position so the eye lands in the intended order. Use when composing new work. For judging an existing screen, use `critique-visual-hierarchy` (visual-critique).
Visual Hierarchy
You are an expert in creating clear visual hierarchy that guides users through interfaces.
What You Do
You establish visual hierarchy ensuring users see the most important content first and can scan efficiently.
Hierarchy Tools
Size
Larger elements draw attention first. Use size differences of at least 1.5x for clear distinction.
Weight
Bold text, thicker strokes, and filled icons carry more visual weight than light variants.
Color and Contrast
High contrast attracts attention. Use color strategically for CTAs, status, and emphasis.
Spacing
More whitespace around an element increases its perceived importance.
Position
Top-left (in LTR layouts) gets seen first. Above the fold matters. F-pattern and Z-pattern scanning.
Density
Isolated elements stand out. Grouped elements are scanned as a unit.
Hierarchy Levels
- Primary: Page title, primary CTA — seen first
- Secondary: Section headings, key content — scanned next
- Tertiary: Supporting text, metadata — read on demand
- Quaternary: Fine print, timestamps — available but not prominent
Common Patterns
- Hero sections: large type + image + single CTA
- Card layouts: image > title > description > action
- Forms: label > input > helper text > error
- Navigation: current state > available > disabled
Best Practices
- Squint test: blur your eyes — hierarchy should still be clear
- One primary action per view
- Don't compete for attention — choose what matters most
- Use hierarchy to tell a story through the page
- Test with real users doing real tasks
© Owl-Listener, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in ui-design/skills/visual-hierarchy of Owl-Listener/designer-skills.
Open the folder on GitHubat commit 9a6930c
Used in 1 other repository
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in Owl-Listener/designer-skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Visual Hierarchy next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Visual Hierarchy this skillOwl-Listener/designer-skills | 2.9k | 1 repos | ~466 | Automated safety check: Pass | MIT | |
| Design AuditAThevon/genjutsu | 431 | 1 repos | ~1.6k | Automated safety check: Pass | Custom licence | |
| Qovery UIQovery/console | 227 | — | ~2k | Automated safety check: Pass | GPL-3.0 | |
| Dsh CI Test ReliabilityZhou-Yujing114514/deepseek-harness-linux | 119 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Design ReviewOwl-Listener/designpowers | 251 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Om UX Review PRgo-musicfox/go-musicfox | 2.6k | 1 repos | ~1.4k | Automated safety check: Notes | GPL-3.0 |
Similar skills
Qovery UI
Qovery/console
Design review and implementation guidance for the Qovery Console.
Dsh CI Test Reliability
Zhou-Yujing114514/deepseek-harness-linux
Design, review, and diagnose DeepSeek Harness tests and fixtures that can fail nondeterministically under CI concurrency, shared host resources, clocks, process-global state, subprocesses, network…
Design Review
Owl-Listener/designpowers
A skill your agent uses when the user wants to evaluate something that ALREADY EXISTS rather than build something new — "review this", "audit this screen", "what's wrong with this page", "is this…
Om UX Review PR
go-musicfox/go-musicfox
Evidence-first design review of a PR's UI. An agent skill from go-musicfox/go-musicfox.
Design Review
jezweb/claude-skills
Review a web app or page for visual design quality — layout, typography, spacing, colour, hierarchy, consistency, interaction patterns, and responsive behaviour.
More from Owl-Listener/designer-skills
All 107 skills in this repoA B Test Design
Owl-Listener/designer-skills
Design an A/B experiment — hypothesis, variants, primary metric, and sample size.
Accessibility Test Plan
Owl-Listener/designer-skills
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol.
Aesthetic Usability
Owl-Listener/designer-skills
Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction.
Affinity Diagram
Owl-Listener/designer-skills
Cluster many qualitative data points into themes and insight statements.
Animation Principles
Owl-Listener/designer-skills
Apply animation principles — easing, staging, follow-through — to one specific UI motion.
Business Design
Owl-Listener/designer-skills
Read financials, map competitive landscapes, and argue design decisions in the language of value.
Related
Categories
Questions about Visual Hierarchy
What does Visual Hierarchy do?
Establish hierarchy through size, weight, colour, spacing, and position so the eye lands in the intended order. Visual Hierarchy is an agent skill from Owl-Listener/designer-skills. Establish hierarchy through size, weight, colour, spacing, and position so the eye lands in the intended order.
When should I use Visual Hierarchy?
Visual Hierarchy fits situations like: composing new work; tasks that involve Design review and critique.
How do I install Visual Hierarchy in Claude Code?
Run `npx skills add Owl-Listener/designer-skills --skill visual-hierarchy -a claude-code`. Or copy the skill folder (ui-design/skills/visual-hierarchy in Owl-Listener/designer-skills) into .claude/skills/visual-hierarchy in your project. Claude Code loads it when a task matches its description.
How do I install Visual Hierarchy in Codex?
Run `npx skills add Owl-Listener/designer-skills --skill visual-hierarchy -a codex`. Or copy the skill folder (ui-design/skills/visual-hierarchy in Owl-Listener/designer-skills) into .agents/skills/visual-hierarchy in your project. Codex loads it when a task matches its description.
Can I use Visual Hierarchy in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Owl-Listener/designer-skills --skill visual-hierarchy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/visual-hierarchy, .gemini/skills/visual-hierarchy, .github/skills/visual-hierarchy and .opencode/skills/visual-hierarchy in your project.
What does Visual Hierarchy need to run?
SKILL.md names no scripts, command-line tools or credentials: Visual Hierarchy is instructions for the agent only.
Does Visual Hierarchy access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Visual Hierarchy safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Visual Hierarchy use?
Visual Hierarchy is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Visual Hierarchy use?
About 466 tokens (SKILL.md is roughly 1.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Visual Hierarchy?
Skills that share tags, products or a category with Visual Hierarchy: Design Audit (AThevon/genjutsu, 431 stars), Qovery UI (Qovery/console, 227 stars), Dsh CI Test Reliability (Zhou-Yujing114514/deepseek-harness-linux, 119 stars) and Design Review (Owl-Listener/designpowers, 251 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Visual Hierarchy?
Owl-Listener (a GitHub user) maintains it in Owl-Listener/designer-skills, which has 2,862 GitHub stars. The repository holds 107 skills in this directory. The repository was last updated on September 5, 2026.
Source: Owl-Listener/designer-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.