[
  {
    "id": "glass-crane",
    "title": "Glass sphere and origami crane",
    "prompt": "Frontend benchmark. Do not read or write files, use tools, run commands, or inspect the workspace. Answer in one response with exactly one complete standalone HTML document and no Markdown fences or commentary. Create an intricate SVG illustration of a photorealistic 3D glass sphere containing a fully detailed folded origami crane. Use layered realistic gradients, paper facets and crease strokes, drop shadows, realistic glass reflection and refraction cues. Add responsive layout, an accessible SVG title and description, and respect prefers-reduced-motion. No external images, fonts, libraries, scripts, or network access. Include all CSS and SVG inline. Make it a polished original composition. Target 250-450 lines of HTML.",
    "file": "glass-crane.html"
  },
  {
    "id": "procedural-globe",
    "title": "Interactive procedural globe",
    "prompt": "Frontend benchmark. Do not read or write files, use tools, run commands, or inspect the workspace. Answer in one response with exactly one complete standalone HTML document and no Markdown fences or commentary. Build an interactive 3D procedural globe using Three.js imported from https://cdn.jsdelivr.net/npm/three@0.170.0/build/three.module.js in a module script. Generate the continent texture on a canvas, add a translucent atmospheric glow mesh and an orbiting ring of light particles. Implement mouse/touch drag rotation, accessible zoom buttons, responsive resize, and one labeled slider controlling continuous rotation speed. Have an informative loading/error state if WebGL or the CDN fails. Use no external images, fonts, other libraries, or network access beyond that Three.js import. All CSS and application code inline. Make the composition visually polished and respect reduced motion. Target 250-450 lines of HTML.",
    "file": "procedural-globe.html"
  },
  {
    "id": "floating-islands",
    "title": "Floating-island wizard game",
    "prompt": "Frontend benchmark. Do not read or write files, use tools, run commands, or inspect the workspace. Answer in one response with exactly one complete standalone HTML document and no Markdown fences or commentary. Create a playable 3D third-person action-adventure game using Three.js imported from https://cdn.jsdelivr.net/npm/three@0.170.0/build/three.module.js. A low-poly wizard explores a bright pastel floating island archipelago. Implement smooth WASD movement, spacebar jumping, mouse-drag orbit camera, camera follow, platform collision and fall recovery. Connect islands so every crystal is reachable. Collect glowing crystals while dodging automated elemental turrets. Include dynamic day/night lighting, particles, real-time health and score HUD, victory and game-over overlays and a fully working restart button. Add Web Audio jump and collection effects, activated only by user gesture, and pause on loss of focus. Responsive layout with keyboard instructions and a clear WebGL/CDN failure message. No external images, fonts, or libraries besides the pinned Three.js module; all other code and CSS inline. Target a compact but complete game of 350-650 lines.",
    "file": "floating-islands.html"
  },
  {
    "id": "neon-saber-arena",
    "title": "Neon Saber Arena: combat and autonomous play",
    "file": "neon-saber-arena.html",
    "prompt": "Build a Complete 3D Lightsaber Combat Game\nCreate a fully playable, polished 3D browser game called Neon Saber Arena, where the player wields a glowing energy sword and fights waves of enemy robots.\nThis is a coding benchmark. The goal is to create a working game, not just a visual demo. Prioritize smooth gameplay, satisfying combat, intelligent enemy behavior, and an impressive visual experience.\n1. Game World and Graphics\nBuild a real-time 3D sci-fi arena with futuristic architecture, metallic surfaces, glowing lights, and atmospheric effects.\nUse a third-person camera that smoothly follows the player.\nCreate a humanoid player character holding a glowing energy sword.\nGive enemy robots distinct 3D models, movement animations, and combat behaviors.\nInclude glowing sword trails, sparks when weapons collide, impact effects, and destruction animations.\nAdd dynamic lighting, shadows, and an appealing futuristic color scheme.\nMake the environment feel like a finished video game rather than a collection of basic shapes.\n2. Player Controls and Combat\nImplement the following controls:\nWASD: Move\nMouse: Rotate the camera and aim\nLeft Click: Attack with the energy sword\nRight Click: Block incoming attacks\nSpace: Dodge or dash\nShift: Sprint\nR: Restart the game\nCombat must include:\nMultiple sword attack animations and a three-hit combo system.\nEnemies that react visibly when struck.\nHealth and damage mechanics.\nSword collision detection that matches the animations.\nBlocking and dodging mechanics.\nEnemy attack warnings and knockback effects.\nSatisfying visual and sound feedback for every successful hit.\n3. Enemy Robots\nCreate at least three different enemy types:\nScout Robot: Fast-moving enemy with low health that attacks frequently.\nGuardian Robot: Armored enemy with higher health that can block attacks.\nElite Robot: Powerful enemy that can dodge, combo attack, and aggressively chase the player.\nEnemies must actively pursue the player, avoid obstacles, attack when in range, and behave differently depending on their type.\nEnemies should not simply move straight toward the player. They should have believable combat behavior.\n4. Wave-Based Survival\nStart with a small group of robots.\nIncrease difficulty with each completed wave.\nIntroduce stronger enemy types as the game progresses.\nDisplay the current wave, player health, enemies remaining, and total score.\nAward points for destroying robots.\nInclude a game-over screen and restart option.\nCreate a short transition between waves.\n5. AUTOPLAY MODE — MOST IMPORTANT FEATURE\nAdd a large, clearly visible button labeled AUTO PLAY.\nWhen the player clicks it, an AI must take complete control of the player character and play the game autonomously.\nThe autonomous player must:\nFind and approach enemies intelligently.\nChoose which robot to attack.\nPosition itself within sword range.\nAttack using the same combat mechanics available to the human player.\nBlock or dodge incoming attacks.\nRetreat when surrounded or low on health.\nNavigate around obstacles instead of getting stuck.\nContinue fighting through multiple waves without human input.\nReact to changing enemy positions in real time.\nAutoplay must be genuine gameplay AI, not a prerecorded animation, scripted victory, instant enemy deletion, or simulated score increase.\nThe AI-controlled character must visibly move, fight, take damage, and follow the same rules as the human player.\nThe button should change to STOP AUTO PLAY while active. Clicking it must immediately return control to the human player without restarting the game.\nInclude a small status indicator showing the AI's current behavior, such as \"Searching,\" \"Attacking,\" \"Blocking,\" or \"Retreating.\"\n6. Game Polish\nInclude:\nA start menu with a Play button.\nA futuristic HUD.\nSmooth camera movement.\nEnemy health bars.\nAnimated sword glow and light trails.\nRobot destruction effects with sparks and debris.\nSound effects for sword swings, impacts, and robot destruction.\nA pause menu.\nA visible autoplay status.\nSmooth transitions between menus and gameplay.\n7. Technical Requirements\nBuild the game for desktop web browsers using JavaScript and Three.js, or another suitable browser-based 3D engine.\nThe game must be genuinely 3D, not a 2D canvas pretending to be 3D.\nUse procedural geometry or freely available assets where needed.\nAvoid requiring paid assets or external API keys.\nAim for smooth performance at 60 FPS on a typical desktop computer.\nEnsure combat collision, enemy AI, and autoplay are functional.\nProvide the complete runnable implementation and clear instructions for launching it.\nDo not substitute pseudocode, mockups, or placeholder functions for actual gameplay systems.\n8. Success Criteria\nThe benchmark is considered successful when:\nA player can launch the game and immediately enter a functional 3D arena.\nThe player can move, swing the sword, block, dodge, and defeat robots.\nRobots independently move, attack, and react to combat.\nThe game progresses through increasingly difficult waves.\nClicking AUTO PLAY causes the player character to fight autonomously in real time.\nThe autoplay AI can defeat enemies using the same mechanics as the human player.\nThe player can switch between manual and automatic control at any time.\nThe game has functional health, scoring, victory progression, and game-over mechanics.\nThe visuals include animated combat, lighting, particle effects, and a polished interface.\nThe game runs without critical errors.\nFinal instruction: Build the actual working game. Make it visually impressive, fun to watch, and satisfying to play. The most important test is whether the AI can create a believable 3D sword-fighting experience with a genuinely autonomous player mode.\n\nonje sinular html file pelase"
  }
]
