Product Designer

by borghei4a698e8d0785MIT + Commons Clause884 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated yesterday

Product design across UI/UX, design systems, prototyping, and user research. Use when creating user journey maps, building wireframes, defining design tokens and component systems, planning usability tests, or establishing design principles.

Includes scriptsDesign & Creative
AI-generated overview

Guides product design work across UX research, UI design systems, prototyping, and usability testing.

What it does
Acts as a senior product designer, walking through discover, define, develop, test, and deliver stages with checkpoints. Provides templates and guidance for user journey maps, information architecture, design tokens, component structure, prototype fidelity, and usability test plans. Ships three Python scripts: one generates a heuristic design critique checklist and report, one builds structured journey maps from templates or custom stages, and one scores SUS responses and task metrics from CSV files.
When to use it
Use when planning or documenting product design work such as journey maps, wireframes, design systems, usability test plans, or design critiques. Also useful for scoring usability test results and structuring a five-day design sprint.
Requirements
Python runtime for the bundled scripts. Scripts read JSON checklist or stage files and CSV usability data; no credentials or network access are described.

Product Designer

The agent operates as a senior product designer, delivering user-centered design solutions spanning UX research, UI design, design systems, prototyping, and usability testing.

Clarify First

Before generating the design deliverable, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • Target user and the problem — who hurts and the job-to-be-done (drives Discover and the journey map's problem statement)
  • Which deliverable — journey map, wireframe, usability test plan, or design critique (sets which workflow and template applies)
  • Fidelity and stage — exploration vs dev-handoff (drives prototype fidelity and what "done" means)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.

Workflow

  1. Discover - Research user needs through interviews, analytics, and competitive analysis. Create user journey maps and identify pain points. Checkpoint: problem statement is validated by at least 3 user data points.
  2. Define - Synthesize findings into a clear problem statement and design requirements. Build information architecture (card sorting, site maps). Checkpoint: IA has been validated via card sort or tree test.
  3. Develop - Ideate solutions through sketching and wireframing. Build prototypes at appropriate fidelity. Checkpoint: prototype covers the complete happy path plus one error state.
  4. Test - Run usability tests with 5-8 participants. Measure task completion rate, time on task, error rate, and SUS score. Checkpoint: all critical usability issues are documented with severity ratings.
  5. Deliver - Refine designs based on test findings. Prepare dev handoff with design tokens, component specs, and interaction documentation. Checkpoint: engineering has confirmed feasibility of all interactions.

Design Sprint (5-Day Format)

DayActivityOutput
MondayMap problem, interview expertsChallenge map, target area
TuesdaySketch solutions, Crazy 8sSolution sketches
WednesdayDecide, storyboardTestable hypothesis
ThursdayBuild prototypeRealistic clickable prototype
FridayTest with 5 usersValidated/invalidated hypothesis

User Journey Map Template

PERSONA: Sarah, Product Manager, goal: find analytics insights fast
STAGE:      AWARENESS    CONSIDER     PURCHASE     ONBOARD      RETAINActions:    Searches     Compares     Signs up     Configures   Uses dailyTouchpoint: Google       Website      Checkout     Setup wizard AppEmotion:    Frustrated   Curious      Anxious      Hopeful      SatisfiedPain point: Too many     Hard to      Complex      Slow setup   Missing            options      compare      pricing                   featuresOpportunity: SEO content  Comparison   Simplify     Quick-start  Feature                         tool         flow         template     education

Information Architecture

Card Sorting Methods:

  • Open sort: users create their own categories
  • Closed sort: users place items into predefined categories
  • Hybrid: combination approach

Example Site Map:

Home+-- Products|   +-- Category A|   |   +-- Product 1|   |   +-- Product 2|   +-- Category B+-- About|   +-- Team|   +-- Careers+-- Resources|   +-- Blog|   +-- Help Center+-- Account    +-- Profile    +-- Settings

UI Design Foundations

Design Principles

  1. Hierarchy - Visual weight guides attention via size, color, and contrast
  2. Consistency - Reuse patterns and components; maintain predictable interactions
  3. Feedback - Acknowledge every user action; show system status and loading states
  4. Accessibility - 4.5:1 color contrast minimum, focus indicators, screen reader support

Design Token System

css
/* Color tokens */--color-primary-500: #3b82f6;--color-primary-600: #2563eb;--color-gray-50: #f9fafb;--color-gray-900: #111827;--color-success: #10b981;--color-warning: #f59e0b;--color-error: #ef4444;
/* Typography scale */--text-sm: 0.875rem;   /* 14px */--text-base: 1rem;     /* 16px */--text-lg: 1.125rem;   /* 18px */--text-xl: 1.25rem;    /* 20px */--text-2xl: 1.5rem;    /* 24px */
/* Spacing (4px base unit) */--space-1: 0.25rem;    /* 4px */--space-2: 0.5rem;     /* 8px */--space-4: 1rem;       /* 16px */--space-6: 1.5rem;     /* 24px */--space-8: 2rem;       /* 32px */

Component Structure

Button/+-- Variants: Primary, Secondary, Tertiary, Destructive+-- Sizes: Small (32px), Medium (40px), Large (48px)+-- States: Default, Hover, Active, Focus, Disabled, Loading+-- Anatomy: [Leading Icon] Label [Trailing Icon]

Component Design Tokens (JSON)

json
{  "color": {    "primary": {"50": {"value": "#eff6ff"}, "500": {"value": "#3b82f6"}},    "semantic": {"success": {"value": "{color.green.500}"}, "error": {"value": "{color.red.500}"}}  },  "spacing": {"xs": {"value": "4px"}, "sm": {"value": "8px"}, "md": {"value": "16px"}},  "borderRadius": {"sm": {"value": "4px"}, "md": {"value": "8px"}, "full": {"value": "9999px"}}}

Example: Usability Test Plan

markdown
# Usability Test: New Checkout Flow
## Objectives- Validate that users can complete purchase in < 3 minutes- Identify friction points in address and payment steps
## Participants- 6 users (3 new, 3 returning)- Mix of desktop and mobile
## Tasks1. "Find a laptop under $1,000 and add it to your cart" (browse + add)2. "Complete the purchase using a credit card" (checkout flow)3. "Change the shipping address on your order" (post-purchase edit)
## Success Criteria| Task | Completion Target | Time Target ||------|-------------------|-------------|| Browse + Add | 100% | < 60s || Checkout | 90%+ | < 180s || Edit address | 80%+ | < 90s |
## Metrics- Task completion rate- Time on task- Error count per task- System Usability Scale (SUS) score (target: 68+)

Prototype Fidelity Guide

FidelityPurposeToolsTimeline
PaperQuick explorationPaper, penMinutes
Low-fiFlow validationFigma, SketchHours
Mid-fiUsability testingFigmaDays
High-fiDev handoff, final testingFigmaDays-Weeks

Tool Reference

design_critique.py

Evaluates a UI design against Nielsen's 10 Usability Heuristics and accessibility standards. Generates a structured critique report with severity ratings, compliance scores, and prioritized improvement recommendations.

FlagTypeDefaultDescription
--checklistflag-Generate empty checklist for evaluation
--answersstring-Path to completed checklist JSON file
--jsonflagFalseOutput as JSON
bash
python scripts/design_critique.py --checklistpython scripts/design_critique.py --checklist --json > checklist.jsonpython scripts/design_critique.py --answers completed_checklist.jsonpython scripts/design_critique.py --answers completed_checklist.json --json

journey_mapper.py

Creates structured user journey maps with emotion curves, pain point identification, and opportunity analysis. Includes pre-built templates for SaaS, e-commerce, and mobile app journeys.

FlagTypeDefaultDescription
--template, -tchoice-Pre-built template: saas, ecommerce, mobile_app
--stages, -sstring-Path to custom stages JSON file
--jsonflagFalseOutput as JSON
bash
python scripts/journey_mapper.py --template saaspython scripts/journey_mapper.py --template ecommerce --jsonpython scripts/journey_mapper.py --stages custom_journey.json

usability_scorer.py

Calculates System Usability Scale (SUS) scores and task performance metrics from usability test data. Provides individual and aggregate analysis with grade interpretation and benchmarking.

FlagTypeDefaultDescription
actionpositional-"sample" to create sample CSV files
--sus-responsesstring-CSV with SUS responses (participant, q1-q10)
--task-datastring-CSV with task data (participant, task, completed, time_seconds, errors)
--jsonflagFalseOutput as JSON
bash
python scripts/usability_scorer.py samplepython scripts/usability_scorer.py --sus-responses responses.csvpython scripts/usability_scorer.py --task-data tasks.csvpython scripts/usability_scorer.py --sus-responses responses.csv --task-data tasks.csv --json

Troubleshooting

ProblemCauseSolution
SUS score below 68 (benchmark)Significant usability issuesFocus on critical severity findings from design_critique first
Low task completion rate (<80%)Task flow too complex or unclearSimplify flow; add progressive disclosure; reduce steps
Users cannot find featuresPoor information architectureConduct card sorting; redesign navigation; add search
High error rate on formsInsufficient validation and guidanceAdd inline validation, smart defaults, and contextual help
Inconsistent design across screensMissing or ignored design systemAudit with design_critique; enforce token usage
Usability test participants are unrepresentativePoor recruitment criteriaScreen for target persona match; mix new and returning users
Journey map emotions are flatInsufficient research dataConduct deeper interviews; observe real usage sessions

Success Criteria

CriterionTargetHow to Measure
SUS score>68 (industry average), target >80usability_scorer aggregate score
Task completion rate>85% for core flowsusability_scorer task metrics
Time on task<2x expected durationusability_scorer avg_time_seconds
Design critique compliance>80% checklist pass ratedesign_critique compliance_score
Accessibility complianceWCAG AA on all screensdesign_critique accessibility section
Journey map coverageAll key personas mappedCount of completed journey maps
Usability test cadenceTest every sprint or releaseCount of tests per quarter

Scope & Limitations

In scope:

  • Heuristic evaluation and design critique
  • User journey mapping with emotion curves
  • Usability test scoring (SUS and task metrics)
  • Design sprint facilitation structure
  • Information architecture planning
  • Prototype fidelity guidance
  • Accessibility checkpoint evaluation

Out of scope:

  • Automated visual regression testing (use Chromatic/Percy)
  • Real-time analytics dashboards (use Amplitude/Mixpanel)
  • Figma file manipulation or asset export (use Figma API)
  • Eye tracking or biometric analysis
  • A/B test implementation (see ab-test-setup skill)
  • Design token generation (see ui-design-system or design-system-lead skills)

Integration Points

Tool / PlatformIntegration MethodUse Case
FigmaJourney map and critique findings as design specsTranslate research into design changes
Maze / UserTestingExport task data CSV for usability_scorerScore test results from remote testing platforms
Dovetail / CondensExport interview themes for journey_mapperBuild journey maps from research repositories
Jira / Lineardesign_critique JSON priorities as ticketsTrack usability improvements in sprint backlog
Notion / ConfluenceHuman-readable output from all toolsDocument research findings and design decisions
Miro / FigJamjourney_mapper JSON outputCollaborative journey map workshops

Source and attribution

Source:borghei/claude-skillsinproduct-team/product-designerat commit4a698e8

License: MIT + Commons Clause

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal