app-investigate-default.txt

❯ how does this app work

⏺ Bash(date '+%Y-%m-%d %H:%M:%S %z')
  ⎿  2026-03-07 19:43:19 -0800

⏺ Based on the CLAUDE.md and project structure, here's how Demo Kit works:

  What It Is

  A web platform for structured demo nights and project showcases. Think: hackathon demo day as a service.

  Core Flow

  1. Creators build demo entries by linking a GitHub repo, adding metadata (description, tags, tech stack), and optionally uploading a screencast
  2. Organizers create events and curate which demos appear in them
  3. Audiences attend events and vote on demos via a live leaderboard

  Key Concepts

  Two-track demo state:
  - status (draft → complete) — are all required fields filled?
  - visibility (private → public) — who can see it?
  - Must be complete before going public or submitting to events

  Two voting systems:
  - Public upvotes — persistent social proof (like GitHub stars)
  - Event audience votes — live ranking during events (points-by-position)

  Hybrid ownership: Demos are reusable assets. One demo can appear in many events. Every demo has a team (solo = team of one).

  Tech Stack

  - Next.js 16 (App Router) + React 19 + TypeScript
  - Supabase for Postgres, Auth (GitHub/Google/email), Storage, and Row-Level Security
  - Tailwind CSS v4 with a 3-layer design token system (raw → semantic → theme)
  - Deployed on Vercel

  Current State

  Working scaffold with auth, role system, dashboard, and a 3-step demo creation wizard. Event management, voting, and public browsing are not yet built (steps 6–11 in the build order).

  Want me to dive deeper into any specific part?