Building product animations, onboarding walkthroughs, feature demos, or tutorial videos with Remotion. Use when the user says "create a Remotion animation", "animate my product", "build an onboarding video", "make a product demo video", "create a tutorial walkthrough", "render a feature launch video", or "set up Remotion".
Picking the right prioritization framework (RICE, MoSCoW, WSJF, Kano) and applying it to a backlog. Use when the user says "how should I prioritize", "score this backlog", "which framework", "what should we cut", "roadmap prioritization", or "RICE / MoSCoW / WSJF / Kano".
Turning a stack of interview transcripts or research notes into themes, Jobs-To-Be-Done statements, and a recommended next step. Use when the user says "synthesize this research", "I have N interview transcripts", "what did we learn from the user interviews", "pull out the themes", or "what's the JTBD here".
Authoring a Product Requirements Document — the spec a junior dev can build from. Use when the user says "write a PRD", "spec out a feature", "what are the requirements for X", "draft a feature brief", or mentions a feature they want to scope. Pairs with `pr_flow/create-prd.mdc` for the full workflow.
Drafting user-facing release notes from a list of merged PRs, a git log range, or a changelog. Use when the user says "release notes", "what shipped this week", "changelog entry", "write the announcement for X", or shares a PR list.
Drafting weekly or per-meeting updates for different audiences — eng leads, executives, customer success, cross-team partners. Use when the user mentions "weekly update", "exec note", "team update", "Friday recap", "stakeholder email", "status report", or asks for "something to send the team".
Your team's brand system — colors, typography, voice, logo rules, and the surface treatments that make every artifact look like the same studio shipped it. Use whenever generating UI, landing pages, ads, decks, emails, animations, release notes, or any artifact that will be seen by a customer or stakeholder.