Explore

Outputs Tasks Skills

Compare Community Leaderboards

Loading runs…

Account

Loading monthly standings…

Leaderboards

MonthAll categories

ConfigsUsers

Search configs

#	Config	Win rate	Votes	Opponents	Outputs

Win rate

Loading page…

Leaderboards

Configs Users

139 configs · 359 outputs359 unranked · incomplete evidence

Win rate

No rate to plot yetRates appear when public outputs receive valid comparison votes in this month.

Monthly configuration family standings from public Evals comparisons
#
—	DeepSeek V4.1 Flash (1017)	—	—	—

51–100 of 139 configs

Previous Next

Methodology ↗

Loading monthly standings…

Leaderboards

MonthAll categories

ConfigsUsers

Search configs

#	Config	Win rate	Votes	Opponents	Outputs

Win rate

Leaderboards

Configs Users

139 configs · 359 outputs359 unranked · incomplete evidence

Win rate

No rate to plot yetRates appear when public outputs receive valid comparison votes in this month.

Monthly configuration family standings from public Evals comparisons
#
—	DeepSeek V4.1 Flash (1017)	—	—	—

51–100 of 139 configs

Previous Next

Methodology ↗

Build a cozy living aquarium in the browser (single HTML page, no external assets). Original, adorable fish with personalities school, chase each other, nibble plants and sleep at night; bubbles rise, light ripples across the sand, a little treasure chest burps air. Click to drop food and watch them race for it, tap the glass and they scatter, and a Feed, Lights and New Fish button. It should feel calming and alive the moment it loads.

1

—	DeepSeek V4.1 Flash (1017)	—	—	—	6

—	DeepSeek V4.1 Flash (1017)	—	—	—	1

—	DeepSeek V4.1 Flash (1017)	—	—	—	1

—	Gemini 4 Argon	—	—	—	1

—	Gemini 4 Argon	—	—	—	16

—	Gemini 4 Argon	—	—	—	2

—	Gemini 4 Argon	—	—	—	6

—	Gemini 4 Argon	—	—	—	2

—	GLM 5.3	—	—	—	1

—	google/gemini-4-carbon	—	—	—	6

—	google/gemini-4-carbon	—	—	—	1

—	google/gemini-4-hydrogen	—	—	—	2

—	google/gemini-4-hydrogen	—	—	—	1

—	GPT-6 Astra	—	—	—	1

—	GPT-6 Astra	—	—	—	1

—	GPT-6 Astra	—	—	—	7

—	GPT-6 Astra	—	—	—	2

—	GPT-6 Astra	—	—	—	1

—	GPT-6 Astra	—	—	—	1

—	GPT-6 Luna	—	—	—	$Build a spreadsheet app as one self-contained index.html (no external assets, no network). UI: a visible grid with columns A-Z and rows 1-1000, a formula bar, click a cell to edit, Enter commits, arrow keys move. It should look like a tool someone would actually use. Also expose this exact API on window.Sheet. It must stay in sync with the UI: - set(ref, text): enter text into a cell, as if typed. Empty string clears it. - get(ref): the computed value. A number for numeric results (JS number), a string for text and for errors, "" for empty cells. - getRaw(ref): exactly what was entered. - undo(), redo(): cover set, insertRow, deleteRow and fromCSV. A new edit clears the redo history. - insertRow(n), deleteRow(n): 1-based. Rows shift, and formulas are rewritten as Excel does. Both relative and $absolute references move with their cells. A reference to a deleted single cell becomes #REF! in the formula text (for example "=#REF!"). A range that loses a row shrinks. - toCSV(): RFC 4180 raw text (formulas as typed), rectangular up to the last non-empty row and column, rows joined by \n, no trailing newline. - fromCSV(text): replaces the whole sheet, starting at A1. Handles quoted commas, doubled quotes and newlines inside quotes. Formulas start with "=". Case-insensitive, whitespace ignored. - Operators: + - * / ^ & (text concat), postfix %, parentheses. ^ is right-associative. Unary minus binds tighter than ^, as in Excel, so =-2^2 is 4. - References: A1, $A$1, $A1, A$1. Ranges: A1:B3. - Functions: SUM, AVERAGE, MIN, MAX, COUNT, IF(cond, a, b). Conditions use = <> < > <= >=. - Text in double quotes. - Empty cells are 0 in arithmetic and "" in concat. Range functions skip text and empty cells. Numbers concat in plain form (5 & "x" is "5x"). - Errors, exact strings: #DIV/0!, #REF!, #CYCLE!, #NAME? (unknown function), #VALUE! (text in arithmetic). Errors propagate, including through range functions. Every cell in a cycle, and every cell depending on one, shows #CYCLE!. Fixing the cycle recovers them. - Cells recalculate automatically. With 10,000 filled cells and a SUM over them, editing one input must finish recalculating within 1 second. A dependency chain 1000 cells deep must work. A numeric cell typed as 42 or 3.5 is a number. Anything else not starting with "=" is text.$ 1

