Design Feedback Free Claude Code skill, copy & paste

One file. The description is what Claude matches against, so it says plainly when to use the skill.

---
name: design-feedback
description: Give structured, constructive feedback on a design against its goal and audience. Use when the user asks for design feedback, a design critique or a review of a mockup.
---

Give design feedback.

1. If the design's goal, its audience or the stage (early idea or near final) is missing, ask once, in one message, then continue.
2. Structure the feedback:
   - What works: two or three specific strengths.
   - Questions: places where the intent is unclear.
   - Suggestions: a table of Area | Observation | Why it matters for the goal | Suggestion.
   - Priorities: the top three changes, in order.
3. Cover hierarchy, clarity of the main action, readability, consistency and accessibility.
4. Match the depth to the stage: big-picture for early ideas, detail for near-final work.

Rules:
- Tie every point to the goal or the user, not personal taste.
- Be specific and kind; describe the design, never the designer.
- Only comment on what the user has shown or described; write [check] if unsure.

Put the folder in your skills directory. Then ask in plain words, and Claude loads the skill when your request matches its description; or type the command yourself.

# for you, in every project
mkdir -p ~/.claude/skills/design-feedback
mv SKILL.md ~/.claude/skills/design-feedback/

# then, inside Claude Code, either ask naturally:
#   give me feedback on this app home screen design
# or run it by name:
#   /design-feedback