Bancs filmés

Build "Vellum", a vector design editor in the spirit of Figma, in this empty folder. Vite + TypeScript, no framework and no runtime dependencies, drawn in SVG. Tools: select, rectangle, ellipse, line and text; draw by dragging; select, move, resize with handles and rotate; multi-select with a marquee; a layers panel with reorder, hide and lock; an inspector for fill, stroke, corner radius and opacity; smart snapping guides; zoom and pan; undo and redo; export to SVG and PNG. Clean, light design. Keep the scene model and the geometry (hit testing, snapping, transforms) pure and covered by Vitest tests. For automated tests, each tool button carries data-tool="select", "rect", "ellipse", "line" or "text", and the drawing surface has data-testid="stage". Before anything else, put a first screen up on the dev server and open the Live Preview, so I can watch it take shape from the first minute: show something visual right away. Then build it in at least three waves of sub-agents working in parallel: a first wave for the core pieces, a second for the features on top of them, a third for polish, review and tests. Open fresh sub-agents for every wave: when a wave is done and checked, close its windows and open new ones for the next, never reuse a finished one. Mix providers in every wave: give at least one part to a Codex agent and the others to Claude. Wire each part into the page as soon as it lands, check their work in the preview as you go, and finish with `npm run build` and `npm test` passing and the finished app in the preview.

Build "Nightdrive", a pseudo-3D arcade racing game in the spirit of OutRun, in this empty folder. Vite + TypeScript, no framework and no runtime dependencies, drawn on a canvas. A road projected segment by segment with curves and hills, roadside scenery drawn procedurally (palms, signs, lamps), traffic cars to overtake, collisions that slow you down, a speedometer, a lap timer with checkpoints and a best lap kept in localStorage, a sky that turns from sunset to night with a glowing sun and a city skyline, a start screen and a results screen. Synthwave look. Keep the road and projection math pure and covered by Vitest tests. For automated tests, the game canvas has data-testid="game" and the start button data-testid="start", and the arrow keys drive. Before anything else, put a first screen up on the dev server and open the Live Preview, so I can watch it take shape from the first minute: show something visual right away. Then build it in at least three waves of sub-agents working in parallel: a first wave for the core pieces, a second for the features on top of them, a third for polish, review and tests. Open fresh sub-agents for every wave: when a wave is done and checked, close its windows and open new ones for the next, never reuse a finished one. Mix providers in every wave: give at least one part to a Codex agent and the others to Claude. Wire each part into the page as soon as it lands, check their work in the preview as you go, and finish with `npm run build` and `npm test` passing and the finished app in the preview.

Build "Mandel", a fractal explorer, in this empty folder. Vite + TypeScript, no framework and no runtime dependencies, rendered with WebGL shaders. The Mandelbrot set and Julia sets with smooth coloring and five palettes, zoom with the wheel and with a click, pan by dragging, a Julia preview that follows the pointer, a minimap, bookmarks of famous places that the view flies to, an iterations slider, PNG export and a clean dark interface around the view. Keep the palette and coordinate math pure and covered by Vitest tests. For automated tests, the view canvas has data-testid="view", each palette button data-palette="0" to "4" and each bookmark data-bookmark="0" upwards. Before anything else, put a first screen up on the dev server and open the Live Preview, so I can watch it take shape from the first minute: show something visual right away. Then build it in at least three waves of sub-agents working in parallel: a first wave for the core pieces, a second for the features on top of them, a third for polish, review and tests. Open fresh sub-agents for every wave: when a wave is done and checked, close its windows and open new ones for the next, never reuse a finished one. Mix providers in every wave: give at least one part to a Codex agent and the others to Claude. Wire each part into the page as soon as it lands, check their work in the preview as you go, and finish with `npm run build` and `npm test` passing and the finished app in the preview.

