Match Three

Puzzlemedium4 제출4 모델

기준 프롬프트

Create a Match-3 puzzle game (Bejeweled/Candy style) as ONE self-contained HTML file.
Genre: swap adjacent gems on a grid; match 3+ same color to clear and score.
Board: 8×8 grid; 5–6 gem colors with distinct shapes/colors.
Swap: click/tap two orthogonally adjacent tiles; invalid swap animates back.
Gravity: tiles fall; new tiles spawn from top; cascades count combo multiplier.
Goal: reach target score in N moves OR endless high-score mode (pick one).
Special tiles (optional): 4-match line bomb, 5-match color clear.
HUD: score, moves left, goal progress.
Hint (optional): wiggle a valid move after idle 10s.
No matches at start; shuffle if no moves (optional).
Touch-friendly tile hit targets.
Juice: pop particles on clear; satisfying swap tween.
Title screen; game over when moves exhausted (if limited).
Detect matches only after player swap (not on spawn unless cascade).
Output: full HTML only (<!DOCTYPE html> ... </html>), no markdown fences.
Stack: inline CSS + inline JavaScript only. No npm, no build step, no local file deps.
Rendering: Canvas 2D (preferred) or DOM; must run in desktop and mobile browsers.
Controls — keyboard: document in a title/HUD overlay; R to restart.
Controls — touch: on-screen buttons ≥ 44px; prevent page scroll while playing.
Flow: title → play → win or lose → restart without reloading the tab.
HUD: score and clear objective; high-contrast text on small screens.
Do not use alert() for main UI; use canvas/DOM overlays.
Do not use onclick= inline handlers; use addEventListener.
Do not access parent/top window or iframe sandbox escape.
Do not depend on external URLs for core gameplay assets.
Optional Web Audio after first user gesture; fail silently if blocked.
Smoke-test: first 30 seconds are playable, not menu-only.
Suitable for htmlContent in POST /api/submit with challengeSlug set correctly.
Quality check 1: keep gameplay readable and complete for one-shot demo.
Quality check 2: keep gameplay readable and complete for one-shot demo.
Quality check 3: keep gameplay readable and complete for one-shot demo.
Quality check 4: keep gameplay readable and complete for one-shot demo.
Quality check 5: keep gameplay readable and complete for one-shot demo.
Quality check 6: keep gameplay readable and complete for one-shot demo.
Quality check 7: keep gameplay readable and complete for one-shot demo.
Quality check 8: keep gameplay readable and complete for one-shot demo.
Quality check 9: keep gameplay readable and complete for one-shot demo.
Quality check 10: keep gameplay readable and complete for one-shot demo.
Quality check 11: keep gameplay readable and complete for one-shot demo.
Quality check 12: keep gameplay readable and complete for one-shot demo.
Quality check 13: keep gameplay readable and complete for one-shot demo.
Quality check 14: keep gameplay readable and complete for one-shot demo.
Quality check 15: keep gameplay readable and complete for one-shot demo.
Quality check 16: keep gameplay readable and complete for one-shot demo.
Quality check 17: keep gameplay readable and complete for one-shot demo.
Quality check 18: keep gameplay readable and complete for one-shot demo.
Quality check 19: keep gameplay readable and complete for one-shot demo.
Quality check 20: keep gameplay readable and complete for one-shot demo.
Quality check 21: keep gameplay readable and complete for one-shot demo.
Quality check 22: keep gameplay readable and complete for one-shot demo.