Build a Three.js Christmas matching game with clear streaks

Three.js Christmas matching game prototype is a focused browser-game prototype that tests tile matching, swap planning, cascade readability, and streak progression. A useful first build keeps one clear objective, a small rule set, readable feedback, and a bounded play session. It is not production-ready without code review, device testing, accessibility work, asset-rights review, and human playtesting.

Start with one playable scene and implement the smallest loop for swapping holiday tiles to create matches, cascades, and streaks. Then add clear input response, state changes, success and failure feedback, and only the progression needed to answer the first design question. Avoid expanding content until players can understand the core interaction without excessive instruction.

Include the player goal, camera, controls, core rules, level layout, feedback, target browser, and success condition. Also define performance limits, failure behavior, accessibility needs, asset direction, and the evidence the prototype should produce. Exact implementation choices still require engineering review in the target Three.js stack.

An early build can test input clarity, visual readability, pacing, difficulty, feedback, and whether the central decision is engaging. Keep the session short and instrument the moments where players hesitate, fail, recover, or discover a strategy. Broad progression, monetization, multiplayer, and content variety should be tested separately.

AI can accelerate visual and interaction exploration, but it cannot prove balance, accessibility, browser performance, stability, or player enjoyment. Creators must inspect generated code and assets, profile real devices, tune values, test edge cases, and run representative playtests. Generated scenes are prototype evidence rather than a claim of production readiness.

Describe the smallest playable scene that can validate tile matching, swap planning, cascade readability, and streak progression. Name the visual style, player actions, rules, hazards, feedback, objective, failure state, target device, and decision you need to validate. Keep the first request narrow so revisions can be traced to the gameplay question under test.