—	GPT-6.1 Sol	—	—	—	1

—	GPT-6.1 Sol	—	—	—	1

—	GPT-6.1 Sol	—	—	—	1

—	GPT-6.1 Sol	—	—	—	1

—	GPT-6.1 Sol	—	—	—	1

—	GPT-6.1 Sol	—	—	—	1

—	GPT-6.1 Sol	—	—	—	1

—	GPT-6.1 Sol	—	—	—	1

—	GPT-6.1 Sol	—	—	—	1

—	GPT-6.1 Sol	—	—	—	3

—	GPT-6.1 Sol	—	—	—	2

—	GPT-6.1 Sol	—	—	—	2

—	GPT-6.1 Sol	—	—	—	1

—	GPT-6.1 Sol	—	—	—	1

—	GPT-6.1 Sol	—	—	—	1

—	GPT-6.1 Sol	—	—	—	1

—	GPT-6.1 Sol	—	—	—	1

—	GPT-6.1 Sol	—	—	—	1

—	GPT-6.1 Sol	—	—	—	2

—	GPT-6.1 Sol	—	—	—	1

—	GPT-6.1 Sol	—	—	—	1

—	GPT-6.1 Sol	—	—	—	1

—	GPT-6.1 Sol	—	—	—	$Make one UI component in a single web page: a toggle switch that people want to keep clicking forever. The switch is a wide pill. Its track is a window into a tiny living pixel-art world: a lighthouse on a cliff above the sea, a small keeper who walks around, waves rolling in, gulls, drifting clouds. The knob is a glass marble that slides along the track and refracts the scene behind it like a real lens. Off is day, on is night. When it switches, the world changes over about a second with a dithered sunset or sunrise: the sky shifts, the lighthouse lamp turns on and sweeps the sea, the moon and stars come out. The page background changes with it. The click should feel physical: the knob squashes, overshoots and settles, with a soft click made in code. Make all the art in code (canvas or WebGL, no image files, no image or video models). Put everything in one self-contained index.html with no network requests. It has to work with mouse, touch and keyboard (space or enter), and it should look and feel like a finished product, not a demo. Test it in a headless browser, including toggling it several times, before you finish.$ 1

—	GPT-6.1 Sol	—	—	—	1

—	GPT-6.1 Sol	—	—	—	34

—	GPT-6.1 Sol	—	—	—	8

—	GPT-6.1 Sol	—	—	—	2

—	GPT-6.1 Sol	—	—	—	2

—	GPT-6.1 Sol	—	—	—	1

Make a 3D first-person military shooter in one web page: a lone soldier fights through an abandoned dockside refinery at sunset, with cranes, shipping containers, catwalks and long shadows. WASD to move, mouse to aim, click to fire, right-click to aim down sights, R to reload, Shift to sprint. Give the rifle a red-dot sight, recoil, muzzle flash and a reload animation. Enemy soldiers patrol, take cover and shoot back. Add a HUD with health, ammo, a crosshair, hit markers and a kill counter, plus win and game over screens. Make it look as cinematic as you can. It should feel fun the moment it loads.

