Build your own Snake.

# Build an original game inspired by Snake

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 browser Snake game called Garden Coil. Guide a growing creature around a fixed grid, collect food, and avoid the defined obstacles. Use the classic Snake genre as a reference with your own artwork, instructions, and sound. Deliver an accurate discrete movement loop that works on keyboards and touch screens.

## Design
Use an original garden theme with readable grid cells, directional buttons, score, speed selection, and pause/restart. Make the creature head, body, food, and boundaries distinguishable by shape. Keep touch controls below the board so fingers do not cover play, and avoid animation-dependent hit detection.

## Features
1. Movement: advance one cell per simulation tick using a bounded direction queue. Prevent immediate reversal into the current neck and validate queued turns against the direction at the tick they will execute.

2. Growth and food: place seeded-random food only in unoccupied cells; eating grows the body and increments the score. If the board fills, enter a completed state instead of attempting an endless spawn loop.

3. Collision: provide one documented wall-bounded mode. Resolve collision using the next body state, including allowing movement into a tail cell that vacates on a non-growth move.

4. Run controls: choose a small fixed set of speeds, pause/resume, auto-pause on focus loss, and confirm restart during a live run. Clear queued input on pause and restart, and support keyboard, swipe, and directional buttons.

5. Local progress: save the snake, food, direction, speed, seed, and score when paused and at bounded intervals. Restore paused, retain best scores per speed, and support validated JSON save export/import.

## Tech stack
Use TypeScript with a pure grid-state reducer and a fixed-step loop independent of the UI. A Canvas renderer or DOM board is enough. Use an injectable seeded random generator for food and tests. Keep direction buffering separate from browser key repeat, and implement a versioned local storage adapter with clear failure feedback.

## Data & behavior
Run {size, bodyCells, direction, queuedDirections, foodCell, tickInterval, score, seed, rngState, status}; Records keyed by mode/speed; Settings. Validate that imported body coordinates are unique, connected, in bounds, and compatible with the configured rules.

Acceptance checks and scope:
Test reversal rejection, two rapid turns before a tick, eating near a wall, moving into a vacating tail, a fully occupied board, and a resumed run at a different display refresh rate. Test touch controls and storage denial. Exclude copied Nokia visuals, online multiplayer, and speed changes that silently alter a recorded run.

## 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.