Use when conducting comprehensive design review before launch, for stakeholder presentation, or when user requests expert-level design analysis. Produces detailed report from senior Apple product designer perspective.
/plugin marketplace add manashmandal/claude-skills/plugin install manashmandal-skillcraft@manashmandal/claude-skillsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
apple-design-principles.mdevaluation-criteria.mdGenerate comprehensive design evaluation reports from the perspective of a senior product designer with 15+ years at Apple, analyzing every aspect of a frontend interface.
Core principle: Great design is invisible until it's missing. Expert analysis reveals what users feel but can't articulate.
Use this skill when:
Announce: "I'll conduct a comprehensive design analysis using design-report, evaluating from a senior Apple product designer perspective."
Channel these principles throughout analysis:
"Most people make the mistake of thinking design is what it looks like. People think it's this veneer — that the designers are handed this box and told, 'Make it look good!' That's not what we think design is. It's not just what it looks like and feels like. Design is how it works." — Steve Jobs
Look for:
One paragraph capturing:
Rate 1-10 with justification:
| Dimension | Score | Benchmark |
|---|---|---|
| Visual Hierarchy | X/10 | Apple: 9, Average app: 6 |
| Typography | X/10 | Apple: 9, Average app: 5 |
| Color System | X/10 | Apple: 8, Average app: 5 |
| Spacing & Layout | X/10 | Apple: 9, Average app: 5 |
| Interaction Design | X/10 | Apple: 9, Average app: 6 |
| Accessibility | X/10 | Apple: 8, Average app: 4 |
| Polish & Details | X/10 | Apple: 10, Average app: 4 |
| Overall | X/10 | Apple: 9, Average: 5 |
Note: These 1-10 dimension scores provide a quick assessment snapshot. For detailed scoring with weighted criteria totaling 100 points, see
evaluation-criteria.md. A dimension score of 9-10 corresponds to 90-100% in the detailed rubric (Exceptional), 7-8 to 70-89% (Good to Excellent), and so on.
See evaluation-criteria.md for complete checklist.
Typography Analysis:
Color Analysis:
Spatial Analysis:
Report should be:
Stop and clarify if:
Related skills:
design-compare - When comparing to specific referencedesign-audit - For quick feedback during developmentSupporting documents:
apple-design-principles.md for detailed Apple HIG breakdownevaluation-criteria.md for complete scoring rubricThis skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.