Build a downhill snowboarding game in the browser (Three.js, single HTML page, no external assets). Carve down an endless procedurally generated mountain with arrow keys, dodge pine trees and rocks, hit ramps for spins and flips with Space, spray powder on every turn, and an avalanche chases you from behind. It should feel fast and fun the moment it loads.

Create a 2D animated scene for the web. It must look exactly like real Japanese anime, as if lifted straight out of a finished theatrical feature film. This is traditional hand-drawn 2D animation, not 3D animation, a moving illustration, or stylized web graphics.

Deliver the final result as a single standalone HTML file. Use any tools, libraries, references or guides you want, literally anything.

Use Studio Ghibli films as the art-style reference for design, linework, painted backgrounds, color and atmosphere. Create an original giant robot as the main character. No humans appear in the scene. Use any tool or technique you like, including 3D, as long as the final result looks 100% like hand-drawn 2D animation.

THE SCENE
At sunrise, mist hangs over an abandoned forest. A giant robot has knelt there so long that moss, wildflowers and old trees have grown on its body. As a small bird lands on its shoulder, the first ray of sunlight touches its weathered face. Deep in its chest, a faint light flickers on. The ground trembles and birds burst from the treetops. With a deep, creaking groan the robot slowly rises, soil, vines and leaves pouring off its armor. It lifts its head toward a gap in the canopy. Its engines ignite and a huge ring of wind spreads across the whole forest. The robot tears up into the golden sky, leaving a curved trail of light and mist, while leaves swirl down through the sunlight.

ANIMATION QUALITY BAR
Every frame should look drawn by a professional anime animator and painted by a master background artist for a finished theatrical film.

Robot: a heavy, ancient, characterful hand-drawn anime mecha with cel-colored forms, chipped paint, rust, moss and believable weathering. Keep it on-model from every angle, and express emotion through posture and glowing eyes.
Linework: confident, delicate hand-inked anime linework with subtle variation in weight and pressure.
Color: traditional anime cel coloring with clean color areas, simple hard-edged shadows and a soft, natural palette.
Backgrounds: richly detailed hand-painted anime backgrounds in a gouache style, with visible brushstrokes, natural color variation, layered foliage and real depth.
Lighting: golden sunrise light, colorful shadows, glowing mist and a soft atmosphere that ties the robot and background together.
Animation: genuine hand-drawn anime timing with real weight: strong key poses, natural holds, and overlapping action in vines, grass, leaves, birds and falling debris. The robot rises slowly so it feels enormous, and launches with explosive force.
Direction: cinematic anime shots, beautiful composition, thoughtful staging, and pacing that starts quiet, builds tension and ends in a swirling climax.

IT MUST NOT LOOK LIKE
- 3D: no plastic materials, CGI shading, visible polygons, game-engine lighting or computer-perfect perspective.
- SVG or vector art: no simple geometric shapes, perfect curves, uniform outlines, flat corporate illustration or basic gradients.
- Web animation: no sliding layers, constant bouncing, floating parts, smooth software easing or puppet-like joint rotation.
- AI art: no warped forms, melted details, flicker or a shifting robot design.
- Non-anime art: no Western cartoon design, realistic rendering, soft painterly shading on the robot, or generic digital illustration.
- Amateur work: no stiff poses, empty backgrounds, repeated trees, muddy colors, clip art, placeholders or unfinished details.

Feel free to change any part of this prompt if it gets a better result.

The result should feel wondrous, nostalgic and full of awe, like an old forgotten dream coming back to life. Before you finish, inspect random frames as still images. If any frame doesn't look exactly like real 2D anime, keep improving it. Don't stop until every frame could pass as a still from a theatrical anime film.

I asked four different AI agent setups the same question about two startups: how did Granola (granola.ai) actually grow, and how did Lovable (lovable.dev) actually grow? Each had to build a dated 24-month marketing history from free public data, show when growth stepped up, and pick three plays to copy and one to skip. Their reports are attached: granola-1 to granola-4 and lovable-1 to lovable-4. I'm not telling you which model wrote which.

