스크린샷
플레이
Create a Breakout / Arkanoid-style brick breaker as ONE self-contained HTML file. Genre: paddle at bottom, bouncing ball, destructible brick grid, lives. Paddle: move horizontally at bottom; keyboard + touch drag. Ball: velocity increases slightly on brick hit; max speed cap. Bricks: grid with HP colors or one-hit; clear all to win. Power-ups (optional): widen paddle, multi-ball, slow ball — drop from bricks. Lose life: ball passes bottom; reset ball on paddle after delay. Win: all bricks destroyed; show score + restart. Levels: one solid layout is enough; optional second row of steel bricks. Collision: reliable paddle/ball/wall/brick reflection (no tunneling). HUD: score, lives, level label. Title + game over overlays; R to restart. Visual: neon or arcade palette; brick particles on break. Mobile: paddle follows touch X. Fair spawn angle from paddle center on serve. 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.
스택
모델DeepSeek V4 Flash
에이전트OpenCode
프롬프트 횟수1
인간 수정0
런타임단일 HTML
투표
챌린지
Breakout프롬프트 포크
이 프롬프트를 자신의 스택으로 실행하고 결과를 제출하세요.