Files
game-scoreboard/README.md
T
joshuaandClaude Opus 5.5 c89a82295b Phase 0: scaffold Next.js, Tailwind tokens, Supabase clients, env validation
Next.js 16 App Router with strict TypeScript, Tailwind 4 theme tokens from
docs/UI.md, Vitest, and the three Supabase clients. Env vars are validated
with zod in next.config.ts so dev and build fail fast with a readable error.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-03 12:27:11 +02:00

2.0 KiB

Game Night Live — build pack

A spec pack for Claude Code. It builds a live scoring app for youth game nights: an admin control room, a projector scoreboard, and per-game judge links.

What's in here

File What it's for
CLAUDE.md Rules Claude Code reads automatically every session
docs/KICKOFF_PROMPT.md The first message you paste into Claude Code
docs/PRD.md Features, roles, user flows
docs/ARCHITECTURE.md Stack, routes, realtime, security model
docs/DATA_MODEL.md Tables explained
docs/SCORING.md Exact scoring math (judges, averages, placement points, bonuses)
docs/UI.md Screens + design direction
docs/BUILD_PLAN.md Phased tasks with acceptance criteria
supabase/migrations/0001_init.sql Starting schema + RLS
.env.example Env vars you'll need

Setup (≈15 min, before you open Claude Code)

  1. Supabase — create a free project at supabase.com.
    • Settings → API: copy the Project URL, anon key, and service_role key.
    • Authentication → Providers: make sure Email is on (magic link is fine).
  2. Vercel — free account, connect GitHub (for deploy at the end).
  3. Node — install current LTS. Check with node -v.
  4. Unzip this folder somewhere, git init, open it in WebStorm.
  5. Copy .env.example → .env.local and paste in your Supabase values + your admin email.

Running Claude Code in WebStorm

  • Install the Claude Code plugin from JetBrains Marketplace (or just run claude in WebStorm's terminal from the project root).
  • Open docs/KICKOFF_PROMPT.md, paste its contents into Claude Code.
  • Let it go phase by phase. After each phase: run it, click around, commit, then say "next phase".

Tips

  • Keep docs/ as the source of truth. If you change your mind on a feature, edit the doc first, then tell Claude Code "I updated PRD.md section X, implement it".
  • Test the scoreboard on the actual projector PC + one judge on a phone before game night. Wi-Fi at church is the #1 thing that'll bite you.