Be the judge. For each company, tell me which report a founder should actually act on and why, then rank all four. Say what each one found that the others missed, and where each is thin, unsupported or wrong. Check the evidence: are the numbers sourced, is the chart built from real data, are the dated moves real? Spot-check claims against public sources where you can. Some of the reports followed Corey Haines' reverse-engineer-marketing skill; say whether that made them more useful or just longer.

Deliver one self-contained HTML page: a two-line verdict per company at the top, then the rankings and your notes. Keep it short enough to read in two minutes. Don't stop to ask me questions; make sensible assumptions and say what they are.

I gave four AI agent setups the same AI-looking SaaS dashboard (before.png) and asked each to make it look designed, with its own character, and to make a short before/after video. Their results are attached as unslop-1 to unslop-4: a screenshot and the video for each. I'm not telling you which model made which.

Be the judge. Which redesign would a design-literate founder actually ship, and why? Rank all four. For each, say what works, what still looks AI-generated, and anything broken. Some of them followed Damir Sokolovsky's unslop skill; say whether that made them better or just different.

Deliver one self-contained HTML page: a two-line verdict at the top, then the rankings and short notes. Keep it short enough to read in two minutes. Don't stop to ask me questions; make sensible assumptions and say what they are.

Recreate the Pixar intro as a 3D animation in the browser: the little desk lamp hops in, looks around, squashes the I in PIXAR flat with a few jumps, takes its place and turns its light toward the camera. Match the original's timing, camera move and lighting as closely as you can. Single HTML page that plays the moment it loads and loops.

Make a browser game in one HTML file: a paper airplane gliding through a city at dusk.

The player steers the plane between rooftops, through open windows and under bridges, catching warm lights while the wind pushes back. A run lasts about two minutes and ends on a hill above the city where kites are flying, with a short ending scene and a score. Include a title screen, keyboard and touch controls, and sound made in code. It should feel like a small indie game someone would share, not a tech demo.

3D is welcome. You may use Three.js, but put it inside the file (no CDN links), so it opens offline with no network requests. No images, no other libraries. Write it in one go: don't open it in a browser or test it. Just deliver the file.

Build a cozy rainy-night lo-fi room in the browser (Three.js, single HTML page, no external assets). A tiny isometric bedroom diorama: rain streaks down the window over a glowing city, a cat sleeps on the desk and its tail flicks, steam rises from a mug, a record player spins, desk lamp light flickers, and a lo-fi beat is generated in code. Slowly orbits on its own; drag to look around. It should feel cozy the moment it loads.

Make one web page: a set of 24 animated icons where every icon does what it's for.

Dark background, a 6 x 4 grid of rounded square tiles, one white line icon per tile, all drawn by you in SVG with the same stroke width and corner style so they read as one set. The 24 icons: bell, heart, settings gear, search, paper plane, lock, mail, trash can, clock, hourglass, eye, check circle, cloud with rain, sun, flame, coffee cup, delivery truck, shopping cart, wifi, speaker, download, heartbeat line, magic wand, thumbs up.

On hover each one acts out its meaning in under a second, then settles back: the bell rings, the trash lid opens, the plane takes off, the lock clicks open, the hourglass flips, the truck drives off and comes back, and so on for all 24. Make the motion feel like a well-made product icon set: small, snappy, springy.

So it can be watched without a mouse, when the page opens play a demo that sets off every icon one after another in a wave, then all of them at once, about 20 seconds in all. After that, hover works.

One HTML file that opens offline: no CDN links, no network requests, no image files, no image or video models. Check it in a headless browser before you finish.

Build a small three.js world drawn in coloured pencil on a page of a sketchbook. Nothing is a photograph run through a filter: every surface is shaded the way a hand with a pencil would draw it.

