UI Styling
Ohh-889/skyroc
Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs.
Critique a rendered screen's hierarchy — entry point, eye flow, weight distribution, and emphasis.
Install Critique Visual Hierarchy
$ npx skills add Owl-Listener/designer-skills --skill critique-visual-hierarchy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/designer-skills critique-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/visual-critique/skills/critique-visual-hierarchy .claude/skills/critique-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 "critique-visual-hierarchy" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/visual-critique/skills/critique-visual-hierarchy into .claude/skills/critique-visual-hierarchy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "critique-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/visual-critique/skills/critique-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 critique-visual-hierarchy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/designer-skills critique-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/visual-critique/skills/critique-visual-hierarchy .agents/skills/critique-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 "critique-visual-hierarchy" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/visual-critique/skills/critique-visual-hierarchy into .agents/skills/critique-visual-hierarchy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "critique-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 critique-visual-hierarchy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/designer-skills critique-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/visual-critique/skills/critique-visual-hierarchy .cursor/skills/critique-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 "critique-visual-hierarchy" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/visual-critique/skills/critique-visual-hierarchy into .cursor/skills/critique-visual-hierarchy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "critique-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 visual-critique/skills/critique-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 critique-visual-hierarchy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/designer-skills critique-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/visual-critique/skills/critique-visual-hierarchy .gemini/skills/critique-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 "critique-visual-hierarchy" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/visual-critique/skills/critique-visual-hierarchy into .gemini/skills/critique-visual-hierarchy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "critique-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 critique-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 critique-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/visual-critique/skills/critique-visual-hierarchy .github/skills/critique-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 "critique-visual-hierarchy" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/visual-critique/skills/critique-visual-hierarchy into .github/skills/critique-visual-hierarchy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "critique-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 critique-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 critique-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/visual-critique/skills/critique-visual-hierarchy .opencode/skills/critique-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 "critique-visual-hierarchy" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/visual-critique/skills/critique-visual-hierarchy into .opencode/skills/critique-visual-hierarchy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "critique-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
critique-visual-hierarchy- GitHub stars
- 2.9k
- Used in
- 1 other repo
- Token cost
- ~608 tokens
- SKILL.md length
- 310 words
- Files
- 1
- Skills in repo
- 107
- Repo updated
- First seen
- Licence
- MIT
At a glance
Critique a rendered screen's hierarchy — entry point, eye flow, weight distribution, and emphasis.
- Works in 3 steps: Observation — what you see (neutral,… → Problem — what is broken and why it… → Fix — a specific, actionable change
- Attention lands in the wrong place
- SKILL.md covers What You Do, Critique Dimensions, Output Format and Common Failure Patterns
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Critique Visual Hierarchy is an agent skill from Owl-Listener/designer-skills. 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).
Its SKILL.md is about 610 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 UI design. 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
- Attention lands in the wrong place
- Tasks that involve UI design
Example prompts
- “/critique-visual-hierarchy”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Observation — what you see (neutral, factual)
- Problem — what is broken and why it matters
- Fix — a specific, actionable change
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
Critique Visual Hierarchy loads about 608 tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 310 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). 310 words, ~608 tokens.
Download SKILL.mdSave it as
.claude/skills/critique-visual-hierarchy/SKILL.md (or your agent's skills folder).- 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).
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:
- Observation — what you see (neutral, factual)
- Problem — what is broken and why it matters
- 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
© 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 visual-critique/skills/critique-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
Critique 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 |
|---|---|---|---|---|---|---|
| Critique Visual Hierarchy this skillOwl-Listener/designer-skills | 2.9k | 1 repos | ~608 | Automated safety check: Pass | MIT | |
| UI StylingOhh-889/skyroc | 795 | 13 repos | ~2.5k | Automated safety check: Pass | MIT | |
| LobeHub Interactive Prototypelobehub/lobehub | 83k | — | ~1.6k | Automated safety check: Pass | Custom licence | |
| Make Interfaces Feel Bettersamuelclay/NewsBlur | 7.6k | 10 repos | ~1.5k | Automated safety check: Pass | MIT | |
| UI UX Pro MaxZxBing0066/pixel-converter | 181 | 13 repos | ~2.6k | Automated safety check: Notes | BSD-2-Clause | |
| Design Dnazanwei/design-dna | 1.9k | 1 repos | ~2.1k | Automated safety check: Pass | MIT |
Similar skills
LobeHub Interactive Prototype
lobehub/lobehub
Builds single-file interactive HTML prototypes rendered with the real LobeHub UI components and written as production-style React, so they can later be split into files.
Make Interfaces Feel Better
samuelclay/NewsBlur
Design engineering principles for making interfaces feel polished.
UI UX Pro Max
ZxBing0066/pixel-converter
UI/UX design intelligence with searchable database. An agent skill from ZxBing0066/pixel-converter.
Design Dna
zanwei/design-dna
Extract, define, and apply design DNA across three dimensions: design system (tokens), design style (qualitative feel), and visual effects (Canvas, WebGL, 3D, particles, shaders, scroll effects…
Figma Design to Code
warpdotdev/warp
Turns a Figma frame or component into production code that matches the design, using the Figma MCP server and the project's own design system.
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 Critique Visual Hierarchy
What does Critique Visual Hierarchy do?
Critique a rendered screen's hierarchy — entry point, eye flow, weight distribution, and emphasis. Critique Visual Hierarchy is an agent skill from Owl-Listener/designer-skills. Critique a rendered screen's hierarchy — entry point, eye flow, weight distribution, and emphasis.
When should I use Critique Visual Hierarchy?
Critique Visual Hierarchy fits situations like: attention lands in the wrong place; tasks that involve UI design.
How do I install Critique Visual Hierarchy in Claude Code?
Run `npx skills add Owl-Listener/designer-skills --skill critique-visual-hierarchy -a claude-code`. Or copy the skill folder (visual-critique/skills/critique-visual-hierarchy in Owl-Listener/designer-skills) into .claude/skills/critique-visual-hierarchy in your project. Claude Code loads it when a task matches its description.
How do I install Critique Visual Hierarchy in Codex?
Run `npx skills add Owl-Listener/designer-skills --skill critique-visual-hierarchy -a codex`. Or copy the skill folder (visual-critique/skills/critique-visual-hierarchy in Owl-Listener/designer-skills) into .agents/skills/critique-visual-hierarchy in your project. Codex loads it when a task matches its description.
Can I use Critique 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 critique-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/critique-visual-hierarchy, .gemini/skills/critique-visual-hierarchy, .github/skills/critique-visual-hierarchy and .opencode/skills/critique-visual-hierarchy in your project.
What does Critique Visual Hierarchy need to run?
SKILL.md names no scripts, command-line tools or credentials: Critique Visual Hierarchy is instructions for the agent only.
Does Critique 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 Critique 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 Critique Visual Hierarchy use?
Critique 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 Critique Visual Hierarchy use?
About 608 tokens (SKILL.md is roughly 2.4k 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 Critique Visual Hierarchy?
Skills that share tags, products or a category with Critique Visual Hierarchy: UI Styling (Ohh-889/skyroc, 795 stars), LobeHub Interactive Prototype (lobehub/lobehub, 83k stars), Make Interfaces Feel Better (samuelclay/NewsBlur, 7.6k stars) and UI UX Pro Max (ZxBing0066/pixel-converter, 181 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Critique Visual Hierarchy?
Owl-Listener (a GitHub user) maintains it in Owl-Listener/designer-skills, which has 2,871 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.