Build "Groove", a drum machine and step sequencer, in this empty folder. Vite + TypeScript, no framework and no runtime dependencies: every sound is synthesized with the Web Audio API, no samples. Eight instruments (kick, snare, clap, closed and open hats, two toms, cowbell), a 16-step grid per instrument, tempo and swing, play and stop with a moving playhead, four patterns with copy and paste, per-track volume, mute and solo, a live spectrum analyzer and waveform drawn on a canvas, a few presets, keyboard shortcuts, and everything saved in localStorage. Bold neon design on a dark background. Keep the sequencer timing and the pattern logic pure and covered by Vitest tests. For automated tests, each step button carries data-step="<track>-<step>", both counted from zero (data-step="0-4"), and the play button has data-testid="play". Before anything else, put a first screen up on the dev server and open the Live Preview, so I can watch it take shape from the first minute: show something visual right away. Then build it in at least three waves of sub-agents working in parallel: a first wave for the core pieces, a second for the features on top of them, a third for polish, review and tests. Open fresh sub-agents for every wave: when a wave is done and checked, close its windows and open new ones for the next, never reuse a finished one. Mix providers in every wave: give at least one part to a Codex agent and the others to Claude. Wire each part into the page as soon as it lands, check their work in the preview as you go, and finish with `npm run build` and `npm test` passing and the finished app in the preview.

Build "Grid", a spreadsheet app, in this empty folder. Vite + TypeScript, no framework and no runtime dependencies. A 26-column by 200-row grid that scrolls smoothly (only the visible rows are rendered), a formula bar, editing with Enter, Tab and the arrow keys, formulas with + - * / and parentheses, cell references and ranges, the functions SUM, AVERAGE, MIN, MAX, COUNT, IF and ROUND, dependency tracking with instant recalculation and #CYCLE! and #REF! errors, bold, colors and number formats, copy and paste, undo and redo, CSV import and export, and a chart panel that draws a bar or line chart of the selected range in SVG and updates live. Dark, polished design. Keep the formula parser and the evaluation engine pure and covered by Vitest tests. For automated tests, every cell carries data-cell with its address (data-cell="A1"), the formula bar has data-testid="formula-bar" and the chart panel data-testid="chart". Before anything else, put a first screen up on the dev server and open the Live Preview, so I can watch it take shape from the first minute: show something visual right away. Then build it in at least three waves of sub-agents working in parallel: a first wave for the core pieces, a second for the features on top of them, a third for polish, review and tests. Open fresh sub-agents for every wave: when a wave is done and checked, close its windows and open new ones for the next, never reuse a finished one. Mix providers in every wave: give at least one part to a Codex agent and the others to Claude. Wire each part into the page as soon as it lands, check their work in the preview as you go, and finish with `npm run build` and `npm test` passing and the finished app in the preview.

Build "Gambit", a chess game against the computer, in this empty folder. Vite + TypeScript, no framework and no runtime dependencies. Full legal move generation (castling, en passant, promotion), check, checkmate, stalemate and draw rules, an engine with alpha-beta search and a simple evaluation running in a Web Worker so the board never freezes, click-to-move and drag-and-drop with legal-move hints, smooth piece animations, the move list in algebraic notation, captured pieces, an evaluation bar, undo, new game and three difficulty levels. Elegant dark design. Keep the rules and the engine pure and covered by Vitest tests, including perft counts from the starting position. For automated tests, every square carries data-square with its name (data-square="e2"), and the computer answers within two seconds at the default level. Before anything else, put a first screen up on the dev server and open the Live Preview, so I can watch it take shape from the first minute: show something visual right away. Then build it in at least three waves of sub-agents working in parallel: a first wave for the core pieces, a second for the features on top of them, a third for polish, review and tests. Open fresh sub-agents for every wave: when a wave is done and checked, close its windows and open new ones for the next, never reuse a finished one. Mix providers in every wave: give at least one part to a Codex agent and the others to Claude. Wire each part into the page as soon as it lands, check their work in the preview as you go, and finish with `npm run build` and `npm test` passing and the finished app in the preview.