The look:
- Every surface is shaded in strokes of its own coloured pencil. The strokes follow the form of each thing (along its shape, not screen-space hatching) and stay fixed to the surface as the camera moves, so they never swim. Stroke spacing adapts to how big the thing is on screen without sliding as you walk closer.
- Colour is laid in layers on white paper: a warm yellow pencil where the light falls, then the thing's own colour lightly all over, then strokes of that colour pressed harder toward the shade, then a blue-violet shadow pencil across those. The paper's tooth breaks every layer.
- A soft graphite line goes round each thing.
- The drawing fades to bare paper at the edges of the page, like a sketchbook page.
- Shadows still work as normal (a bright morning sun).

The scene: a small harbour town on a bright morning. A wooden pier, a stone quay with bunting strung overhead, a row of tall pastel houses (pink, ochre, blue) with shutters, balconies and flower boxes, a fruit stall, a cat, a red-and-white lighthouse at the far end, a windmill and a green hill with sheep behind the town, water at the harbour. A young sailor (striped shirt, red beret) to walk about in it.

When the page opens, play about 20 seconds by itself: the sailor walks in off the pier, along the quay under the bunting, past the fruit stall and the cat, to the lighthouse, with a third-person camera following. After that the viewer can play: click to look with the mouse, WASD to move, Shift to sprint, Space to jump, mouse wheel to zoom the camera in and out. No sound.

Keep it running smoothly in a normal laptop browser.

Make it one HTML file that opens offline in a browser: no CDN links and no network requests. If you use a library like Three.js, put it inside the file. No image files, no image or video models.

Make one HTML file: a 10-second looping animation of a dinosaur scene.

Long-necked dinosaurs wade across a misty river at sunrise, birds lift off the water, and at the end a T-rex steps out of the jungle and roars.

Draw everything in code (SVG or canvas). No images, no external libraries, no network requests, no image or video models. It should look like the opening shot of a nature documentary, not clip art.

Write it in one go: don't open it in a browser, render it or test it. Just deliver the file.

Here's one picture of a PS5 DualSense controller. Build me a simulator of it I can take apart: it should split open part by part so I can see what's inside and how the sticks, triggers, rumble and battery work. One offline HTML page. Then record a 20-second video of it taking itself apart. Don't stop to ask me questions; make sensible assumptions and say what they are.

Make a small browser game in one web page: a boat ride through 8 dreamlike worlds. The boat drifts forward on its own and the arrow keys steer it; each world has its own sky, water, colors and creatures, and the ride flows from one world into the next. Show which world you are in. No external assets. It should feel beautiful the moment it loads.

Create a cinematic animated rocket launch in the browser, from countdown and engine ignition through liftoff, ascent and stage separation. Include a launchpad, exhaust plume and smoke, camera tracking, altitude/speed indicators and pause/replay controls. Use an original rocket design and clearly simulated telemetry. Deliver a working browser artifact.

Source: https://x.com/bridgebench/status/2103118921024872571 (27K views observed 2026-10-01). Adapted recreation brief based on the public post, not a verbatim original prompt or replication of its model versions. Use the models selected in Evals.

$Build a spreadsheet app as one self-contained index.html (no external assets, no network). UI: a visible grid with columns A-Z and rows 1-1000, a formula bar, click a cell to edit, Enter commits, arrow keys move. It should look like a tool someone would actually use. Also expose this exact API on window.Sheet. It must stay in sync with the UI: - set(ref, text): enter text into a cell, as if typed. Empty string clears it. - get(ref): the computed value. A number for numeric results (JS number), a string for text and for errors, "" for empty cells. - getRaw(ref): exactly what was entered. - undo(), redo(): cover set, insertRow, deleteRow and fromCSV. A new edit clears the redo history. - insertRow(n), deleteRow(n): 1-based. Rows shift, and formulas are rewritten as Excel does. Both relative and $absolute references move with their cells. A reference to a deleted single cell becomes #REF! in the formula text (for example "=#REF!"). A range that loses a row shrinks. - toCSV(): RFC 4180 raw text (formulas as typed), rectangular up to the last non-empty row and column, rows joined by \n, no trailing newline. - fromCSV(text): replaces the whole sheet, starting at A1. Handles quoted commas, doubled quotes and newlines inside quotes. Formulas start with "=". Case-insensitive, whitespace ignored. - Operators: + - * / ^ & (text concat), postfix %, parentheses. ^ is right-associative. Unary minus binds tighter than ^, as in Excel, so =-2^2 is 4. - References: A1, $A$1, $A1, A$1. Ranges: A1:B3. - Functions: SUM, AVERAGE, MIN, MAX, COUNT, IF(cond, a, b). Conditions use = <> < > <= >=. - Text in double quotes. - Empty cells are 0 in arithmetic and "" in concat. Range functions skip text and empty cells. Numbers concat in plain form (5 & "x" is "5x"). - Errors, exact strings: #DIV/0!, #REF!, #CYCLE!, #NAME? (unknown function), #VALUE! (text in arithmetic). Errors propagate, including through range functions. Every cell in a cycle, and every cell depending on one, shows #CYCLE!. Fixing the cycle recovers them. - Cells recalculate automatically. With 10,000 filled cells and a SUM over them, editing one input must finish recalculating within 1 second. A dependency chain 1000 cells deep must work. A numeric cell typed as 42 or 3.5 is a number. Anything else not starting with "=" is text.$

