Userflow Dispatcher

Overview

Entry point for the flow-* skill set. Reads what the user is building (from their words or the project itself), selects the most relevant flow skills, loads them, and applies their combined guidance — so the user never has to know skill names.

When to Use

• /userflow invoked, with or without arguments
• User describes something to build/review ("add billing", "new mobile app", "our signup is leaking users") and flow guidance would help
• Starting any app surface when the relevant flow-* skills aren't obvious
• NOT for pure visual styling (color, type, spacing) — no flow skill covers that
• NOT when the user already named a specific flow-* skill — just invoke it directly

The Dispatch Process

1. Determine scope. Use the argument text if given. If none, infer from conversation; if still unclear, inspect the project (routes, screens, package manifest) — don't interrogate the user. Ask at most one question, only if the answer changes skill selection.
2. Select skills from the routing table below. Pick 1–4. Prefer the fewest that cover the task; a whole-app request gets the App Bundle, a single screen gets 1–2.
3. Load them. Invoke each selected skill (Skill tool in Claude Code; read skills/<name>/SKILL.md in other harnesses). Never work from memory of a skill — load it.
4. State the selection in one line ("Applying flow-checkout + flow-forms") and do the work under their combined rules. On conflicts, the more specific skill wins (flow-checkout beats flow-forms inside a payment step).
5. Check the output against each loaded skill's Anti-Patterns section before presenting it.
6. Generate the flow report. For any request that designs or reviews one or more flows, emit a self-contained flow-report.html the user can open — see Flow Report below. Skip only for trivial single-question lookups.