Design Audit
AThevon/genjutsu
Design audit checklist - motion gaps, accessibility, color consistency, responsive, performance.
A skill your agent uses when reviewing design work against a plan, design principles, or quality standards — provides structured critique covering design intent, accessibility, consistency, and user…
Install Designpowers Critique
$ npx skills add Owl-Listener/designpowers --skill designpowers-critique -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/designpowers designpowers-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/designpowers.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/designpowers-critique .claude/skills/designpowers-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 "designpowers-critique" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/designpowers-critique into .claude/skills/designpowers-critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "designpowers-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/designpowers/tree/main/skills/designpowers-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/designpowers --skill designpowers-critique -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/designpowers designpowers-critique --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designpowers.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/designpowers-critique .agents/skills/designpowers-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 "designpowers-critique" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/designpowers-critique into .agents/skills/designpowers-critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "designpowers-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/designpowers --skill designpowers-critique -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/designpowers designpowers-critique --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designpowers.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/designpowers-critique .cursor/skills/designpowers-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 "designpowers-critique" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/designpowers-critique into .cursor/skills/designpowers-critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "designpowers-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/designpowers.git --path skills/designpowers-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/designpowers --skill designpowers-critique -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/designpowers designpowers-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/designpowers.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/designpowers-critique .gemini/skills/designpowers-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 "designpowers-critique" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/designpowers-critique into .gemini/skills/designpowers-critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "designpowers-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/designpowers designpowers-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/designpowers --skill designpowers-critique -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Owl-Listener/designpowers.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/designpowers-critique .github/skills/designpowers-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 "designpowers-critique" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/designpowers-critique into .github/skills/designpowers-critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "designpowers-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/designpowers --skill designpowers-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/designpowers designpowers-critique --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designpowers.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/designpowers-critique .opencode/skills/designpowers-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 "designpowers-critique" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/designpowers-critique into .opencode/skills/designpowers-critique/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "designpowers-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
designpowers-critique- GitHub stars
- 251
- Token cost
- ~1.6k tokens
- SKILL.md length
- 705 words
- Files
- 1
- Skills in repo
- 33
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when reviewing design work against a plan, design principles, or quality standards — provides structured critique covering design intent, accessibility, consistency, and user…
- Works in 8 steps: Gather Review Inputs → Evaluate Against Intent → Craft and Taste Evaluation → …
- Reviewing design work against a plan
- SKILL.md covers When to Use, Process and Integration
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Designpowers Critique is an agent skill from Owl-Listener/designpowers. Use when reviewing design work against a plan, design principles, or quality standards — provides structured critique covering design intent, accessibility, consistency, and user impact. This is the Designpowers critique skill — use this instead of the Superpowers design-critique when working within a Designpowers workflow
Its SKILL.md is about 1.6k 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 Accessibility. The repository describes itself as: An agent design team you control: 10 agents that run an inclusive design process while you direct. The licence is MIT.
When your agent uses it
- Reviewing design work against a plan
- Design principles
- Quality standards — provides structured critique covering design intent
Example prompts
- “/designpowers-critique”
Workflow steps
8 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 cb00757. 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 (its code samples are markdown).
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
Designpowers Critique loads about 1.6k tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 705 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/designpowers at commit cb00757, republished under its MIT licence (© Owl-Listener). 705 words, ~1,599 tokens.
Download SKILL.mdSave it as
.claude/skills/designpowers-critique/SKILL.md (or your agent's skills folder).- name
- designpowers-critique
- description
- Use when reviewing design work against a plan, design principles, or quality standards — provides structured critique covering design intent, accessibility, consistency, and user impact. This is the Designpowers critique skill — use this instead of the Superpowers design-critique when working within a Designpowers workflow
Design Critique
Critique is a structured evaluation of whether the design achieves what it set out to do, for the people it set out to serve — and whether it does so with the craft quality the project demands. This skill ensures review is rigorous, specific, and constructive. When a taste profile exists, critique includes aesthetic evaluation against that profile — not arbitrary personal preference, but the specific emotional target, craft standards, and quality bar the team agreed on.
When to Use
- After completing a design task or set of tasks
- Before handoff to engineering
- When a design decision feels uncertain
- At scheduled review points in a design plan
Process
Step 1: Gather Review Inputs
Before critiquing, assemble:
- The design brief (from design-discovery)
- The design plan (from writing-design-plans)
- The design principles (from design-strategy)
- The personas (from inclusive-personas)
- The current design artefacts (mockups, code, prototypes)
Step 2: Evaluate Against Intent
For each design decision, ask:
- Does it solve the stated problem? Refer to the design brief
- Does it serve the identified personas? All of them, not just the primary user
- Does it follow the design principles? Specifically which principles it upholds or violates
- Does it align with the design system? If applicable
Step 3: Craft and Taste Evaluation
If a taste profile exists (from design-taste), evaluate the design against it:
Emotional target:
- Does the design evoke the intended feeling? (Reference the taste profile's emotional target)
- Would the user describe this experience with the words in the emotional target?
Craft standards:
- Spacing has intentional rhythm — not just "correct," but considered
- Colour usage follows the restraint/vibrancy rules in the taste profile
- Shadows, borders, and radii use a consistent vocabulary
- Typography choices serve both readability and personality
- The overall composition feels cohesive — like one designer, not a committee
Reference benchmark:
- This design would sit comfortably next to the taste references
- The quality level matches what was agreed (prototype/production/flagship)
Craft findings format:
| Element | Taste expectation | Current state | Gap |
|---|---|---|---|
| [Element] | [What the taste profile calls for] | [What exists] | [Specific difference] |
If no taste profile exists, note this as an observation: "No taste profile was created for this project. Craft evaluation is based on general quality standards only."
Show full SKILL.md (342 more words)Show less
Step 4: Accessibility Review
Every critique includes an accessibility evaluation:
Perceivable:
- All content is available to screen readers
- Colour is not the sole indicator of meaning
- Contrast ratios meet WCAG AA minimum
- Text is resizable to 200% without loss of function
- Alt text is present and appropriate
Operable:
- All interactions are keyboard accessible
- Focus order is logical
- Focus indicators are visible
- Touch targets meet 44x44px minimum
- Motion respects prefers-reduced-motion
- No keyboard traps
Understandable:
- Language is plain and clear
- Navigation is consistent
- Error messages explain the problem and the solution
- Form labels are visible and associated
- Behaviour is predictable
Robust:
- Semantic HTML is used correctly
- ARIA is used only when necessary and correctly
- The design works across supported browsers and assistive technology
Step 5: Classify Issues
Rate each finding:
| Severity | Definition | Action |
|---|---|---|
| Critical | Blocks access for some users or violates the design intent | Must fix before proceeding |
| Major | Degrades experience significantly but does not block access | Should fix before handoff |
| Minor | Improvement opportunity, does not block or significantly degrade | Fix if time allows |
| Note | Observation or suggestion for future iteration | Document for next cycle |
Step 6: Write the Critique
# Design Critique: [Feature/Task Name]
**Reviewed against:** [Design brief, plan, principles — with references]
**Date:** [YYYY-MM-DD]
## Summary
[2-3 sentences: overall assessment]
## Craft Assessment
[Does the design meet the taste profile's quality bar? Emotional target alignment? Reference benchmark?]
## Findings
### Critical
- [Finding]: [Explanation] → [Recommended action]
### Major
- [Finding]: [Explanation] → [Recommended action]
### Minor
- [Finding]: [Explanation] → [Recommended action]
### Notes
- [Observation]
## Accessibility Status
[Pass/Fail against WCAG AA with specific gaps]
## Recommendation
[Proceed / Revise and re-review / Rethink approach]Step 7: Present and Discuss
Present findings to the user. For each critical or major issue, explain:
- What the issue is
- Who it affects (reference specific personas)
- What the recommended fix is
- Why it matters
Critical issues block progress. They must be resolved before moving to handoff.
Step 8: Record Design Debt
After the critique is complete and the fix round is determined:
- Identify all Minor and Note severity findings that will NOT be fixed in this round
- Invoke
design-debt-trackerto capture these as debt items in the Design Debt Register - Each deferred item must include: who is affected, suggested fix, and why it was deferred
Do not silently drop Minor findings. They either get fixed or they get tracked.
Integration
- Called by:
writing-design-plans(at review checkpoints) - Reviews output from:
ui-composition,interaction-design,accessible-content,cognitive-accessibility,adaptive-interfaces,design-system-alignment - Calls: Relevant design skills for fixes,
design-debt-trackerfor deferred findings, thendesign-handoffwhen critique passes
© 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 skills/designpowers-critique of Owl-Listener/designpowers.
Open the folder on GitHubat commit cb00757
Compare with similar skills
Designpowers 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 |
|---|---|---|---|---|---|---|
| Designpowers Critique this skillOwl-Listener/designpowers | 251 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Design AuditAThevon/genjutsu | 440 | — | ~1.6k | Automated safety check: Pass | Custom licence | |
| Critique Theaternexu-io/open-design | 100k | — | ~640 | Automated safety check: Pass | Apache-2.0 | |
| Design FlowOwl-Listener/inclusive-design-skills | 105 | — | ~528 | Automated safety check: Pass | MIT | |
| Web Interface Guidelines Reviewervercel-labs/openreview | 1.7k | 97 repos | ~308 | Automated safety check: Pass | None | |
| Frontend Designjwynia/agent-skills | 170 | — | ~3.2k | Automated safety check: Pass | MIT |
Similar skills
Critique Theater
nexu-io/open-design
Five-dimension design quality review — score the artifact against craft, brand, accessibility, and copy, then fix what falls short before handing it over.
Design Flow
Owl-Listener/inclusive-design-skills
Design an interaction flow with inclusive input and output options from the start.
- Official
Web Interface Guidelines Reviewer
vercel-labs/openreview
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…
Frontend Design
jwynia/agent-skills
Create distinctive, production-grade frontend interfaces with high design quality.
Frontend Design
spinspire/pocketbase-sveltekit-starter
Create distinctive, production-grade frontend interfaces with high design quality and accessible markup.
More from Owl-Listener/designpowers
All 33 skills in this repoAdaptive Interfaces
Owl-Listener/designpowers
A skill your agent uses when designing for user preferences — motion sensitivity, contrast needs, colour schemes, text sizing, information density, or any interface behaviour that should adapt to…
Design Debate
Owl-Listener/designpowers
A skill your agent uses when a design direction is uncertain, when the team could go multiple ways, or when the user wants to see competing approaches argued before committing — orchestrates…
Design Debt Tracker
Owl-Listener/designpowers
A skill your agent uses when critique or review produces deferred findings, when checking accumulated design compromises, or when deciding what to address in the next iteration.
Design Discovery
Owl-Listener/designpowers
You MUST use this before any creative or design work — building features, creating components, designing interfaces, modifying user-facing behaviour.
Design Handoff
Owl-Listener/designpowers
A skill your agent uses when design work is complete and needs to be communicated to engineering — creates specifications, documents rationale, accessibility requirements, and interaction details in…
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…
Related
Categories
Questions about Designpowers Critique
What does Designpowers Critique do?
A skill your agent uses when reviewing design work against a plan, design principles, or quality standards — provides structured critique covering design intent, accessibility, consistency, and user…. Designpowers Critique is an agent skill from Owl-Listener/designpowers. Use when reviewing design work against a plan, design principles, or quality standards — provides structured critique covering design intent, accessibility, consistency, and user impact.
When should I use Designpowers Critique?
Designpowers Critique fits situations like: reviewing design work against a plan; design principles; quality standards — provides structured critique covering design intent.
How do I install Designpowers Critique in Claude Code?
Run `npx skills add Owl-Listener/designpowers --skill designpowers-critique -a claude-code`. Or copy the skill folder (skills/designpowers-critique in Owl-Listener/designpowers) into .claude/skills/designpowers-critique in your project. Claude Code loads it when a task matches its description.
How do I install Designpowers Critique in Codex?
Run `npx skills add Owl-Listener/designpowers --skill designpowers-critique -a codex`. Or copy the skill folder (skills/designpowers-critique in Owl-Listener/designpowers) into .agents/skills/designpowers-critique in your project. Codex loads it when a task matches its description.
Can I use Designpowers 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/designpowers --skill designpowers-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/designpowers-critique, .gemini/skills/designpowers-critique, .github/skills/designpowers-critique and .opencode/skills/designpowers-critique in your project.
What does Designpowers Critique need to run?
SKILL.md names no scripts, command-line tools or credentials: Designpowers Critique is instructions for the agent only.
Does Designpowers 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 Designpowers 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 Designpowers Critique use?
Designpowers 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 Designpowers Critique use?
About 1.6k tokens (SKILL.md is roughly 6.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 Designpowers Critique?
Skills that share tags, products or a category with Designpowers Critique: Design Audit (AThevon/genjutsu, 440 stars), Critique Theater (nexu-io/open-design, 100k stars), Design Flow (Owl-Listener/inclusive-design-skills, 105 stars) and Web Interface Guidelines Reviewer (vercel-labs/openreview, 1.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Designpowers Critique?
Owl-Listener (a GitHub user) maintains it in Owl-Listener/designpowers, which has 251 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on June 23, 2026.
Source: Owl-Listener/designpowers on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.