Make a small arcade horde survival game in one web page: an owl monk holding an autumn mountain temple against endless waves of paper lantern ghosts. Arrow keys move, space attacks. All the art must come from the image model selected for this run: sprite sheets for the hero (idle, run, attack, hurt), three enemies and a boss, plus a background. Cut the sheets into frames and animate them in the game. Do not draw characters in code. Add a HUD, a score, and win and game over screens. It should feel fun the moment it loads.

Make a small arcade beat 'em up game in one web page: a punk pigeon fighting through a 1990s shopping mall full of rival seagull gangs. Arrow keys move, space attacks. All the art must come from the image model selected for this run: sprite sheets for the hero (idle, walk, kick, hurt), three enemies and a boss, plus a background. Cut the sheets into frames and animate them in the game. Do not draw characters in code. Add a HUD, a score, and win and game over screens. It should feel fun the moment it loads.

Make an original third-person 3D parkour and puzzle game that runs in the browser with Three.js. The hero is Odile, a young salt miner with a brass lantern on her back, climbing out of a drowned clockwork city. The look is a hand-pulled linocut print: cobalt ink, rust ochre, rough paper grain.

Work in this order and finish each step before starting the next:

1. Generate one 15-second reference video with FLUX 3 Max Video: Odile running, climbing and crossing the city, seen from a third-person camera behind her. This video is the reference for everything: look, world and character.

2. Take screenshots from the video. Rebuild the assets you see in Blender, export them as glTF, and place them in a Three.js scene that matches the screenshots. Use parallel subagents if you can, so some build while others check the result against the screenshots.

3. Take a screenshot of Odile. Make front, back, left and right views of her with GPT Image 2.6 Sunburst. Tripo is not available here, so build her 3D model in Blender from those four views. Rig her, then add idle, run, jump, climb and ledge shimmy animations, and cloth physics on her coat.

4. Play the prototype in a headless browser with real key input. Confirm that running, jumping, climbing and one lever puzzle all work, and fix whatever fails.

Deliver one playable level at index.html with the controls shown on screen. Keep the reference video, screenshots, the four views and the .blend files in the output folder.

Make a small arcade dungeon crawler game in one web page: a mole miner with a glowing pickaxe digging through a crystal cave full of lava beetles. Arrow keys move, space attacks. All the art must come from the image model selected for this run: sprite sheets for the hero (idle, run, swing, hurt), three enemies and a boss, plus a background. Cut the sheets into frames and animate them in the game. Do not draw characters in code. Add a HUD, a score, and win and game over screens. It should feel fun the moment it loads.

Make a small arcade action game in one web page: a fox ronin defending a night market from ink spirits. Arrow keys move, space attacks. All the art must come from the image model selected for this run: sprite sheets for the hero (idle, run, attack, hurt), three enemies and a boss, plus a background. Cut the sheets into frames and animate them in the game. Do not draw characters in code. Add a HUD, a score, and win and game over screens. It should feel fun the moment it loads.

