design-critique Skill
Give a structured product design critique — user job clarity, hierarchy, affordance, error states, accessibility, and consistency — focused on what to change, in what order, and why. Published by microsoft in amplifier-app-paperclip.
What is design-critique Skill?
Give a structured product design critique — user job clarity, hierarchy, affordance, error states, accessibility, and consistency — focused on what to change, in what order, and why. Published by microsoft in amplifier-app-paperclip. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Design and media
- Research
- Design and media use cases
- Research use cases
Technical details
- Install or run with Copy skill directory
When to use design-critique Skill
- Use it for design and media.
- Use it for research.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/amplifier-app-paperclip
- Skill file: packages/skills-catalog/catalog/optional/product/design-critique/SKILL.md
What it does
Give a structured product design critique — user job clarity, hierarchy, affordance, error states, accessibility, and consistency — focused on what to change, in what order, and why.
Skill instructions
Product Design Critique A structured critique pass for a screen, flow, or component. The output is a prioritized list of changes a designer or engineer can act on — not adjectives. Critique is not redesign; recommend, do not rebuild. When to use - A designer or engineer asks for feedback on a screen, mock, or live UI. - A feature is shipping and someone wants a final UX read. - A flow is suspected of causing user drop-off and you want a pre-research read before instrumentation. When not to use - The user wants a redesign. That is a design project, not a critique. - The work is so early that no concrete artifact exists. Sketch with them instead of critiquing air. - You have no context on the user job. Ask for it first; design critique without user context devolves into taste. Pre-critique context Before opening a screen, get: - Who is the user. Specific role and competence, not "users". - What job they are doing on this screen. One sentence. - What success looks like. What the user can
Explore related resources
Frequently asked questions
What is design-critique?
design-critique is a open-source AI agent skill with Copy skill directory. Give a structured product design critique — user job clarity, hierarchy, affordance, error states, accessibility, and consistency — focused on what to change, in what order, and why.
Who is design-critique best for?
design-critique is best for reusing agent instructions, scripts, and references, design and media workflows, research workflows.
How do I install design-critique?
Install or run design-critique using Copy skill directory. Check design-critique for the latest setup command.
Is design-critique actively maintained?
design-critique may need a closer maintenance check before production use.
Auto-fetched from GitHub.
