Localized reading guide
design-critiquePurpose, usage and source
Get structured design feedback on usability, hierarchy, and consistency. Trigger with "review this design", "critique this mockup", "what do you think of this screen?", or when sharing a Figma link or screenshot for feedback at any stage from exploration to final polish.
Source retrieved:
- Source repository
- anthropics/knowledge-work-plugins
- SKILL.md
design/skills/design-critique/SKILL.md- Repository stars
- 34,049
- Repository updated
- 2026-10-30
- Categories
- Design
- Last collected
License: Apache-2.0
Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.
The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.
What this Skill does
Get structured design feedback on usability, hierarchy, and consistency. Trigger with "review this design", "critique this mockup", "what do you think of this screen?", or when sharing a Figma link or screenshot for feedback at any stage from exploration to final polish.
How the upstream workflow works
Usage
Review the design: @$1 If a Figma URL is provided, pull the design from Figma. If a file is referenced, read it. Otherwise, ask the user to describe or share their design.
Upstream passage · L13 ↗How to Give Feedback
Be specific: "The CTA competes with the navigation" not "the layout is confusing" Explain why: Connect feedback to design principles or user needs Suggest alternatives: Don't just identify problems, propose solutions Acknowledge what works: Good feedback includes positive observations
Upstream passage · L59 ↗/design-critique
> If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md. Get structured design feedback across multiple dimensions.
Upstream passage · L7 ↗/design-critique $ARGUMENTSRequirements and setup
No short requirements passage was selected from this file. This does not mean the Skill has no dependencies. Check the repository setup instructions and referenced files.
Limits and quality checks
No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.
Start with a safe trial
- Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
- Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
- Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
- Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.
Read further in the source
Related Skills
Translation and scope
This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.
This introduction refers to the pinned version below; current repository activity and collection time are shown separately.
- Pinned source
- Read the original ↗
- Source retrieved
- Source commit
2574e29377c7173d0cecffef29a6ecbd7f8ccb5d- Source SHA-256
3a4f260eb9f60b431782bf6d90f22afb480c0c67860267a032df58a3e1bd19cd