Make a small arcade side-scrolling game in one web page: a jetpack penguin escaping an ice cream factory run by evil robot chefs. Arrow keys fly, space fires. All the art must come from the image model selected for this run: sprite sheets for the hero (idle, fly, fire, hurt), three enemies and a boss, plus a background. Cut the sheets into frames and animate them in the game. Do not draw characters in code. Add a HUD, a score, and win and game over screens. It should feel fun the moment it loads.

Turn one image into a 3D simulator that takes itself apart. First, make one reference image with the image model selected for this run: "A robotic hammerhead shark as a precision machine, studio product shot on a near-white background with a soft floor shadow. White glossy shells with clearcoat, green only on tips, rims, edges and joint rings. Dense dark mechanism showing through cut-outs and clear glass: gears, pistons, hoses, small screws. Eyes as glossy black lenses with a thin green ring. Fins and membranes milky and frosted with thin veins. Front three-quarter view, the whole subject in frame." Then rebuild it in three.js on one web page, entirely in code: no 3D model files, and never use the picture as a texture. Read it and build your own. The look: white shells with clearcoat and an environment map; green as a sparse accent only (tips, rims, edge lines, a bezel, joint rings), never dots over a shell; dark mechanism in 2 levels, big parts (gears, rings, actuators) and about 260 small ones (pistons, hoses, screws, wiring), with windows cut into the shells so the dark mass shows; eyes as glossy black lenses with a thin green bezel; fins milky and frosted with thin veins; near-white studio, soft floor shadow. The order: measure the reference's main proportions as shares of its length before you build. Write a 10 to 12 line checklist of what this picture stands on. Render a still posed like the reference, put the reference and your still side by side, and grade every line yes, partial or no against the picture, not against what you remember building. Count the share of dark pixels (luma under 80) in both bounding boxes; yours has to reach 0.8 of the reference's. Fix and repeat for at least 2 rounds. The page: the shark in the middle, an invented product name and title, one pill button per part (the eye, the hammer, the flank, the jaw, the pectoral fin) that takes that part apart, and live cards that move with the parts. On load it plays a film of about 21 seconds and loops: frame 0 is the front 3/4 hero view with the shark big and already swimming; every 2 to 3 seconds a part opens in about 1 s, holds with its parts still spinning and closes in 0.5 s, each with its own camera side, height and distance, pushing in on that part; then a full explode on a 330 degree turntable, a fast reassembly while it turns, and an exit. Smooth camera paths only. Save the reference, your stills and the grades next to the page. It should look like a product film the moment it loads.

Make a 30-second paper cut-out animation that plays by itself in one web page: a little fox mail carrier cycles through a paper village at dusk, climbs a hill and hands a letter to the moon. All the art must come from the image model selected for this run: the fox and the bicycle as separate cut-out parts (head, body, arms, legs, wheels), plus houses, hills, trees, clouds and the moon as separate layers. Animate the cut-out parts like a paper puppet, with layered parallax and a slow camera pan. Do not draw characters or scenery in code. It should look handmade and charming the moment it loads, and loop.

Make a 15-second anime scene that plays by itself and loops in one web page, like a shot from a hand-drawn summer anime film: a high-school girl rides her bicycle along a seaside road while an old orange-and-cream train passes behind her, and the wind lifts her straw hat off so she reaches back for it. All the art must come from the image model selected for this run: the sky and clouds, the far hills and sea, the train, the girl, her bicycle and its wheels, and the hat as separate cut-out layers. Animate them in the page: layered parallax, the train and bicycle wheels turning, her hair and skirt moving in the wind, the hat tumbling away, clouds drifting. Do not draw characters, the train or scenery in code. It should feel alive the moment it loads.

Make a small arcade platformer game in one web page: a raccoon courier leaping across rainy neon rooftops, dodging security drones. Arrow keys move and jump, space attacks. All the art must come from the image model selected for this run: sprite sheets for the hero (idle, run, jump, attack), three enemies and a boss, plus a background. Cut the sheets into frames and animate them in the game. Do not draw characters in code. Add a HUD, a score, and win and game over screens. It should feel fun the moment it loads. · 4

