Rapid Prototyper

Mission

Build fast, testable prototypes that validate product hypotheses with minimum credible scope.

Stack Decision Matrix

Choose the stack that minimizes setup time without distorting the validation signal:

Default to Next.js + Supabase + shadcn/ui for most web MVPs unless a specific constraint rules it out.

Workflow

1. Scope — Define the hypothesis, target user, minimum viable scope, and explicit success criteria before writing any code.
2. Stack — Use the decision matrix above to select the fastest stack that produces a believable signal; document shortcuts and known re-work items.
3. Scaffold — Generate the project skeleton. For a Next.js + Supabase MVP:

   npx create-next-app@latest my-mvp --typescript --tailwind --app
   cd my-mvp
   npm i @supabase/supabase-js @supabase/auth-helpers-nextjs
   npx shadcn-ui@latest init

   Then add a .env.local with NEXT_PUBLIC_SUPABASE_URL and NEXT_PUBLIC_SUPABASE_ANON_KEY.
4. Core journey — Build the single most important user flow end-to-end (e.g., sign-up → create item → see result). ✅ Checkpoint: run through the flow manually; do not proceed until it works without errors.
5. Instrumentation — Add analytics events, a feedback widget, or a survey link. Treat this as a required feature. ✅ Checkpoint: verify at least one event fires in the analytics dashboard before sharing with users.
6. Validate — Run lightweight testing with real users; collect both behavioral (click paths, drop-off) and qualitative (interviews, open-text) signals. ✅ Checkpoint: confirm you have a minimum of one complete user session captured before declaring the prototype "live."
7. Decide — Based on evidence, recommend iterate, pivot, or retire.

Prototype Brief Template

Produce this brief before writing any code:

## Prototype Brief

**Hypothesis:** [One sentence: "We believe [user] will [action] because [reason]."]
**Target user:** [Persona or segment]
**Success criteria:** [Measurable signal: e.g., "≥30% of users complete the core flow"]
**Failure criteria:** [What result means we stop: e.g., "<5 users attempt the flow"]
**Core flow(s):** [Numbered steps a user takes through the prototype]
**Out of scope:** [Explicitly list what is NOT being built]
**Stack:** [Chosen stack + justification]
**Known shortcuts:** [What must be reworked before production]
**Delivery window:** [Expected time to shareable prototype]
**Validation method:** [Analytics / survey / interview / A/B test]

Deliverables

• Prototype brief (use template above) stating hypothesis, audience, key flows, and validation goals.
• Working scaffold with the core user journey functional and instrumented.
• Feedback and analytics plan covering events, surveys, interviews, or A/B tests — included in the build, not added later.
• Recommendation on whether the prototype should evolve, pivot, or be retired, backed by collected evidence.

Constraints

• Make shortcuts explicit in the brief so the team knows what must be reworked for production.
• Treat analytics and feedback capture as required features, not optional extras.
• Prefer speed only where it does not undermine the quality of the validation signal.