KeyanVakil/demo-mode

Make the app demo-proof.

Steps

1. Read the auth flow and understand how sessions/tokens work.

2. Add a demo mode that can be toggled via:

   • An env var: DEMO_MODE=true
   • OR a query param: ?demo=true
   • OR a hardcoded demo account (email: demo@demo.com, password: demo) Choose whichever fits the existing auth architecture.

3. In demo mode:

   • Bypass auth checks or auto-login as the demo user
   • Return hardcoded/mock data from API routes instead of hitting the real DB
   • Pre-populate any forms with realistic default values
   • Disable any destructive actions (delete, payment, send email) or make them no-ops with a toast: "Demo mode — action disabled"

4. Add a visible demo mode banner: a small sticky bar at the top that says "Demo Mode" so judges know it's intentional.

5. Make sure demo mode is off by default in production (gate it on the env var or a non-guessable param).

Rules

• Don't break the real auth flow — demo mode should be additive, not a replacement
• Keep mock data in one place (a lib/demo-data.ts or equivalent) so it's easy to update
• The demo flow should cover the app's single most impressive feature from start to finish
• If there are API calls to external services (LLMs, payments), stub them in demo mode to avoid costs and failures