[01] LOOP
ProductmanualHardened

Signup Flow Until Smooth

Walk register-through-onboard in the browser, annotate friction points, fix UX blockers, and repeat until the flow is smooth.

by Trooper

Kickoff prompt
Start the "Signup Flow Until Smooth" loop.

Goal: signup through first value moment completes without friction blockers
Max iterations: 10
Between iterations run: Complete signup flow in browser and verify no annotated blockers remain
Exit when: full signup-to-onboard path completes with zero open friction annotations

Step 1: Walk register-through-onboard in browser, annotate friction, fix blockers, and retest.

## Before you start

Connect plugins:
- Browser / Web access (required) — Open pages, inspect live state, collect evidence, and verify changes.
- Support tickets (required) — Read customer tickets, feedback, onboarding gaps, and support themes.
- CRM (required) — Read accounts, deals, owners, stages, and onboarding state.
- Linear / Jira (required) — Read roadmap, task, bug, owner, and status context.
- Figma (required) — Inspect designs, dimensions, assets, and handoff notes.

Attach skills:
- Loop runner (required) — Self-pace iterations, run the check between passes, and stop only on the exit condition.
- Customer operations (optional) — Identify at-risk accounts, missing setup steps, and safe next actions.
- Approval workflows (optional) — Keep outbound actions in draft or approval states when risk is non-trivial.
- Visual design QA (optional) — Compare implementation against visual expectations and capture regressions.
- Browser QA (optional) — Exercise product flows, capture visual evidence, and verify fixes in-browser.

Self-pace this loop. After each iteration, run the check command, read the output, and only continue if the exit condition is not met. Stop when the exit condition passes or max iterations is reached. Give a short status update each pass.

Paste the kickoff prompt into Cursor, Claude Code, or Codex. Deeplinks do not install hook files.

Steps

1. Walk the flow

Register a test account and complete onboarding in the browser.

2. Annotate friction

Screenshot confusing steps, errors, and drop-off points with notes.

3. Fix and retest

Patch UX blockers, then re-walk the flow from scratch.

Flow diagram

Guardrails

Rules the agent must follow so it cannot cheat the exit condition.

  • Use test accounts — do not create production users without cleanup
  • Screenshot and annotate every friction point before fixing
  • Do not remove validation to mask UX problems

More Product loops