Detalle del Skill

product-designer

End-to-end product design, research, flows, prototyping, systems, and handoff.

CoincidenciaDirectaRevisado para diseñadores de producto
Fuenteborghei/claude-skillsFuente externa
Instalaciones reportadas4,465Solo señal de popularidad

Revisar antes de usar

La revisión automática comprueba relevancia, no seguridad ni respaldo. Lee las instrucciones de la fuente antes de usar este Skill.

Vista previa guardada

SKILL.md

Este extracto es una copia guardada durante la revisión. La fuente externa contiene la versión completa y actual.

---
name: product-designer
description: >
  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.
license: MIT + Commons Clause
metadata:
  version: 1.0.0
  author: borghei
  category: product-design
  domain: product-design
  updated: 2026-03-31
  tags: [design, ux, ui, figma, prototyping, design-systems]
---
# 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)

| Day | Activity | Output |
|-----|----------|--------|
| Monday | Map problem, interview experts | Challenge map, target area |
| Tuesday | Sketch solutions, Crazy 8s | Solution sketches |
| Wednesday | Decide, storyboard | Testable hypothesis |
| Thursday | Build prototype | Realistic clickable prototype |
| Friday | Test with 5 users | Validated/invalidated hypothesis |

## User Journey Map Template

```
PERSONA: Sarah, Product Manager, goal: find analytics insights fast

STAGE:      AWARENESS    CONSIDER     PURCHASE     ONBOARD      RETAIN
Actions:    Searches     Compares     Signs up     Configures   Uses daily
Touchpoint: Google       Website      Checkout     Setup wizard App
Emotion:    Frustrated   Curious      Anxious      Hopeful      Satisfied
Pain point: Too many     Hard to      Complex      Slow setup   Missing
            options      compare      pricing                   features
Opportunity: 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
Leer la fuente completa en GitHub (abre una página externa)
Contexto

Trabajo relacionado