ui-ux-pro-max
This skill encodes the audit methodology of a senior product designer — not heuristics, but a five-layer evaluation that asks whether the UI earns user trust, reduces cognitive load, and actually delivers the business outcome the product promises.
Qué hace esta skill
- Evaluates design across 5 layers in sequence (first impression → task flows → visual system → trust → business alignment)
- Produces findings tagged by severity: Critical / Major / Minor
- For each finding: location, problem, why it matters, specific recommended fix
- Generates a quick-wins list: 3 changes that have outsized impact for under 30 minutes of work
- Outputs a prioritized action plan, not just a list of problems
Cuándo usarla
- Before a launch, pitch, or investor demo — you need an honest read, not reassurance
- When conversion is low and you don't know why
- When the product "works" but users drop off or complain it's confusing
- When you've been staring at the design too long to see its problems
Proceso
- Share the design: Screenshots, Figma link, or a live URL — describe the product's core user task and business goal in one sentence
- Layer 1 — First impression (0-5 seconds):
- What does a new user understand immediately?
- What is the primary CTA? Is it obvious?
- Is visual hierarchy working or competing?
- Layer 2 — Task flows:
- Pick the 2-3 most important user tasks
- Walk each step: dead ends, unnecessary clicks, cognitive load spikes, confusing labels
- Measure: how many steps to complete core task? Any back-navigation required?
- Layer 3 — Visual consistency:
- Typography system (controlled or ad hoc?)
- Color usage (semantic vs. decorative?)
- Spacing (systematic or arbitrary?)
- Icon family consistency
- Layer 4 — Trust signals:
- Social proof: present, credible, specific?
- Error states: helpful or just red boxes?
- Empty states: designed or blank voids?
- Loading states: communicated or ignored?
- Layer 5 — Business alignment:
- Does the UI surface the product's core value proposition?
- Does the CTA match user readiness at each stage of the flow?
- Is there a mismatch between what the product promises and what the screen shows?
- Output: Severity-tagged findings + quick wins list + prioritized fix order
Finding format
[CRITICAL/MAJOR/MINOR] — Screen: <name> | Element: <name>
Problem: <what's wrong>
Why it matters: <user impact or business cost>
Fix: <specific recommended change>
Ejemplo de prompt
Aquí están los screenshots de mi app de reservas para restaurantes. El onboarding tiene baja conversión — la gente llega a la pantalla de "elige tu mesa" y se va. Audit completo por favor.
Relación con otras skills
| Situación | Skill |
|---|---|
| El problema no es el flujo sino el visual — bordes, tipografía, espaciado | refactoring-ui |
| Quieres entender si el UI comunica el job correcto que los usuarios contratan | jobs-to-be-done |
| La investigación de usuarios aún no está hecha | mom-test |