renatoasse/ibeia-skills/dont-make-me-think

Don't Make Me Think

Audit an existing journey, then rebuild it so the user never has to think. Three engines drive every decision:

1. Clarity (Krug/Nielsen) — every screen self-evident, one obvious next step.
2. Simplicity (Maeda/Tesler) — hide complexity until it's needed; the product absorbs it, never the user.
3. Flow (game-feel, calibrated) — clear goal, instant feedback, visible progress, celebrated wins. Never dark patterns.

The unit of work is the JOURNEY (a flow), not the isolated screen. Zoom into screens only after walking the flow end to end.

Announce at start: "Using dont-make-me-think to audit and rebuild [journey]."

The Process — 3 phases, 1 gate

AUDIT ──► Friction Map ──► BLUEPRINT ──► 🚦 user approves? ──► REBUILD ──► re-run audit on result
                                              │ no
                                              ▼
                                        revise blueprint

Phase 1 — AUDIT → Friction Map

Read reference/audit.md and follow it. Walk the journey in code AND live in the browser (Playwright) when a URL is reachable. Produce a prioritized Friction Map (P0–P3) with evidence. Do NOT propose fixes yet — this phase only collects friction.

Phase 2 — BLUEPRINT → approval gate 🚦

Read reference/clarity.md, reference/simplicity.md, reference/flow.md (the three engines), then reference/blueprint.md (the output format). Rebuild the journey ON PAPER. Present the blueprint and STOP. Do not touch code until the user explicitly approves.

Phase 3 — REBUILD → verified code

Implement the approved blueprint following the repo's existing patterns. Verify by RE-RUNNING the Phase 1 walkthrough and trunk test on the result — the audit is the acceptance test. Delegate purely visual work (palette, typography, ornament) to impeccable/frontend-design when it makes sense: dont-make-me-think owns the experience decision, not the pixels. Commit in atomic units per the repo's conventions.

Surface calibration — declare it at the top of every blueprint

Fundamentals apply ALWAYS — they are what makes any app feel good. Strong mechanics (streaks, variable rewards, levels) NEVER appear by default outside the third row. If the user explicitly asks to crank it up, move one row down.

Red flags — stop and reconsider