Build your own Wordle.

# Build an original game inspired by Wordle

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 word game called Lettertrail, inspired by the idea of Wordle. Players solve an original six-letter daily word in seven attempts or choose a practice puzzle. Create a distinct identity, layout, feedback palette, and original instruction wording. Use an independently sourced, licensed word list; do not copy NYT puzzle schedules, answer lists, code, or visual presentation.

## Design
Use a responsive notebook-style layout with a current-word input, a vertical history of guesses, and a compact keyboard. Mark exact, misplaced, and absent letters using shapes and text as well as an original color palette. Announce feedback accessibly, respect reduced motion, and keep keyboard and touch input equivalent.

## Features
1. Puzzle selection: choose one valid six-letter answer from an owned or permitted answer list using a documented date zone and deterministic schedule. Keep practice sessions separate and avoid repeating recently played practice answers.

2. Guess validation: accept only the configured alphabet and length, validate against the permitted dictionary, and reject invalid submissions without consuming an attempt. Lock submissions after the win or final loss.

3. Letter evaluation: first mark exact matches and consume those answer-letter counts, then allocate misplaced matches only from the remaining counts. Duplicate letters cannot receive more positive marks than the answer contains.

4. Play controls: support physical keys, on-screen keys, deletion, instructions, pause/resume, and a confirmed practice restart. Daily restart must preserve the recorded daily outcome instead of granting another statistical win.

5. Progress: save puzzle ID, guesses, result, and statistics after every accepted guess. Reload resumes the same puzzle; share an original spoiler-free text summary and export/import a validated local save.

## Tech stack
Use TypeScript with a small browser UI and a pure deterministic puzzle engine that accepts an answer and guess. Keep dictionary validation, scoring, date selection, and statistics separate from rendering. Store a versioned local save and handle denied storage without blocking play. Browser answers are inspectable, so describe this as casual local play rather than a tamper-proof competition. Preserve an existing suitable stack.

## Data & behavior
Dictionary {version, allowedWords, answerWords, license}; Puzzle {id, dateKey, mode, answerIndex}; Session {puzzleId, guesses, status, paused}; Statistics {played, wins, distribution, currentStreak, lastCompletedDate}; Settings. Recompute feedback from saved guesses, validate imports, and deduplicate daily completion by puzzle ID.

Acceptance checks and scope:
Test answers with repeated letters, including an exact occurrence plus an extra guessed occurrence; invalid words; the final winning attempt; date rollover; reload mid-puzzle; and a storage failure. Confirm text/shape feedback works without color. Exclude NYT puzzle packs, copied tile layouts, accounts, online leaderboards, and paid puzzle subscriptions.

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