ux-flows Cursor ruleA
ux-flows from ssheleg/super-ux is a Cursor rule: instructions the Cursor agent follows in that repo.
mdr add ssheleg/super-ux/.cursor/rules/ux-flows.mdc@git:20260909.1c2e4abPins git:20260909.1c2e4ab in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- Cursor rule
- Repository
- ssheleg/super-ux
- Path
.cursor/rules/ux-flows.mdc- Versions recorded
- 1
- Latest version
- git:20260909.1c2e4ab, committed Sep 9, 2026
- Size
- 4,012 bytes
- Repository stars
- 6
- License
- MIT
Design or improve user flows (docs/ux/flows.md): apply for task analysis, flow diagrams, screen states, wireframes, heuristic UX evaluation, or any 'improve/fix the UX' request.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# ux-flows — Design HOW Users Move `docs/ux/flows.md` is the HOW layer between foundation (stories) and scenarios: task analysis + mermaid user flows referencing screens by `SCR-ID`. The canonical per-screen spec lives in `docs/ux/screens.md` — the UI map: every screen and state with its Figma frame, wireframe, code coverage, scenarios, and resources. IDs `FLW-NN`/`SCR-NN`, sequential, never reused. Any interface change updates `screens.md` (and the Figma frame when enabled) in the same change — a screen whose code diverges from its record is `drifted`. ## Flow entry (ux-contract v4) Fields: `Traces` (story/job IDs), `Goal` (observable end state), `Entry points` (ALL of them), `Success exit`, `Task analysis` (numbered user-visible micro-steps), mermaid `flowchart` (screens as `Screen: <name>`, decisions as diamonds, `*_err` error nodes with labeled recovery edges), `Screens traversed` table (`| Screen | States used here |` — SCR-IDs only; the full per-screen spec lives once in `screens.md`). Each screen entry in `screens.md`: `Used by`, `Purpose`, `Elements` (mark the ONE primary action), `States` table (`| State | Trigger | Figma frame | …
Read the whole file at its exact version.
How to install
mdr add ssheleg/super-ux/.cursor/rules/ux-flows.mdc@sha256:3f5857c889cfd115The line at the top of this page pins the label git:20260909.1c2e4ab, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_brbzcao4wcca3iwb)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 9, 2026.
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (4012 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
ssheleg/super-ux · 6 stars · license MIT · pushed 2026-11-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_brbzcao4wcca3iwb GET https://markdownregistry.com/api/v1/resolve?ref=ssheleg/super-ux/.cursor/rules/ux-flows.mdc GET https://markdownregistry.com/api/v1/blob/3f5857c889cfd11542578c5ed01e8484ec9c2161dbb52d10bf990e20f5684bc8
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: Cursor rules vs AGENTS.md · which agent file does what.
More from ssheleg/super-ux
Every file in ssheleg/super-ux