Build your own Among Us.

# Build an original game inspired by Among Us

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 private-room browser deduction game called Signal Station, inspired by the hidden-role loop of Among Us. Support four to eight invited players, one secret saboteur, one small original station map, and three original task interactions. Players complete tasks or identify the saboteur through reports, meetings, and votes. Use original characters, maps, writing, sounds, and task designs.

## Design
Use an original top-down station with clear player silhouettes, task indicator, interact/report buttons, connection state, and meeting overlay. Support keyboard movement and touch controls. Meetings use a readable player list, countdown, vote confirmation, and results; do not expose role information in spectators, logs, or client debug panels.

## Features
1. Rooms and roles: create expiring invite-code rooms, require a bounded four-to-eight-player roster, and start with server-assigned hidden roles. Send each client only its own permitted private state and visible public observations.

2. Authoritative play: process movement, interactions, task progress, range checks, cooldowns, and eliminations on the server. Clients submit intentions; they cannot directly set position, complete tasks, or declare another player eliminated.

3. Meetings and votes: report a valid visible incident or call a limited emergency meeting, freeze movement, and run bounded discussion/voting phases. Count one final vote per eligible living player and define skips, ties, and timeout behavior.

4. Outcomes and lifecycle: track shared task completion and living role counts server-side; end once and reveal roles only at the outcome. Offer an explicit host pause/resume for this private pilot, confirmed lobby restart, and a documented disconnect policy.

5. Recovery: save authoritative room snapshots and event revisions server-side, reconnect with expiring scoped tokens, and send a role-filtered resync. Restore interrupted rooms paused within a short retention window; expire abandoned rooms and revoke old match tokens.

## Tech stack
Use TypeScript with a browser canvas UI, a Node.js WebSocket room service, and durable transactional storage for bounded room snapshots. Keep a deterministic fixed-step room engine separate from transport and rendering. Use authenticated session tokens, rate limits, server-side randomness for role assignment, and per-recipient state serialization. A browser-only localStorage implementation cannot provide real shared rooms or hide all roles.

## Data & behavior
Room {id, inviteCodeHash, state, revision, expiresAt, mapVersion}; Player {id, sessionHash, role, alive, position, taskIds, reconnectUntil}; TaskProgress; Meeting {id, phase, endsAt, eligibleVoterIds, votes}; Event {revision, type, privateAudience}; Snapshot. Store secrets server-side and derive public/private views per request.

Acceptance checks and scope:
Test four independent clients, attempted role leakage in all messages, forged task/position actions, out-of-range elimination, duplicate votes, ties, disconnect/reconnect, stale tokens, simultaneous win conditions, and snapshot recovery. Inspect every client payload to ensure another player's hidden role is absent. Exclude copied maps/art, public matchmaking, voice chat, large rooms, and production moderation 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.