wize-ux-scenarios rulesA
wize-ux-scenarios is agent-read markdown (rules) from qwize-br/wize-development-kit: 2-plan: UX Scenarios.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns 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@git:20260613.a8c0f41mdr add qwize-br/wize-development-kit/.cursor/rules/wize-ux-scenarios.mdc@sha256:779ebe95ca49679dPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_o2qvjqek3x5epivg)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (5555 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 · 16 stars · license NOASSERTION · pushed 2026-09-23 · 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/779ebe95ca49679de59040ea533df320877db36d3d0cb28c3f657611fe71170f
Your agent 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.