Build your own Kahoot!.

# Build an original game inspired by Kahoot!

You are an experienced game designer and gameplay engineer. Build a working, polished MVP from the brief below. Implement the core journeys end to end; a static mockup is not sufficient. Inspect the current environment, make sensible implementation decisions, and get started. Ask a question only if a missing answer genuinely blocks implementation.

Starting platform: Web. Explicit customized Product & audience and Tech stack requirements take precedence over this starting target.

## Product & audience
Build an original live quiz game called Quizroom, inspired by Kahoot. A host authors original multiple-choice questions, opens a room, and runs timed rounds while players join from their browsers. The server owns the timer, answers, and score calculation. Start with a small adult/test classroom group using pseudonyms and no player accounts.

## Design
Create an original host presentation and a separate mobile-friendly player screen with clear room-code entry, large answer buttons, text labels, and accessible color/shape cues. Distinguish lobby, question, submitted, reveal, leaderboard, and finished states. Use original art and sound.

## Features
1. Quiz authoring: create draft/published quizzes with original questions, answer options, one correct answer, and bounded round durations. Validate every question and freeze a quiz snapshot when a session starts.

2. Room and lobby: issue unguessable internal session IDs and rate-limited human-friendly room codes, limit room size, allow the host to remove a participant, and give reconnecting players a private recovery token.

3. Authoritative rounds: let only the host advance, publish question/options without the answer key, use server deadlines, and accept at most one answer per player/round. Never trust client timers or claimed response times.

4. Scoring and reveal: define a deterministic correctness/time scoring rule, compute results once after the deadline, reveal correct answers only at the proper phase, and show standings and a final podium from stored scores.

5. Recovery and reports: recover a player after refresh, prevent a second device from impersonating another player, stop orphaned rooms, and export a host-only result summary with an explicit retention policy.

## Tech stack
Use TypeScript browser host/player clients, a Node.js WebSocket server, and PostgreSQL for quiz versions, sessions, and answers. Persist phase transitions and score results; use server timestamps and an injectable clock for rule tests. No client may receive unpublished answer keys.

## Data & behavior
Quiz; QuizVersion; Question; AnswerOption {correct}; Session {phase, currentRoundId}; HostSession; Player {nickname, recoveryTokenHash}; Round {opensAt, deadline}; Submission {playerId, roundId, optionId, acceptedAt}; RoundScore; FinalResult. Use uniqueness and phase guards for answers and scoring.

Acceptance checks and scope:
Test early/late/duplicate answers, simultaneous host advances, a reconnect mid-round, repeated scoring, hidden answer keys in network payloads, tied scores, and an expired room code. Play with one host and three browser sessions. Exclude copyrighted question sets, paid plans, school rostering, and claims of child-ready public operations.

## Originality and assets
The named product is a reference for general workflows only. Use an original product name, visual identity, wording, layout, and assets. Do not copy proprietary code, branded logos, distinctive screens, private APIs, paid templates, or protected media. Use original or appropriately licensed sample data and assets. Build from this brief rather than scraping the reference service. Do not imply affiliation with the referenced company.

## Implementation quality
- Make every visible control work, with clear loading, success, empty, validation, and failure states. Remove controls for unimplemented features.
- Support the target platform and responsive or resizable layouts where appropriate. Use platform-appropriate accessibility semantics, labels, keyboard operation, visible focus, sufficient contrast, and reduced-motion preferences. Provide alternatives for drag-only interactions.
- Validate inputs at the relevant boundary. Treat imported or user-generated content as untrusted; render it safely. Confirm destructive actions or offer undo.
- Keep state changes reliable across navigation and reloads. Never silently lose edits. Handle persistence and network errors with an actionable message.
- Keep the scope realistic. Prioritize the complete primary journey. If a custom Features section differs from the baseline, update the data model, design, and acceptance checks to match it; explicit custom requirements take precedence over baseline assumptions.
- Provide realistic original sample content and a useful empty state. Keep sample data clearly separate from user-created data.

## Delivery and verification
1. Inspect the repository and outline the implementation in a few sentences.
2. Implement the app and connect its actual data flow. Continue until the primary journey works.
3. Run appropriate checks and test the acceptance cases above on the target platform. Verify responsive layouts and keyboard navigation when browser tools are available. For native projects, build with the available SDK and test an emulator or device when possible; report any missing native verification honestly. For games, verify the rules and gameplay loop, not only the menus.
4. Fix observed failures, then provide the runnable result, setup/run instructions, a brief explanation of what is implemented, and any specific configuration or verification limits.

This is a focused MVP. Do not add billing, AI services, or unrelated features unless explicitly requested in the brief. Start building now.