Bulaev Built a Florida Man Shooter with 10 Levels in Two Days Using Claude Agents
Bulaev built the browser shooter Florida vs Man in two days. Several Claude agents wrote weapons, levels, and weather in parallel. Two models, Codex and Claude, review every change, and an autopilot plays through the levels and takes screenshots. Claude generates the graphics and sound in code, and there are no asset files. For a small prototype, the scheme works: a human plays and makes requests, and the agents add features and verify them.
AI-processed from TG: @sergiobulaev (Сергей Булаев AI); edited by Hamidun News
Many people put off game ideas for months: you have to write the code, draw the art, record the sound, and test all of it. Sergey Bulaev, author of the channel "Sergey Bulaev AI," showed a different approach. In two days, he and several Claude agents built Florida vs Man, a browser shooter in which a hero in flip-flops fights off Florida wildlife. The game has ten levels based on Florida's geography, and Claude draws and synthesizes all the assets (images, font, sound, and music) in code. There are no ready-made files. Below, we break down how this pipeline works and what can be taken from it.
Where the idea came from and why this name
It all started with frogs. For a week, rain has been falling at the author's house, and small frogs have covered the walls. He and Vova watched his mother try to keep them out of the house, and they came up with a Florida-themed tower defense game. Then they decided to start with a simpler task: a shooter about a hero in flip-flops.
The setting was suggested by the American meme Florida Man, the headlines beginning "Florida man..." that report the strange escapades of the state's residents. On the evening of November 17, Bulaev asked Claude to check whether the name was free. It turned out that the Florida Man mark was already registered for both games and media. That is why the game is called Florida vs Man. The habit is a useful one: the name check took one query, not legal problems after release.
How the pipeline works
Several Claude developers built the game on the author's server. They worked in parallel streams: weapons, ten levels, weather, floods and canals, Easter eggs referencing famous places, and a high score table. It resembles a team where each programmer owns a module, and no one gets in the way of a neighbor.
Quality rests on two layers. The first is cross-checking: two models, Codex and Claude, review every change. If one misses a bug, the other has a chance to catch it. The second layer is the autopilot, which plays through the levels itself and takes screenshots. It replaces manual testing: after a change, the agent launches the game and provides proof that it works.
The most unusual detail is the assets. A game usually needs files with images, fonts, and audio. Here there are none: Claude draws the graphics and synthesizes sound and music with program code. For a small browser project, this is convenient. There is no need to resolve licensing questions about third-party materials, there are no heavy downloads, and any element can be changed by editing text. The cost of this approach is a simple procedural style rather than hand-drawn sprites.
What came out of it and what to take away
Bulaev acted as the product owner and player: he played and wrote down what was missing. First lives, then two flip-flops, then a gun and weather. The agents turned these wishes into code, and the autopilot checked the results. According to the author, the version grew from 0.5 to 0.21 in a day. The post does not explain how the numbering works, so these figures are best read as a sign of rapid pace, not as an exact metric.
The demo has three regions: a backyard, a golf club, and the Everglades. Bosses wait there: a giant iguana, an old alligator, and a gigantic python. Each run ends with a newspaper headline in the spirit of the meme, for example "Alligator on pool float refuses to leave, Florida man swims elsewhere." You can play right away in the browser at floridavsman.app or sign up to be a tester.
There are limitations too. This is the author's own post, not an independent review. Bulaev does not report token or server costs, so how much the two days of agent work cost is unknown. So far, the author himself has mainly assessed the game's balance and quality, and only three regions are available in the demo.
Practical takeaways for developers and product managers:
- Parallel agents work better when tasks are split by stream: weapons separately, levels separately, weather separately.
- Review by two different models and automated runs with screenshots are cheaper than catching bugs by hand after release.
- If assets can be generated in code, the prototype is more compact and changes are cheaper.
- The human role comes down to taste and priorities: they play, say what is wrong, and make the decisions.
An idea that used to be put off for months becomes a playable demo in two days. For prototypes and internal tools, this is a noticeable shift, but large projects will require separate verification of the same scheme.
- Nov 21, 2026A Developer Had Claude Install 900 Apps and Built a Free Mac Cleaner
- Nov 21, 2026Apple Is Building an AI Agent and Making It Harder for Outsiders to Get Access: Permission Now Takes 14 Steps, Not 4
- Nov 21, 2026Qwen3-0.6B Fine-Tuned on a Mac mini: Errors Dropped to 3 out of 30 from 9
- Nov 21, 2026The Programmer Stopped Being an AI Agent Dispatcher: Multica Takes Over the Handoff Routine
Key Questions Answered
Where the idea came from and why this name?
It all started with frogs. For a week, rain has been falling at the author's house, and small frogs have covered the walls. He and Vova watched his mother try to keep them out of the house, and they came up with a Florida-themed tower defense game. Then they decided to start with a simpler task: a shooter about a hero in flip-flops. The setting was suggested by the American meme Florida Man, the headlines beginning "Florida man..." that report the strange escapades of the state's residents.
How the pipeline works?
Several Claude developers built the game on the author's server. They worked in parallel streams: weapons, ten levels, weather, floods and canals, Easter eggs referencing famous places, and a high score table. It resembles a team where each programmer owns a module, and no one gets in the way of a neighbor. Quality rests on two layers. The first is cross-checking: two models, Codex and Claude, review every change. If one misses a bug, the other has a chance to catch it.
What came out of it and what to take away?
Bulaev acted as the product owner and player: he played and wrote down what was missing. First lives, then two flip-flops, then a gun and weather. The agents turned these wishes into code, and the autopilot checked the results. According to the author, the version grew from 0.5 to 0.21 in a day. The post does not explain how the numbering works, so these figures are best read as a sign of rapid pace, not as an exact metric. The demo has three regions: a backyard, a golf club, and the Everglades.
Build & Ship Production AI Agents Without Boilerplate Code
Start your free 72-hour trial at Hamidun Academy (academy.hamidun.com) — interactive lessons on Claude Code & Cursor, live Tech Radar, and production agent templates.
The AI world, distilled — once a week
Seven stories that actually mattered, hand-picked. No noise, no reposts, no press releases.
Done! Check your inbox for a confirmation.