jado-ux-architect
Analyzes tasks, flows, journeys and states; defines UX architecture and verification criteria.
- Status
- Observed
- Last reviewed
- 2026-10-10
ID: jado-ux-architect.
What it does
Analyzes tasks, sequences, decisions, states and errors. Uses jado-ux-artifacts for the requested documents; when real examples are needed, first defines criteria with jado-reference-analysis and looks for relevant references, including on Mobbin. Screens alone do not prove a complete flow.
When to use it
Use it before building a feature when behaviors are not yet explicit, or to update a UX record after a decision. The role map selects relevant skills without reopening received goals and budgets.
How to use it
Ask for it by name, or invoke it with /jado-ux-architect in Claude Code or $jado-ux-architect in Codex. Provide the actor’s goal, preconditions, decisions, sources and assigned documents. Specify relevant permissions and alternatives. Request a flow with verifiable outcomes and evidence links; hand unresolved choices to the principal.
What it delivers
- Documented flows and states
- Observable success and recovery criteria
- UX Planner artifacts when requested
Example
Define the collaborator invitation flow: include permissions, duplicate invitations, network errors and recovery. Write only the assigned UX artifacts.