Build your own Solitaire.

# Build an original game inspired by Solitaire

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 Klondike solitaire game called Quiet Deck. Players draw from the stock, arrange descending alternating-color tableau columns, and build suit foundations. Start with one clearly documented draw-one ruleset and unlimited stock passes. Use original or properly licensed cards and a distinct table design; do not copy a commercial collection.

## Design
Use a responsive original card table with seven tableau columns, stock/waste, four foundations, deal number, move count, pause, restart, and undo. Keep card ranks/suits readable without color alone. Provide tap-select/tap-destination and keyboard alternatives to dragging, with an optional reduced-motion deal.

## Features
1. Dealing: shuffle exactly one fifty-two-card deck with a seeded generator and deal the standard seven tableau columns with only top cards face up. Show the seed and distinguish a random deal from a guaranteed-solvable one.

2. Tableau moves: move a valid face-up descending alternating-color sequence onto a compatible card, or a king-led sequence onto an empty column. Turn over an exposed face-down top card as part of the same move.

3. Stock and foundations: draw one card to waste, recycle waste in a documented order, and build each foundation from ace to king in one suit. Validate card ownership and top-card access before every move.

4. Undo and session controls: undo/redo complete moves including flips and stock recycle; pause/resume; restart the same deal; or confirm a new deal. A hint shows a currently legal move without claiming the deal is solvable.

5. Persistence and completion: save card piles, face-up flags, seed, history, move count, and status after every move. Detect completion when all cards are in foundations, resume after reload, and allow validated save export/import.

## Tech stack
Use TypeScript with a pure card/pile rules engine and a browser renderer. Represent each card by a unique immutable ID and route all drag, click, touch, and keyboard actions through the same validation. Store versioned local saves and reject imports with missing or duplicated cards. Keep animation asynchronous but rule transitions atomic; do not accept a second move during an unresolved visual transition.

## Data & behavior
Card {id, suit, rank}; Deal {seed, ruleset}; Run {stock, waste, foundations, tableau, faceUpIds, moveCount, status, paused}; HistoryCommand with before/after pile changes; Settings. Card conservation is an invariant: every card exists in exactly one pile.

Acceptance checks and scope:
Test seeded deal reproduction, invalid mixed-order sequence moves, exposed-card flips, king-only empty columns, foundation suit/rank rules, recycle order, and undo after drawing or recycling. Test small-screen tap controls and corrupted saves. Exclude copied card art, five-game collection parity, solver guarantees, and network competition.

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