ux-scenarios Cursor ruleA
ux-scenarios from ssheleg/super-ux is a Cursor rule: instructions the Cursor agent follows in that repo.
mdr add ssheleg/super-ux/.cursor/rules/ux-scenarios.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-scenarios.mdc- Versions recorded
- 1
- Latest version
- git:20260909.1c2e4ab, committed Sep 9, 2026
- Size
- 3,382 bytes
- Repository stars
- 6
- License
- MIT
Maintain docs/ux/scenarios.md (the UX scenario base): apply when creating or updating UX scenarios, starting any new feature or project, changing user-facing behavior, or onboarding a codebase into scenario-driven development.
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-scenarios — Maintain the Scenario Base `docs/ux/scenarios.md` describes everything the user can do, see, and hit — every feature, button, state, error, result. Keep it true. ## File structure (ux-contract v4) Title, then header comment, then: **Index** table (`| ID | Title | Feature | Persona | Traces | Status | Last audit |`), **Personas** (pointer to foundation.md when it exists, else defined here), **Scenarios** grouped by feature. When `docs/ux/foundation.md` exists, scenarios derive from it: draft per user story / journey stage, fill `Traces:` (e.g. `ST-001 (JTBD-01, JRN-01/#2)`), enforce traceability — every must/should story covered by ≥1 scenario, every scenario serves ≥1 story or job. Scenario entry fields (exact names): `Persona`, `Feature`, `Traces`, `Entry point`, `Preconditions`, `Steps` (numbered, one user action each, paired with the observable system response), `Expected result` (observable), `Alt paths` (meaningful non-error deviations — skip/dismiss/alternate route — omit only when none exist), `UI elements` (every button/field/link/dialog/toast involved — this is what audits check), `States covered` (loading|empty|error|success), …
Read the whole file at its exact version.
How to install
mdr add ssheleg/super-ux/.cursor/rules/ux-scenarios.mdc@sha256:54a6146605d57d73The 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_mv26ejktbhiawy7g)
5 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 (3382 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_mv26ejktbhiawy7g GET https://markdownregistry.com/api/v1/resolve?ref=ssheleg/super-ux/.cursor/rules/ux-scenarios.mdc GET https://markdownregistry.com/api/v1/blob/54a6146605d57d7359e3258267819ccfe2a6970fe938112b99d000bf2a5a7c9c
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