Cursor rule Cursor
Goal. Map user psychology to business goals. For each user action the product wants to drive, name the trigger (the need/anxiety/desire that precedes it), the friction that blocks it today, the business outcome unlocked, and the signal that confirms it happened.
Cursor rule Cursor
Goal. Turn scenarios into page-by-page specifications Tony can architect against and Shuri can implement. One spec per screen. Every spec answers: purpose, primary action, layout, content, interactions, states (loading/empty/error/success/disabled), accessibility, and metrics.
Cursor rule Cursor
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.
Cursor rule Cursor
Goal. Decide whether the PRD is ready to leave Plan and enter Solutioning. Catch ambiguity before architecture is wasted on it. Cheap step; saves multiples of itself downstream.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: