Product Design Workflow Bundle
XiaomiMiMo/MiMo-Code
Entry point to a bundle of product design workflows covering context, research, audits, ideation, URL or image to code, design QA and sharing a prototype.
Facilitate a structured team critique — framing, feedback rules, and actionable outcomes.
Install Design Critique
$ npx skills add Owl-Listener/designer-skills --skill design-critique -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/designer-skills design-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/Owl-Listener/designer-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/design-ops/skills/design-critique .claude/skills/design-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 "design-critique" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-ops/skills/design-critique into .claude/skills/design-critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-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/Owl-Listener/designer-skills/tree/main/design-ops/skills/design-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 Owl-Listener/designer-skills --skill design-critique -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/designer-skills design-critique --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/design-ops/skills/design-critique .agents/skills/design-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 "design-critique" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-ops/skills/design-critique into .agents/skills/design-critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-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 Owl-Listener/designer-skills --skill design-critique -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/designer-skills design-critique --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/design-ops/skills/design-critique .cursor/skills/design-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 "design-critique" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-ops/skills/design-critique into .cursor/skills/design-critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-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/Owl-Listener/designer-skills.git --path design-ops/skills/design-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 Owl-Listener/designer-skills --skill design-critique -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/designer-skills design-critique --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/design-ops/skills/design-critique .gemini/skills/design-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 "design-critique" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-ops/skills/design-critique into .gemini/skills/design-critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-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 Owl-Listener/designer-skills design-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 Owl-Listener/designer-skills --skill design-critique -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/design-ops/skills/design-critique .github/skills/design-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 "design-critique" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-ops/skills/design-critique into .github/skills/design-critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-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 Owl-Listener/designer-skills --skill design-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 Owl-Listener/designer-skills design-critique --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/design-ops/skills/design-critique .opencode/skills/design-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 "design-critique" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-ops/skills/design-critique into .opencode/skills/design-critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-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
design-critique- GitHub stars
- 2.9k
- Used in
- 1 other repo
- Token cost
- ~513 tokens
- SKILL.md length
- 235 words
- Files
- 1
- Skills in repo
- 107
- Repo updated
- First seen
- Licence
- MIT
At a glance
Facilitate a structured team critique — framing, feedback rules, and actionable outcomes.
- Works in 5 steps: Present (5 min) — Designer walks through… → Clarify (5 min) — Questions to… → Feedback rounds — Structured by category… → …
- Running a session with people in the room
- SKILL.md covers What You Do, Critique Framework, Critique Types and Common Pitfalls, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Design Critique is an agent skill from Owl-Listener/designer-skills. Facilitate a structured team critique — framing, feedback rules, and actionable outcomes. Use when running a session with people in the room. For a solo expert review, use heuristic-evaluation (prototyping-testing).
Its SKILL.md is about 510 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 Media & Creative, covering Design review and critique, UX design and Prototyping. 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
- Running a session with people in the room
- Tasks that involve Design review and critique
- Tasks that involve UX design
Example prompts
- “/design-critique”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Present (5 min) — Designer walks through the work and goals
- Clarify (5 min) — Questions to understand, not judge
- Feedback rounds — Structured by category or priority
- Discuss — Open conversation on key tensions
- Capture — Document decisions and action items
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
Design Critique loads about 513 tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 235 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). 235 words, ~513 tokens.
Download SKILL.mdSave it as
.claude/skills/design-critique/SKILL.md (or your agent's skills folder).- name
- design-critique
- description
- Facilitate a structured team critique — framing, feedback rules, and actionable outcomes. Use when running a session with people in the room. For a solo expert review, use `heuristic-evaluation` (prototyping-testing).
Design Critique
You are an expert in facilitating productive design critiques that improve work and grow teams.
What You Do
You structure and facilitate design critiques that produce clear, actionable feedback.
Critique Framework
Before the Critique
- Designer shares context: goals, constraints, target audience, stage of work
- Define what feedback is needed (layout? flow? copy? everything?)
- Set the rules: constructive, specific, actionable
During the Critique
- Present (5 min) — Designer walks through the work and goals
- Clarify (5 min) — Questions to understand, not judge
- Feedback rounds — Structured by category or priority
- Discuss — Open conversation on key tensions
- Capture — Document decisions and action items
Feedback Format
- 'I notice...' (observation, not judgment)
- 'I wonder...' (question or exploration)
- 'What if...' (suggestion or alternative)
- 'I think... because...' (opinion with rationale)
After the Critique
- Designer summarizes takeaways
- Action items with owners and deadlines
- Follow-up review if needed
Critique Types
- Desk crit: Informal, 1-on-1, quick feedback
- Team crit: Scheduled, structured, full team
- Cross-team crit: Fresh eyes from outside the project
- Stakeholder review: Decision-focused, approval-oriented
Common Pitfalls
- Designing by committee (too many opinions, no direction)
- Focusing on personal preference instead of user needs
- Critiquing too early (exploring) or too late (polishing)
- No clear next steps
Best Practices
- Separate exploration critiques from refinement critiques
- Critique the work, not the person
- Always tie feedback to goals and user needs
- Rotate the facilitator role
- Make critique a regular ritual, not an event
© 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 design-ops/skills/design-critique 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
Design 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 |
|---|---|---|---|---|---|---|
| Design Critique this skillOwl-Listener/designer-skills | 2.9k | 1 repos | ~513 | Automated safety check: Pass | MIT | |
| Product Design Workflow BundleXiaomiMiMo/MiMo-Code | 14k | — | ~721 | Automated safety check: Pass | MIT | |
| Steve Jobs Design Reviewwondelai/skills | 2.4k | — | ~4.5k | Automated safety check: Pass | MIT | |
| Product Designeraakashg/pm-claude-skills | 112 | — | ~2.4k | 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 |
Similar skills
Steve Jobs Design Review
wondelai/skills
Review designs, products, and features with Steve Jobs' standards: ruthless simplicity, focus, and end-to-end excellence.
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.
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.
I Critique
boussadjra/vuestrata
Evaluate design effectiveness from a UX perspective. An agent skill from boussadjra/vuestrata.
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 Design Critique
What does Design Critique do?
Facilitate a structured team critique — framing, feedback rules, and actionable outcomes. Design Critique is an agent skill from Owl-Listener/designer-skills. Facilitate a structured team critique — framing, feedback rules, and actionable outcomes.
When should I use Design Critique?
Design Critique fits situations like: running a session with people in the room; tasks that involve Design review and critique; tasks that involve UX design.
How do I install Design Critique in Claude Code?
Run `npx skills add Owl-Listener/designer-skills --skill design-critique -a claude-code`. Or copy the skill folder (design-ops/skills/design-critique in Owl-Listener/designer-skills) into .claude/skills/design-critique in your project. Claude Code loads it when a task matches its description.
How do I install Design Critique in Codex?
Run `npx skills add Owl-Listener/designer-skills --skill design-critique -a codex`. Or copy the skill folder (design-ops/skills/design-critique in Owl-Listener/designer-skills) into .agents/skills/design-critique in your project. Codex loads it when a task matches its description.
Can I use Design 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 Owl-Listener/designer-skills --skill design-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/design-critique, .gemini/skills/design-critique, .github/skills/design-critique and .opencode/skills/design-critique in your project.
What does Design Critique need to run?
SKILL.md names no scripts, command-line tools or credentials: Design Critique is instructions for the agent only.
Does Design 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 Design 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 Design Critique use?
Design 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 Design Critique use?
About 513 tokens (SKILL.md is roughly 2.1k 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 Design Critique?
Skills that share tags, products or a category with Design Critique: Product Design Workflow Bundle (XiaomiMiMo/MiMo-Code, 14k stars), Steve Jobs Design Review (wondelai/skills, 2.4k stars), Product Designer (aakashg/pm-claude-skills, 112 stars) and Om UX Review PR (go-musicfox/go-musicfox, 2.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Design Critique?
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.