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.
Evaluate design effectiveness from a UX perspective. An agent skill from boussadjra/vuestrata.
Install I Critique
$ npx skills add boussadjra/vuestrata --skill i-critique -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install boussadjra/vuestrata i-critique --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/boussadjra/vuestrata.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/i-critique .claude/skills/i-critique && 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 "i-critique" agent skill from https://github.com/boussadjra/vuestrata/tree/main/.github/skills/i-critique into .claude/skills/i-critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i-critique", 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/boussadjra/vuestrata/tree/main/.github/skills/i-critiqueType 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 boussadjra/vuestrata --skill i-critique -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install boussadjra/vuestrata i-critique --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boussadjra/vuestrata.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/i-critique .agents/skills/i-critique && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "i-critique" agent skill from https://github.com/boussadjra/vuestrata/tree/main/.github/skills/i-critique into .agents/skills/i-critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i-critique", 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 boussadjra/vuestrata --skill i-critique -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install boussadjra/vuestrata i-critique --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boussadjra/vuestrata.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/i-critique .cursor/skills/i-critique && 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 "i-critique" agent skill from https://github.com/boussadjra/vuestrata/tree/main/.github/skills/i-critique into .cursor/skills/i-critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i-critique", 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/boussadjra/vuestrata.git --path .github/skills/i-critique--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 boussadjra/vuestrata --skill i-critique -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install boussadjra/vuestrata i-critique --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boussadjra/vuestrata.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/i-critique .gemini/skills/i-critique && 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 "i-critique" agent skill from https://github.com/boussadjra/vuestrata/tree/main/.github/skills/i-critique into .gemini/skills/i-critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i-critique", 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 boussadjra/vuestrata i-critiqueInstalls 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 boussadjra/vuestrata --skill i-critique -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/boussadjra/vuestrata.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/i-critique .github/skills/i-critique && 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 "i-critique" agent skill from https://github.com/boussadjra/vuestrata/tree/main/.github/skills/i-critique into .github/skills/i-critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i-critique", 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 boussadjra/vuestrata --skill i-critique -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install boussadjra/vuestrata i-critique --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boussadjra/vuestrata.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/i-critique .opencode/skills/i-critique && 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 "i-critique" agent skill from https://github.com/boussadjra/vuestrata/tree/main/.github/skills/i-critique into .opencode/skills/i-critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "i-critique", 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
i-critique- GitHub stars
- 111
- Used in
- 4 other repos
- Token cost
- ~1.3k tokens
- SKILL.md length
- 678 words
- Files
- 1
- Skills in repo
- 21
- Repo updated
- First seen
- Licence
- MIT
At a glance
Evaluate design effectiveness from a UX perspective. An agent skill from boussadjra/vuestrata.
- Works in 10 steps: AI Slop Detection (CRITICAL) → Visual Hierarchy → Information Architecture → …
- Tasks that involve Design review and critique
- SKILL.md covers Design Critique and Generate Critique Report
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
I Critique is an agent skill from boussadjra/vuestrata. Evaluate design effectiveness from a UX perspective. Assesses visual hierarchy, information architecture, emotional resonance, and overall design quality with actionable feedback.
Its SKILL.md is about 1.3k 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 and UX design. The repository describes itself as: A modern, production-ready Vue 3 template with multi-theme support, Reka UI wrappers, and enterprise-grade tooling. The licence is MIT.
When your agent uses it
- Tasks that involve Design review and critique
- Tasks that involve UX design
Example prompts
- “/i-critique”
Workflow steps
10 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 73cbf9f. 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
I Critique loads about 1.3k tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 678 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 boussadjra/vuestrata at commit 73cbf9f, republished under its MIT licence (© boussadjra). 678 words, ~1,290 tokens.
Download SKILL.mdSave it as
.claude/skills/i-critique/SKILL.md (or your agent's skills folder).- name
- i-critique
- description
- Evaluate design effectiveness from a UX perspective. Assesses visual hierarchy, information architecture, emotional resonance, and overall design quality with actionable feedback.
- user-invokable
- true
- argument-hint
- AREA=<value>
Conduct a holistic design critique, evaluating whether the interface actually works—not just technically, but as a designed experience. Think like a design director giving feedback.
First: Use the i-frontend-design skill for design principles and anti-patterns.
Design Critique
Evaluate the interface across these dimensions:
1. AI Slop Detection (CRITICAL)
This is the most important check. Does this look like every other AI-generated interface from 2024-2025?
Review the design against ALL the DON'T guidelines in the i-frontend-design skill—they are the fingerprints of AI-generated work. Check for the AI color palette, gradient text, dark mode with glowing accents, glassmorphism, hero metric layouts, identical card grids, generic fonts, and all other tells.
The test: If you showed this to someone and said "AI made this," would they believe you immediately? If yes, that's the problem.
2. Visual Hierarchy
- Does the eye flow to the most important element first?
- Is there a clear primary action? Can you spot it in 2 seconds?
- Do size, color, and position communicate importance correctly?
- Is there visual competition between elements that should have different weights?
3. Information Architecture
- Is the structure intuitive? Would a new user understand the organization?
- Is related content grouped logically?
- Are there too many choices at once? (cognitive overload)
- Is the navigation clear and predictable?
4. Emotional Resonance
- What emotion does this interface evoke? Is that intentional?
- Does it match the brand personality?
- Does it feel trustworthy, approachable, premium, playful—whatever it should feel?
- Would the target user feel "this is for me"?
5. Discoverability & Affordance
- Are interactive elements obviously interactive?
- Would a user know what to do without instructions?
- Are hover/focus states providing useful feedback?
- Are there hidden features that should be more visible?
6. Composition & Balance
- Does the layout feel balanced or uncomfortably weighted?
- Is whitespace used intentionally or just leftover?
- Is there visual rhythm in spacing and repetition?
- Does asymmetry feel designed or accidental?
7. Typography as Communication
- Does the type hierarchy clearly signal what to read first, second, third?
- Is body text comfortable to read? (line length, spacing, size)
- Do font choices reinforce the brand/tone?
- Is there enough contrast between heading levels?
8. Color with Purpose
- Is color used to communicate, not just decorate?
- Does the palette feel cohesive?
- Are accent colors drawing attention to the right things?
- Does it work for colorblind users? (not just technically—does meaning still come through?)
Show full SKILL.md (289 more words)Show less
9. States & Edge Cases
- Empty states: Do they guide users toward action, or just say "nothing here"?
- Loading states: Do they reduce perceived wait time?
- Error states: Are they helpful and non-blaming?
- Success states: Do they confirm and guide next steps?
10. Microcopy & Voice
- Is the writing clear and concise?
- Does it sound like a human (the right human for this brand)?
- Are labels and buttons unambiguous?
- Does error copy help users fix the problem?
Generate Critique Report
Structure your feedback as a design director would:
Anti-Patterns Verdict
Start here. Pass/fail: Does this look AI-generated? List specific tells from the skill's Anti-Patterns section. Be brutally honest.
Overall Impression
A brief gut reaction—what works, what doesn't, and the single biggest opportunity.
What's Working
Highlight 2-3 things done well. Be specific about why they work.
Priority Issues
The 3-5 most impactful design problems, ordered by importance:
For each issue:
- What: Name the problem clearly
- Why it matters: How this hurts users or undermines goals
- Fix: What to do about it (be concrete)
- Command: Which command to use (prefer: /i-adapt, /i-animate, /i-audit, /i-bolder, /i-clarify, /i-colorize, /i-critique, /i-delight, /i-distill, /i-extract, /i-harden, /i-normalize, /i-onboard, /i-optimize, /i-polish, /i-quieter — or other installed skills you're sure exist)
Minor Observations
Quick notes on smaller issues worth addressing.
Questions to Consider
Provocative questions that might unlock better solutions:
- "What if the primary action were more prominent?"
- "Does this need to feel this complex?"
- "What would a confident version of this look like?"
Remember:
- Be direct—vague feedback wastes everyone's time
- Be specific—"the submit button" not "some elements"
- Say what's wrong AND why it matters to users
- Give concrete suggestions, not just "consider exploring..."
- Prioritize ruthlessly—if everything is important, nothing is
- Don't soften criticism—developers need honest feedback to ship great design
© boussadjra, 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 .github/skills/i-critique of boussadjra/vuestrata.
Open the folder on GitHubat commit 73cbf9f
Used in 4 other repositories
We found 4 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 4 other GitHub owners. This page covers the copy in boussadjra/vuestrata, which our catalogue first saw on October 7, 2026.
Compare with similar skills
I Critique 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 |
|---|---|---|---|---|---|---|
| I Critique this skillboussadjra/vuestrata | 111 | 4 repos | ~1.3k | 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 | |
| Design Reviewjezweb/claude-skills | 1.1k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Design Reviewplugin87/ux-ui-agent-skills | 1.6k | — | ~437 | Automated safety check: Pass | MIT | |
| Design Critiquemohitagw15856/pm-claude-skills | 1.4k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Interface Design for Dashboards and Appsholaboss-ai/holaOS | 11k | 3 repos | ~6k | Automated safety check: Pass | MIT |
Similar skills
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.
Design Review
plugin87/ux-ui-agent-skills
Review or audit a design/UI across 6 weighted dimensions with Nielsen's 10 heuristics and a prioritized findings table.
Design Critique
mohitagw15856/pm-claude-skills
Give structured, constructive feedback on any design using UX frameworks.
Interface Design for Dashboards and Apps
holaboss-ai/holaOS
Pushes an agent past generic defaults when designing dashboards, admin panels, SaaS apps and tools, with attention to structure, type, navigation and how data is shown.
Product Designer
aakashg/pm-claude-skills
A skill your agent uses when the user asks to review a design, critique a UI or mockup, give design feedback, or check a screen for usability and accessibility issues.
More from boussadjra/vuestrata
All 21 skills in this repoI Delight
boussadjra/vuestrata
Add moments of joy, personality, and unexpected touches that make interfaces memorable and enjoyable to use.
I Optimize
boussadjra/vuestrata
Improve interface performance across loading speed, rendering, animations, images, and bundle size.
I Frontend Design
boussadjra/vuestrata
Create distinctive, production-grade frontend interfaces with high design quality.
I Harden
boussadjra/vuestrata
Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management.
I Onboard
boussadjra/vuestrata
Design or improve onboarding flows, empty states, and first-time user experiences.
I Teach Impeccable
boussadjra/vuestrata
One-time setup that gathers design context for your project and saves it to your AI config file.
Related
Categories
Questions about I Critique
What does I Critique do?
Evaluate design effectiveness from a UX perspective. An agent skill from boussadjra/vuestrata. I Critique is an agent skill from boussadjra/vuestrata. Evaluate design effectiveness from a UX perspective.
When should I use I Critique?
I Critique fits situations like: tasks that involve Design review and critique; tasks that involve UX design.
How do I install I Critique in Claude Code?
Run `npx skills add boussadjra/vuestrata --skill i-critique -a claude-code`. Or copy the skill folder (.github/skills/i-critique in boussadjra/vuestrata) into .claude/skills/i-critique in your project. Claude Code loads it when a task matches its description.
How do I install I Critique in Codex?
Run `npx skills add boussadjra/vuestrata --skill i-critique -a codex`. Or copy the skill folder (.github/skills/i-critique in boussadjra/vuestrata) into .agents/skills/i-critique in your project. Codex loads it when a task matches its description.
Can I use I Critique 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 boussadjra/vuestrata --skill i-critique -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/i-critique, .gemini/skills/i-critique, .github/skills/i-critique and .opencode/skills/i-critique in your project.
What does I Critique need to run?
SKILL.md names no scripts, command-line tools or credentials: I Critique is instructions for the agent only.
Does I Critique 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 I Critique 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 I Critique use?
I Critique 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 I Critique use?
About 1.3k tokens (SKILL.md is roughly 5.2k 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 I Critique?
Skills that share tags, products or a category with I Critique: Om UX Review PR (go-musicfox/go-musicfox, 2.6k stars), Design Review (jezweb/claude-skills, 1.1k stars), Design Review (plugin87/ux-ui-agent-skills, 1.6k stars) and Design Critique (mohitagw15856/pm-claude-skills, 1.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains I Critique?
boussadjra (a GitHub user) maintains it in boussadjra/vuestrata, which has 111 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 5, 2026.
Source: boussadjra/vuestrata on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.