Prompt di Balik Build Opus 5.5 Hari Pertama

Build a complete, playable [GAME TYPE] that runs in a single HTML file in the browser.

Hard rules:
- One file, no build step, no external assets. Generate all art, sound and levels in code.
- Playable end to end on first load: start screen, controls, win and lose states, restart.
- [3-4] levels or worlds, each with its own look and its own difficulty curve.
- Real physics for movement and collisions, a visible score or timer, and a leaderboard kept in local storage.
- Hold 60 frames per second on a laptop. If you must cut detail to hold it, tell me what you cut.

Work through it end to end before you show me anything. Then list what you cut and what you would add next.

Build a complete, playable endless runner that runs in a single HTML file in the browser.

Hard rules:
- One file, no build step, no external assets. Generate the character, props, backgrounds and sound in code.
- Playable end to end on first load: start screen, keyboard and touch controls, game over, restart.
- Four worlds that rotate every 30 seconds, each with its own props, colour palette and obstacle set.
- Real physics for jumping and collisions, a distance score, a combo multiplier, and a top-ten leaderboard in local storage.
- Hold 60 frames per second on a laptop. If you must cut detail to hold it, tell me what you cut.

Work through it end to end before you show me anything. Then list what you cut and what you would add next.

Build a complete, playable kart racer that runs in a single HTML file in the browser.

Hard rules:
- One file, no build step, no external assets. Generate karts, track, scenery and engine sounds in code.
- Playable end to end on first load: track select, countdown, three laps, results screen, restart.
- Three circuits with different layouts and scenery, eight racers with simple AI that overtakes and blocks.
- Real physics: acceleration, drift, collisions with walls and karts. A HUD with lap, position, lap time and a minimap.
- Hold 60 frames per second on a laptop. If you must cut detail to hold it, tell me what you cut.

Work through it end to end before you show me anything. Then list what you cut and what you would add next.

Build a complete, playable souls-like action game that runs in a single HTML file in the browser.

Hard rules:
- One file, no build step, no external assets. Generate the knight, the arena, the boss and all sound in code.
- Playable end to end on first load: title screen, tutorial arena, a bridge boss fight, victory and death screens, restart.
- Stamina-based combat: light attack, heavy attack, dodge roll with invincibility frames, block. Every hit must feel readable.
- A boss with three phases and telegraphed attacks, a health bar for both sides, and a "boss vanquished" moment.
- Hold 60 frames per second on a laptop. If you must cut detail to hold it, tell me what you cut.

Work through it end to end before you show me anything. Then list what you cut and what you would add next.

Build an interactive explainer that teaches [TOPIC] by letting me play with it, not by describing it.

Hard rules:
- One HTML file, runs in the browser, no external assets.
- The main object is a real 3D model I can drag, rotate and adjust with at least one control that changes the physics live.
- Every control explains what changed and why, in plain language, in a side panel.
- It must be correct: [NAME THE RULE OR FORMULA THE SIMULATION MUST OBEY].
- Studio look: dark background, one accent colour, no clutter.

Plan the whole thing first, then build it in one pass. When you finish, list every simplification you made.

Build an interactive explainer that teaches how a camera lens focuses, by letting me play with it, not by describing it.

Hard rules:
- One HTML file, runs in the browser, no external assets.
- The main object is a real 3D lens assembly I can drag and rotate. A focus ring control slides the lens group and moves the plane of focus live, with a small scene (trees, a cabin) going in and out of focus.
- Every control explains what changed and why, in plain language, in a side panel: focal length, aperture, depth of field.
- It must be correct: obey the thin lens equation 1/f = 1/u + 1/v, and depth of field must narrow as the aperture opens.
- Studio look: dark background, one accent colour, no clutter.

Plan the whole thing first, then build it in one pass. When you finish, list every simplification you made.

Build an interactive underwater exploration piece that runs in a single HTML file under 3 MB.

Hard rules:
- One file, no external assets. Water, light shafts, fish, a shipwreck and ambient sound are all generated in code at runtime.
- A diver I can move with keyboard and touch, buoyancy that feels like water, and a simple goal: find the objects listed on screen.
- Light must behave like water: blue attenuation with depth, caustics on the seabed, particles in the beam.
- Runs at 60 frames per second on a laptop; degrade particle count before anything else.

Plan the whole thing first, then build it in one pass. When you finish, list every simplification you made.

Make a [LENGTH] animation about [SUBJECT], drawn entirely in code. No video model, no stock footage, no image files.

Hard rules:
- One HTML file with a canvas. Every frame is painted by the code, frame by frame, at 60 frames per second.
- Style: [hand-drawn brush strokes / flat vector / paper cut-out], one colour palette, no text on screen.
- Storyboard it first as a list of beats with timings. Show me that list, then build.
- Add a record button that exports the canvas to a webm file.

When you finish, list which beats you simplified and why.

Make a 45-second animation about a small red robot discovering light, drawn entirely in code. No video model, no stock footage, no image files.

Hard rules:
- One HTML file with a canvas. Every frame is painted by the code, frame by frame, at 60 frames per second.
- Style: hand-drawn brush strokes with visible texture, warm paper background, a palette of five colours, no text on screen.
- Storyboard it first as a list of beats with timings: the robot alone, the prism, the rainbow, the dark ending. Show me that list, then build.
- Add a record button that exports the canvas to a webm file.

When you finish, list which beats you simplified and why.

Build a working [TOOL] I can use today, not a mockup.

Hard rules:
- [Front end and storage: a single page in the browser with local storage, or a small server only if it truly needs one.]
- The core loop must work end to end: [create -> edit -> preview -> export].
- Include the timeline, the keyboard shortcuts and the export, not just the pretty screen.
- Sound and animation should feel finished, not placeholder.

Build it, then give me a short list of what is missing before it is production-ready.

Build a working keyframe animation editor I can use today, not a mockup.

Hard rules:
- A single page in the browser. Projects are saved to local storage automatically.
- The core loop must work end to end: draw a shape -> add keyframes on a timeline -> scrub and preview -> export to webm and JSON.
- Include the timeline with drag-to-move keyframes, keyboard shortcuts (space to play, arrow keys to step, cmd/ctrl+z to undo), and a sound track lane.
- Sound and animation should feel finished, not placeholder.

Build it, then give me a short list of what is missing before it is production-ready.

You are being compared to another model on the same task, today.

Task: [THE EXACT PROMPT YOU GAVE THE OTHER MODEL]

Rules:
- One shot. No questions back to me, no half-finished code.
- When you finish, list every feature you built that a weaker model would have skipped.