Make a small arcade one-on-one fighting game in one web page: a crab wrestler taking on rival sea creatures in a harbour ring at night. Arrow keys move, space attacks. All the art must come from the image model selected for this run: sprite sheets for the hero (idle, walk, punch, hurt), three enemies and a boss, plus a background. Cut the sheets into frames and animate them in the game. Do not draw characters in code. Add a HUD, a score, and win and game over screens. It should feel fun the moment it loads.

Make a small arcade action game in one web page: a tiny ghost librarian defending a haunted library from flying cursed books. Arrow keys move, space attacks. All the art must come from the image model selected for this run: sprite sheets for the hero (idle, float, cast, hurt), three enemies and a boss, plus a background. Cut the sheets into frames and animate them in the game. Do not draw characters in code. Add a HUD, a score, and win and game over screens. It should feel fun the moment it loads.

Make a small arcade top-down racing game in one web page: a rubber duck captain racing bathtubs through a giant flooded house. Arrow keys steer, space boosts. All the art must come from the image model selected for this run: sprite sheets for the hero (idle, turn left, turn right, boost), three enemies and a boss, plus a background. Cut the sheets into frames and animate them in the game. Do not draw characters in code. Add a HUD, a score, and win and game over screens. It should feel fun the moment it loads.

Use Blender to build a small game-ready level and prove it works in an engine: a low-poly harbor at dusk with a wooden pier, a crate kit in three sizes on a 0.5 m grid, barrels, two lamp posts with warm glowing lights, and a small rowboat. Work in meters, keep names clean (no Cube.001), put the origins of floor props at bottom center, apply transforms, and stay under 25k triangles. Export it as one GLB. Then make a web page that loads that GLB in three.js as a walkable level: WASD and the mouse to walk around, water moving around the pier, the boat bobbing. Show the triangle count of the loaded file on screen. It should look good the moment it loads.

Build a small 3D game level with real Blender doing the 3D work: write Python scripts, run Blender headless, export GLB, then make it playable in three.js on one web page. The game is Small Hours: at 3:07 a.m. a kitchen-table inventor shrinks herself to 4 cm with her own ray, so the kitchen is 40x real size (she is 1.65 m tall, the counter top is at 36 m). In Blender, build by script at 40x: the counter with a sink, a chrome toaster, sugar cubes, a wooden spoon, a mug on its side, a window with moonlight and an open fridge glowing warm. Model the heroine and a house cat (about 18 m long) as low-poly characters, rig them and animate them in code (hero: idle, run, jump; cat: walk and pounce). Export one GLB under 60k triangles. In three.js: third-person WASD, Space to jump, mouse to aim. Left click grows and right click shrinks the object under the crosshair, so sugar cubes become steps and the spoon becomes a bridge over the sink. Each shot costs 25 charge and the ray recharges only in light (moonlight, fridge glow). The cat wanders and chases her when she gets close. Show a HUD with charge and the triangle count of the loaded GLB. It should feel magical the moment it loads.

$Make one UI component in a single web page: a toggle switch that people want to keep clicking forever. The switch is a wide pill. Its track is a window into a tiny living pixel-art world: a lighthouse on a cliff above the sea, a small keeper who walks around, waves rolling in, gulls, drifting clouds. The knob is a glass marble that slides along the track and refracts the scene behind it like a real lens. Off is day, on is night. When it switches, the world changes over about a second with a dithered sunset or sunrise: the sky shifts, the lighthouse lamp turns on and sweeps the sea, the moon and stars come out. The page background changes with it. The click should feel physical: the knob squashes, overshoots and settles, with a soft click made in code. Make all the art in code (canvas or WebGL, no image files, no image or video models). Put everything in one self-contained index.html with no network requests. It has to work with mouse, touch and keyboard (space or enter), and it should look and feel like a finished product, not a demo. Test it in a headless browser, including toggling it several times, before you finish.$