ux-flow
Skill0 starsChanged 2 months agoMITView on GitHub
Define user journey, screens, states, and interactions before coding.
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- architecture-decisionSkill
- developer-handoffSkill
- react-fsd-pocSkill
- backendSkill
- component-designSkill
- databaseSkill
- devopsSkill
- prototypeSkill
- supabaseSkill
- testingSkill
- acceptance-criteriaSkill
- product-definitionSkill
- product-discoverySkill
- project-analysisSkill
- user-storySkill
- validationSkill
- security-reviewSkill
- verificationSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use when the task matches: ux-flow, user journey, screen flow.
- Distinctive: line 39
Keep Product validation and engineering verification distinct.
- Distinctive: line 40
Do not claim completion without evidence.
- Distinctive: line 44
Do not start React coding in this skill.
- Distinctive: line 45
Do not invent a full design system without need.
- Distinctive: line 46
Do not skip Product confirmation on ambiguous flows.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
ux-flow
When to use
Use when the task matches: ux-flow, user journey, screen flow.
Purpose
Agree experience behavior so POC implementation follows Product intent.
Inputs
- Feature brief
- User stories
- Acceptance criteria
Process
- Map the primary user journey end to end.
- List screens or steps in order.
- Define loading, empty, error, success, and permission states.
- Confirm journey with Product before architecture or POC.
Outputs
- User journey
- Screen flow
- States
- Interactions
Verification
- Confirm each output exists and is reviewable.
- Keep Product validation and engineering verification distinct.
- Do not claim completion without evidence.
Restrictions
- Do not start React coding in this skill.
- Do not invent a full design system without need.
- Do not skip Product confirmation on ambiguous flows.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.