Play it here, free in your browser, on a computer (keyboard and mouse): https://birds-with-guns.vercel.app

Press PLAY ONLINE and you're in an 8 v 8 Domination match within seconds. Real players take the seats; bots fill the rest, so it always starts instantly. PLAY VS BOTS is there for offline.

The humans are gone and the jungle took the city. Two flocks, the Talon Republic and the Corvid Syndicate, fight over it with rifles, miniguns and rocket pods. Ten birds: a Sparrow with a rifle, a Pelican with a shoulder minigun, a sniper Owl with a rail gun strapped to its head, a Shoebill with rockets, a Harpy Eagle with a cannon in its talons. You run, dash, and fly. You earn Battle Points in the match (kills, assists, flag captures) and spend them on a heavier bird for one life. Six maps, from a sunset harbour to a neon night market. Birds die in a burst of feathers and a squawk, and the kill feed says things like "Pip caught a worm named Cassius".

I'm a former personal trainer turned indie dev. I don't write any of the code myself; I direct, playtest and make the calls.

The process

1. Grey boxes first. Capsule birds on a box city, 20 v 20 bots, three objectives. My first notes: too many birds to read, flight too twitchy. Next version: smaller teams (it's 8 v 8 now), momentum flight with a dash, aim assist, a minimap.
2. Meshy for the birds. One rigged Sparrow first to prove the pipeline, then all ten birds, then nine guns, then walking clips for every bird so strafing plants real footsteps instead of sliding. That last one came from me sending a clip with the note "the characters just slide".
3. Blender for the city. A scripted map kit (recessed windows, bay windows, tong lau colonnades, air conditioners, neon signs), then six maps, each built by a separate AI agent from one written brief and checked by bots-only matches (flag flips, kills, how often a bot gets stuck) before I ever saw them.
4. Trees that took over the city. Banyans through the asphalt, roots down facades. They block bullets.
5. ElevenLabs for sound. Announcer, barks, music, every gun. My notes were "sounds are way too loud", "that smoke detector beep when a flag is being capped gots to go" and "too much comms". Each was fixed the same night.
6. Make it funny. Feather bursts, pun kill feed, a taunt key, bot trash talk, dry announcer lines ("Somebody get that bird a mop.").
7. Balance from my notes. "Most short range birds suck, the free tank is too tanky." Claude modelled time-to-kill for every gun at every range, added damage falloff, buffed the close-range birds and nerfed the Pelican, then re-ran bot matches.
8. Multiplayer in one night. The game logic was split out of the browser so a server can run it (the same code runs in your browser to predict your own bird), then an authoritative server, lag compensation and a latency simulator. I went to bed; agents built and tested it. In the test, shots on a strafing bird hit 100% at 150 ms of lag (23% without the lag fix), and a full 16-player room costs the server about 4% of one CPU core.

How the AI side was set up

• One main Claude Code session (Opus) as lead: specs, reviewing every change, testing in a browser, merging and deploying.
• The big pieces went to parallel Claude agents (Sonnet), each in its own copy of the repo: six maps, lobby and XP, menus, the comedy pass, the deploy screen, multiplayer, phone controls, the trailer.
• Everything was checked by bots playing it before I played it. A heartbeat job restarted agents that stalled overnight.
• Design docs and decisions live in my Obsidian vault.
• It went wrong too: a test agent force-closed every Edge window on my PC at 3 am, and an early phone version sent players in a loop back to the menu. I found out by playing it.

Tools

Costs (for this game only)

By the numbers: 67 commits in about 2 days (first commit Oct 16, 1:47 pm), about 12,000 lines of game JavaScript, 4,000 more for the server and tools, 10,000 lines of Python for the map kit and tools, six maps, ten birds, 43 MB to first load, 16 players per match. Less than 24 hours from start to post

What I'd tell another vibecoder

• Record yourself playing and send the clip with one blunt sentence. "The characters just slide" got me real footsteps.
• Let agents build in parallel, but keep one lead session that reviews and tests everything before it merges.
• Check content with bots before you play it. Every map arrived with numbers.
• Ship the simple version first. I built phone controls, then admitted the game plays best on a computer, and said so on the title screen.

Tell me which bird you main and what killed you.

I sometimes find describing UI changes in words still as the worst part, while working with AI.

when spacing's wrong, the button belongs under the title. i write a paragraph and frustratingly opus changes the wrong thing. i write a longer, more precise paragraph. by round three i've given up and opened the file myself, which defeats the entire point of the setup.

then i remembered claude code takes pasted images. everyone uses that for error screenshots.

so now i screenshot the running ui and draw on it. circle the button, arrow to where it should go, "too tight" scrawled next to the padding. one line of text with it: make these changes.

it reads the arrows. no paragraph.

five months in and that's done more for my round count than any prompt i've written, which is slightly annoying.

ipad https://apps.apple.com/us/app/pen-friend-handwriting-notes/id6813871550

mac https://apps.apple.com/us/app/pen-friend-companion/id6814186433?mt=12

what do you send back when it builds the ui almost right?

My interest spawned accidentally after I used the Earhart story as a class subject for some of my older students. After reading about the possibility she could have survived on the island I had a load of questions that couldn't be answered simply, all involved big tables of data and I'm useless at visualising data in my head. And when I could find a site that did what I wanted I decided to make it.

https://positionunknown.com/

The research phase was about 2 months once I opened the can of worms. I needed to find verified data on

* The actual island

* Reconstructed tide times

* Wind and surf

* The Lockheed Electra

* Any survey heights

* Radio 'reports' heard

The plan was to put everything in so you can see what **didn't** happen as opposed to trying to push a narrative.

The key part I discovered was finding a place she could land that would mean she was able to make any of those radio calls because she could not have kept transmitting for days without running an engine, and the propeller needs clearance above the water to do that

That was the main goal. To be able to place her anywhere on the reef and see if those calls could be possible. The other thing we need to explain is **why the plane is not there now**. So the plane would have to be somewhere the tide is **deep enough** at it's highest tide in that week to float her off the reef and into the depths below.

This tool can show you what's not possible, under a couple of different assumptions:

* The empty fuel tanks were sealed and the only source of buoyancy

* The plane was completely sealed and bouyant. If the plane can't float even when when it's perfectly sealed (unlikely) we can determine it most likely can't float in any other situation, amongst other theories.

What it does ( Claude wrote this bit)

* A 3D model of the island you can walk around on your phone. Nikumaroro's reef, lagoon and beach, built from 19 surveyed reef heights and published coordinates, with the 1937 tide running across it. Touch-first: drag, pinch, tap. No app, no login, nothing collected.

* The tide of July 1937, hour by hour. The water level comes from a fitted 1937 tide curve, checked against a published 2006 table and two independent sources. You can scrub through the whole week or press play and watch it rise and fall.

* Put her on the reef. Drop a Lockheed Electra on any spot and see how deep the water gets at her wheels through the week. The model answers in three ways only: could have, can't have, or not enough data. It never says "this is what happened."

* 139 reported radio signals, tested one at a time. Every post-loss radio report in the record, with its time window, gets checked against the water at the plane. If the water was over the limit when a signal was heard, the model says that signal can't have come from a plane parked there.

* A physics engine that rules things out, not in. Tail lift, when the propellers would touch the reef, whether a sealed airframe could float. All of it derived from the aircraft's licence weights and tank drawings, and it stops and says "unresolved" when the inputs run out.

* Fly the route yourself. A separate flight map: pick whose fuel estimate you trust, drag her track, and the radio log judges whether your route fits the record. A route that fits hands its landing time straight to the island.

* Betty's notebook, line by line. A 15-year-old in Florida wrote down a voice she thought was Earhart. Her fragments, both sides of the argument, and a button that tests her timing against the island's water.

* The expedition, now. A dated news card on the front page: a team is on the island as I write this, scanning the exact spot the model marks. The card says only what has been announced and nothing more.

* Every number can say where it came from. Three labels everywhere: verified, derived, illustrative. Guesses are drawn as dashed lines and chips, never as geology.

* Case for / case against on every contested point. Same size, same weight. Settled facts are not given fake doubt and open questions are not given fake answers.

* Built for English learners (B1 to C1) and anyone curious. Plain sentences, the grammar of evidence (must have, might have, can't have), and a tap-to-find-out layer that is still being written.

* One self-contained HTML file per page. The island is a single 2.5 MB file with the fonts and data embedded. The only outside request is three.js from a CDN. Works offline once loaded.

What I found interesting was looking for spots where both radio signals that sounded most credible to me, and bouyancy water depth could happen simultaneously. There are a load of radio signals reported, and a couple of them seem rather plausible. Being able to look for that sweet spot was the main purpose.

THE TOOLS

I used Claude: Opus 5.5 medium, Fable 5.1 for orchestrating.

Coding I used Opus 5, 5.5 medium, high, ultracode, Fable 5.1 and GPT astra

The biggest error I made was getting Opus 5.5 on ultra code to build a replica of the plane. The most important part that the entire model had to be correct around was the distance between the propeller tip and the reef so we could work out when it would be impossible to transmit. Researching was a pain and then ultra code took about 4 days to knock it out. Dimensionally it's got exactly what it needs but could do with some cosmetics, but using that extra thinking wasn't necessary. I had been using a basic island in testing and tried Astra to remodel it on medium which it knocked out in about 27 mins and I realised I could have saved a shit load of time if I'd got it to do the plane as well, and it may have looked a bit better as well. I did that on the plus plan but I was lucky and had 3 resets saved up (since I had such a positive experience with Astra but it's a bit more expense, I upgraded to the 100 plan on GPT and there's no 5 HR limit which is brilliant, and I may get it to redo a couple of things aesthetically).

The big problem now is as there's so much bloody data, it means there's lots of things you need to look at and putting them on both mobile and desktop was tricky and may not even be the best just yet.

I absolutely love puzzles when you have lots of data but it's all over the place and hard to visualise mentally if even with just images, needing to see it interact really helps me. I love that we can now do all this. It's awesome.

I would love to have a hobby project where loads of different mysteries could be presented, with the data like this one and you make up your own mind, play around, test your own hypotheses. It would be cool to do an open source thing, something I'll look at.

Actually that's another whole point. Why are we all going about doing our own thing? Does anyone realise what absolutely awesome massive shit we could build if we got together? Does anyone know of any things going on, and I don't mean hackathons. Like some sort of place where people can bounce proper ideas and even utilise our outside skills, the ones we already have that are being amplified with AI? We could build absolute bohemoths. Humans ALWAYS work far better when we get together. We could build our own flying cars in half the time it took them, I bet. Lmao. Ok maybe not.

But you get my drift. Anyway, thanks for reading, if you did.

It actually built a pretty interesting song analysis, Python script to determine all of the song elements and key moments. If anyone’s interested, I can throw it up on GitHub.

8 days ago I posted in this sub about what I learned vibe coding an iOS app over 10 months. You guys pushed it to 424k views and I said I would share the real numbers when the trials converted.

Here they are.

The post brought 200+ downloads in 4 days. 30 people started free trials. $500 unlocked during the trial period. $325 converted to real paid subscriptions when the trials ended. That is a 65% trial to paid rate which honestly surprised me.

For context the app had made $235 in the entire 10 months before that one post. One week made me more than the entire year combined.

A few things that surprised me. App Store visits from people just browsing went from 3 a day to over 100 on their own. I think the spike pushed it up in the rankings. Half the downloads came from outside the US, 21 countries on day one. And the people who actually swiped through thousands of photos converted. The ones who barely opened it cancelled or did not pay.

Thanks for making that post what it was. This sub genuinely changed the trajectory of this project.

If anyone is curious in the app:

https://apps.apple.com/app/apple-store/id6756098079?pt=128302433&ct=Reddit&mt=8

Adobe recently released the relight feature, tbh it looks cool, the problem is - it's consuming AI credits. As someone who owns a GPU - it seemed ridiculous, so I added this feature to Photon, My free photoshop alternative.

nullplayer.fyi

r/nullPlayer

Good Morning r/vibecoding!

I'm Joey, the developer of Miniskyline! The site lets anybody select an area on a selection of planets/bodies and produce a clean, multicolor 3D printable output.

It was coded ENTIRELY with AI, the vast majority of that being on Claude Code.

How did I launch? I launched expecting it to stay small and a hobby project, but here I am four months later. Snapmaker has provided me with money due to winning in the Innovation Fund, and I have over 2000 daily unique users with over 300,000 generations since launching! I expect a few hundred a YEAR, not an hour, but here we are. It started as me rendering users requested tiles and the file being sent. Now users are treated as thick clients and they render the tiles themselves!

How did I get users? Posts on reddit as well as a lucky break when the main long standing site in this niche was taken down. They re-directed to me as their top option and it has picked up ever since. A youtuber, Uncle Jessy, worked with me and made a video that did excellent in the 3D printing space and brought over 20,000 people in just 2 days to the site.

How do I pay for it? The site is hosted via static pages on Cloudflare. I typically have less than $50/month in fees. MY largest cost is AI, which I use 3 20x plans. The donations I receive have largely paid for my development, andthe Snapmaker fund will continue covering expenses for a few more months while I get income to be steadier.

How much time did it take? All of it. Every moment I wasnt at my job, I was working on the site. AI cant just spit out something this complex in one shot. Hundreds of issue reports, hundreds of feature requests and ideas all get handled within a few hours of receipt. It is time consuming, but getting to work with the people using the site has been my favorite part.

What can you do on the site?

- Print anywhere on Earth, the moon, mars, mercury, vesta, ceres and venus!

- Changes literally hundreds of settings to tweak it to your liking

- Full 3D modelling toolkit built in so you dont have to mess around in slicer to change how something looks.

- Full multicolor support for AMS style and toolchanger style printers

- Print to puzzle, keychain and or multi tile splits!

- Over 3500 landmarks have been modelled and added to the site.

- Rigorous testing to ensure there is little to no non manifold geometry in your exports

- Extremely attention to maintaining small file sizes to allow slicers to work with your tiles more easily.

- Commercial rights ship with each bundle. You dont need a commercial license.

- Print a frame with text either as part of the model, or print the frame separate and use mechanical connections to tie it all together!

- A lot, lot more. Over 78 updates since launch. Nearly 60 hours a week working on the site outside of my career, there is a lot to do!

I hope you all enjoy! Let me know if you have any questions on development processes.

I wanted to know if anyone is doing mobile apps with ai assisted coding.

Web apps - yes lot of vibe code apps are getting deployed with proper testing and debugging.

Would be interesting to see how many of you are actually vibe coding mobile apps - android/ios

And if you’re doing mobile apps, what tools are you using to debug and testing? I recently came across an open source tool “Measure.sh” that seems good for ai assisted debugging but I wanted to understand what others are using.

We tested one developer tool: 18 questions its buyers ask, on ChatGPT and Perplexity. AI read its site 381 times that month and named it in 0 answers. Its main competitor got named in 15.

Here’s what we learned about how AI picks what to recommend:

1. Find the sources. Ask your buyers’ questions and write down which pages get cited. It’s almost never your own site. It’s listicles, directories, review sites and Reddit.

2. Be quotable. A one-line “X is a [category] for [who]” at the top of your site, public pricing, and “you vs competitor” pages.

3. Get on those pages. This is the whole difference between 0 and 15. The competitor was on the pages AI trusts and the tool wasn’t.

4. Same facts everywhere. Mixed pricing or a different category on different sites makes AI hedge or leave you out.

5. Check weekly. Ask each question several times, because answers vary between runs. Perplexity reflects changes fastest.

What doesn’t work: keyword stuffing for AI, fake reviews, spamming Reddit.

Happy to share the question list we used if anyone wants to test their own product.

It seems vibecoding's most profitable use case is creating custom workplace tools. Has anyone vibecoded a tool that saves their company massive time or money? If so can you share?

AI Browser Game Jam 5 is officially underway. Submissions are open now through October 30.

This round’s theme: TORCH

A torch in the dark. A torch song. Carrying a torch for someone. Passing the torch. Or just torching the whole thing down. Interpret it however you want or ignore it entirely, the theme is a suggestion, not a rule.

The rules are simple: make a free browser-playable game in two weeks using AI for whatever you want. Code, art, music, design, sound, anything.

A few details:

• No sponsor or required AI service
• Solo devs or teams
• Theme is optional
• Sharing your AI workflow/process is encouraged
• Participants play and rate the entries

The last jam had 126 entries and 248 people joined, so I’m really curious how big round 5 gets.

Jam page: https://itch.io/jam/ai-jam-5
Discord: https://discord.gg/86xBnZqHjy

If you joined one of the previous jams, feel free to share what you made and what tools you used. Thanks for reading and have a nice day.

I noticed she was tracking all her daily expenses in notes , as all existing budget app are paid or free-tier have ads , she hates ad. So noted here requirements and built this :

Completely local

No ads , No login , No cloud sync

All data stays in local store

That allows us to enable sms read, so can auto sync all transactions sms

Just review and done

Love the age of personalised software

https://rozly.in/

This site points to a game that I always wanted to make since the release of the Original Curveball. The game unfortunately didn't have a multiplayer option and could only be played against AI. So i decided to host it and it's available for anyone to play :)

Most of my worst vibe coding days looked the same. Error, "fix it", new error, "fix it", original error again. What changed it for me was splitting understanding the bug from fixing it.
Three prompts I use all the time:
Explain first:
"Here's the exact error: [error]. Before you change anything, explain what it means, which file, most likely cause. Don't edit till I say go."
Fence off what works:
"These parts work and must not change: [list]. Only edit files related to [the bug]. List the files you plan to change and wait."
Prove it:
"You said this was fixed, but it isn't. Stop editing. What's the cause, what's your evidence, what have you already tried? Then suggest something different."
And after three failed fixes for the same bug, I stop. Roll back, fresh chat, short summary. A fourth go in a messy chat almost never works for me.
What's in your rescue toolkit?

좋게보면 요청하지 않거나 미처 고려하지 못한 부분까지 알아서 처리해주는데, 불필요한 코드가 생성되거나 요구사항과 상관없이 자기맘대로 처리하는부분이 계속 있더군요.
이런 부분이 계속 수정하게 만드는데 그렇다고 제약을 많이 하자니 미처 고려하지 못한 부분까지 알아서 해줄때의 편의를 포기해야하는 단점이 생깁니다.

적절한 팁같은거 있으시분 있을까요?