
Product Designer
Run a structured UI critique against Nielsen heuristics, Gestalt, and accessibility checkpoints before you ship screens.
Overview
product-designer is an agent skill most often used in Ship (also Build, Validate) that generates heuristic UI critiques with severity ratings using Nielsen, Gestalt, and accessibility checkpoints.
Install
npx skills add https://github.com/borghei/claude-skills --skill product-designerWhat is this skill?
- Evaluates designs against Nielsen's 10 usability heuristics with per-heuristic checkpoints
- Includes Gestalt principles and accessibility standards in the critique framework
- Python CLI: --checklist, --answers answers.json, optional --json report output
- Produces structured critique with severity ratings and improvement suggestions
- Standard-library-only script for local design review workflows
- Nielsen's 10 usability heuristics with checkpoint lists per heuristic
Adoption & trust: 3.5k installs on skills.sh; 227 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have screens ready to ship but no consistent way to score usability risks beyond subjective "looks fine" feedback.
Who is it for?
Indie frontend builders who want a repeatable Nielsen-style checklist and JSON-driven critique runs in the terminal.
Skip if: Teams needing automated pixel diff, full WCAG scan, or generative UI layout from scratch.
When should I use this skill?
User needs UI design critique, heuristic evaluation, or structured design review against Nielsen, Gestalt, and accessibility standards.
What do I get? / Deliverables
You receive a structured design critique report with rated issues and actionable improvements before launch.
- Structured critique report with severity ratings
- Improvement suggestions mapped to heuristics
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Pre-ship design review is the canonical moment to score usability gaps with severity—after UI exists but before users hit production friction. Review subphase covers heuristic evaluation and quality gates that complement code review for frontend work.
Where it fits
Score a click-through prototype for visibility of status and jargon before you commit to engineering.
Critique navigation and feedback patterns on implemented components mid-sprint.
Run answers.json through design_critique.py and fix high-severity usability issues pre-release.
How it compares
Use as a heuristic design checker instead of treating generic code review as a substitute for usability evaluation.
Common Questions / FAQ
Who is product-designer for?
Solo builders and small teams shipping web or app UI who want Nielsen heuristic critiques with severities without hiring a dedicated UX reviewer for every iteration.
When should I use product-designer?
During ship review before release, while building frontend when polishing flows, or when validating a prototype—run the checklist or pass answers.json for a structured report.
Is product-designer safe to install?
The bundled script uses Python stdlib only; still review the Security Audits panel on this page and inspect the repo before running CLI in CI.
SKILL.md
READMESKILL.md - Product Designer
#!/usr/bin/env python3 """ Design Critique Generator Evaluates a UI design against established heuristics (Nielsen's 10, Gestalt principles, accessibility standards) and generates a structured critique report with severity ratings and improvement suggestions. Uses ONLY Python standard library. Usage: python design_critique.py --checklist python design_critique.py --answers answers.json python design_critique.py --answers answers.json --json """ import argparse import json import sys from typing import Dict, List # Nielsen's 10 Usability Heuristics NIELSEN_HEURISTICS = [ { "id": "N1", "name": "Visibility of system status", "description": "The design keeps users informed about what is happening through appropriate feedback within reasonable time.", "checkpoints": [ "Loading states are visible for operations >1 second", "Progress indicators shown for multi-step processes", "Success/error feedback appears after user actions", "Current location is clear in navigation", ], }, { "id": "N2", "name": "Match between system and real world", "description": "The design uses language, concepts, and conventions familiar to the user.", "checkpoints": [ "Labels use user language, not internal jargon", "Icons follow established conventions", "Information appears in natural and logical order", "Metaphors match real-world expectations", ], }, { "id": "N3", "name": "User control and freedom", "description": "Users can easily undo, redo, or exit unwanted states.", "checkpoints": [ "Undo is available for destructive actions", "Cancel/back options are clearly visible", "Users can exit flows without losing progress", "Confirmation dialogs for irreversible actions", ], }, { "id": "N4", "name": "Consistency and standards", "description": "Users don't have to wonder whether different words, situations, or actions mean the same thing.", "checkpoints": [ "UI elements behave the same way throughout", "Terminology is consistent across all pages", "Visual patterns (spacing, colors) are consistent", "Platform conventions are followed", ], }, { "id": "N5", "name": "Error prevention", "description": "Good design prevents problems from occurring in the first place.", "checkpoints": [ "Form validation occurs before submission", "Constraints prevent invalid inputs", "Destructive actions require confirmation", "Default values reduce user effort and errors", ], }, { "id": "N6", "name": "Recognition rather than recall", "description": "Minimize the user's memory load by making elements, actions, and options visible.", "checkpoints": [ "Options are visible rather than requiring memorization", "Help and instructions are easily accessible", "Recently used items are easily accessible", "Search and filter options are visible", ], }, { "id": "N7", "name": "Flexibility and efficiency of use", "description": "Accelerators allow experienced users to speed up interaction.", "checkpoints": [ "Keyboard shortcuts available for frequent actions", "Customizable interface elements", "Shortcuts or recent items for repeat tasks", "Batch operations for power users", ], }, { "id": "N8", "name": "Aesthetic and minimalist design", "description": "Interfaces should not contain irrelevant or rarely needed information.", "checkpoints": [ "Each screen focuses on one pri