wize-ux-scenarios Cursor ruleA
wize-ux-scenarios from qwize-br/wize-development-kit is a Cursor rule: instructions the Cursor agent follows in that repo.
mdr add qwize-br/wize-development-kit/.cursor/rules/wize-ux-scenarios.mdc@git:20261019.207e46cPins git:20261019.207e46c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- Cursor rule
- Repository
- qwize-br/wize-development-kit
- Path
.cursor/rules/wize-ux-scenarios.mdc- Versions recorded
- 2
- Latest version
- git:20261019.207e46c, committed Oct 19, 2026
- First version recorded
- Jun 13, 2026
- Size
- 5,637 bytes
- Repository stars
- 19
- License
- a license file GitHub does not identify
Use quando o PRD estiver validado e precisar produzir o mapa de cenários UX que ancora todo o design.
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 # UX Scenarios **Goal.** Produce a scenario map that anchors all UX work. Eight focused questions; one short answer each. Scenarios are pieces of behavior, not personas — they're how *this* user, in *this* state, tries to accomplish *that* JTBD. Mantis drives. Output lands in `.wize/planning/ux/ux-scenarios.md`. It's the bridge from PM intent (PRD) to designer concreteness (next workflow: `wize-ux-design`). ## Inputs - `.wize/planning/prd.md` (validated) - `.wize/planning/ux/trigger-map.md` (Pepper) - `.wize/planning/brief.md` ## Outputs - `.wize/planning/ux/ux-scenarios.md` ## Steps ### 1. Identify the scenarios A scenario = one (user, state, JTBD) tuple where the product earns or loses. Aim for **3–8 scenarios** that, taken together, cover all backbone stories in the PRD. Rules: - One sentence each at this stage. - Verb-led. *"New manager onboards their first team."* Not *"Manager onboarding."* - Distinct. If two scenarios share trigger + state, collapse them. ### 2. Run the 8-question dialog per scenario (WDS Freya) For each scenario, answer the eight questions. One paragraph per answer. No filler. Cite trigger-map row when relevant. …
Read the whole file at its exact version.
How to install
mdr add qwize-br/wize-development-kit/.cursor/rules/wize-ux-scenarios.mdc@sha256:1cb212e116b9668fThe line at the top of this page pins the label git:20261019.207e46c, 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_o2qvjqek3x5epivg)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jun 13, 2026 and Oct 19, 2026, about one every 128 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261019.207e46c latest | 2026-10-19 | 207e46c | 5,637 B | A | view · diff |
| git:20260613.a8c0f41 | 2026-06-13 | a8c0f41 | 5,555 B | A | view |
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (5637 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
qwize-br/wize-development-kit · 19 stars · license a license file GitHub does not identify · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_o2qvjqek3x5epivg GET https://markdownregistry.com/api/v1/resolve?ref=qwize-br/wize-development-kit/.cursor/rules/wize-ux-scenarios.mdc GET https://markdownregistry.com/api/v1/blob/1cb212e116b9668ff55c134835f5951e11d4613ad3717be62a84704e7470bed7
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 qwize-br/wize-development-kit
Every file in qwize-br/wize-development-kit