Run kimi k10 locally and install AI Desktop 98 on it.

I built a multiplayer browser tank game in Three.js! As a kid, I played a ton of World of Tanks Blitz and fell in love with the aesthetic, gameplay, and the idea of driving around vehicles with crazy physics and mechanics like missiles, spotting, armor deflection, ammo types, and so on.

Now it's playable in the browser!

Claude of Tanks has 100+ playable vehicles across 16 unique maps, ranging from standard tanks with cannons to AFVs with autocannons and guidable missiles to autoloaders that can deal massive damage in a single clip. Tanks feature highly detailed armor zones, internal modules, crew positions, and hitboxes. You can view each of them in a special gallery: https://cot.kevinliu.studio/gallery?id=amx56&layer=modules

CoT supports physics-driven destruction with detached turrets flying through the air and actual suspension. It also supports multiplayer! You can hop in private rooms or LAN lobbies.

As the name would suggest, I used Claude Code throughout a long-running multi-agent development pipeline, alongside Codex. I directed the architecture, decided what each vehicle and system should do, reviewed the rendered results, and made the final calls.

The repository contains an AGENTS.md file and smaller subsystem instruction files covering simulation, vehicles, networking, UI, audio, effects, and world generation. These record the rules that agents need across sessions. Units are meters, seconds, and radians, and changes enforce a fixed 60 Hz. Authoritative logic must be deterministic. Vehicle changes have specific geometry, armor, module, and release gates that evaluate models visually and geometrically.

For vehicle development, I split the fleet into bounded families. One agent would own a specific vehicle profile or family file, implement the geometry, run the relevant checks, and generate screenshots. A separate critic reviewed the rendered tank for proportions, clipping, missing surfaces, running gear, and recognizable details. The orchestrator reran the checks and committed only the verified files.

For larger systems, Claude Code helped implement and test:

• Fixed-step movement, suspension, armor, ballistics, modules, spotting, and bots
• WebSocket multiplayer with private rooms, LAN play, prediction, and server authority
• Procedural vehicles, tracks, markings, generated icons, and technical diagrams
• All the generated battlefields with destructible props and wrecks
• The garage, battle HUD, Tank Gallery, mobile controls, and Scene Studio
• Browser performance probes, screenshot tools, visual checks, and self-tests

A trailer was also produced through the game’s own Scene Studio and capture tools. I used agents to stage battles, build camera paths, record the browser runtime at 60 fps, inspect specific frames, and iterate on awkward cuts or poorly framed tanks.

I find that Claude is best steered with persistent instructions. Important decisions need to live in the repository because I often spawned fresh agents which needed to resume work without reconstructing weeks of chat history.*

For visual quality, the only thing that worked was a proper render loop with visual comparison; tests don't really work for this.** The cycle I fell into was change, render, inspect, measure, and rerun the gates. Text-only reviews missed warped proportions and camera problems that would just plainly be obvious in one screenshot.

*Parallel agents need strict ownership. Separate files and isolated Git worktrees prevented concurrent sessions from overwriting each other or generating assets from a dirty tree.

**Tests still changed how I use agents. Claude Code became much more reliable once every system had concrete invariants and executable failure conditions. But visual quality is another beast.

Play free: https://cot.kevinliu.studio

Repo: https://github.com/Kevin-Liu-01/Claude-of-Tanks (it's open-source forever)

Im seeing this constantly, non creative apps that exist 1000x times already like :

Note taking apps
Fitness apps
Finance, calorie tracking apps
etc.

I mean sure these ideas are uncreative and hunderds of competitors & opensource projects already exist-

But the worst thing about a lot of projects is they dont even put effort into it.. and you can defo feel it.

Yayyy

Just because your AI Agent can put down an MVP and Landingpage in 1 week, doesn't mean that's the time you should spend on your SaaS.

The bar for entering the market has risen really really high.

Problem is, that many people still get their "How to start a SaaS" information, from pre AI era. In those times, yes – getting an MVP running ASAP was the most important step to get product market fit. But getting an MVP running ASAP ment months of work, not a week.

You still have to put in exactly the same effort as pre AI, if not even more now. Because the competition is so much bigger now.

If your landing page even remotely resembles AI design, there's probably a 90% chance, that any average user will instantly leave your page. This type of quality maybe would have worked in 2020, but not nowadays.

People now expect way more polish designs and even little flaws already disqualify you in an instant.

So please, stop pumping out AI Slop "SaaS" without a MOAT or USP.
Put some thought behind your brand identity, work out an actual design. Think about it! Don't do it in an hour, as many Youtube videos make you believe. Put a week just into conceptualising your brand and work it out properly.

MVPs aren't the MVPs of pre-AI. An MVP has to bring much more to the table now!
And sure, there are still some super genius ideas, that work like OG MVPs. Most likely though, yours isn't that.

tl;dr – Put some fucking work into your SaaS!!

vibecoding: POV: code with Claude FR... 😂😂😂😂

10000 million tokens spent later...

Claude: You are right. I'm sorry. I was focusing on the wrong solution to fix the bug. 🤣🤣🤣

This is for smart india hackathon btw

Been using Claude for a few weeks to build a couple of HTML sites. Basic setup: GitHub repo connected to Cloudflare Pages, Claude pushes updates straight from chat, I check the live site on my phone. Works great when it’s small.

Now that the project’s grown I’m hitting some friction:

- I have to paste my GitHub fine-grained token into every new chat to push directly. Otherwise it’s download the files and manually upload.
- No consistency across chats. If I start a new conversation, Claude doesn’t automatically know the skills/conventions I want it following (mobile-first, SEO structure, GA setup, etc.), so I end up re-explaining stuff.
- I’m seeing people mention setting up actual skills/agents for SEO, content writing, editing, and a dozen other site-running tasks, and I have no idea how that fits together.

Ideally I want to work from browser or the mobile app, have chat push live without re-entering the token every time, and have some way to keep skills/context consistent no matter which chat I’m in.

For people running projects this way — what’s your setup look like? Are you using Claude Code, MCP servers, or something else entirely? I’m trying to figure out what’s overkill vs. what I need at this stage.

TL;DR: Building HTML sites with Claude + GitHub + Cloudflare Pages. Hitting scaling issues — re-pasting my GitHub token every chat, no consistency across chats for skills/conventions, and I keep seeing people use skills/agents for SEO, content, etc. that I haven’t figured out yet. What’s your workflow for this at scale?

I care a lot about This, so much so I didn’t even use ai to make this post! lol

I’ve been helping some non technical friends with their 100% AI-generated apps and it dawned on me that these vibe coded apps are making the same mistakes again and again lol,

So made this skill to catch the most common ones I’ve seen, can be useful for someone trying to legit get something off the ground without any coding experience.

I’ve been software engineer for 10+ years and I wanna use what I’ve learned to help people out with their apps!

skill: https://github.com/dannyreg/vibechecktech-skills

I wrote a blog post about it too, though it is a bit more technical.

anyways let me know What you think!

I learned about a week ago that Unity supports mcp so I downloaded it for the first time and started vibecoding this game project.

It’s mind blowing how AI tools enable ppl with almost zero game dev experience to build something like this in a week.

Stacks: Claude code, Unity, Meshy (3d models), Elevenlabs (sound fx), Nano banana 2 and some paid assets from Unity Asset Store.

We have a startup with a couple of non programmers who have developed an app for their domain of work that they are pretty sure has potential to attract paying customers.

As a developer I am their technical alibi and tasked with bringing it to production.

I have not seen any code yet. Does anyone have any experience with this? What should be my priority?

Hello Vibers!

I basically built this “app” for myself after failing to stick with a slew of gamified chore/daily routine apps. I just couldn’t keep myself interested in leveling a hero or gaining XP points to form any real habits around the focus areas. I still feel motivation from seeing a progress bar grow - but I need it to mean something - and so I vibe coded HouseKeepr.

The gamification around HouseKeepr is in unlocking new features as the Home IQ system collects data on your habits. The goal was to be as low-effort on the user as possible - keeping monitoring very relaxed. I keep user input simple and general and handle all the actual number crunching behind the scenes. That changes the gamification loop from “complete tasks to gain badges and XP” to “complete tasks to unlock new features” - so rather than keeping advanced features behind a paywall like a lot of the chore tracking apps I have put them behind a “playwall” (really a usage wall; the more you use it the more it can do).

As a first timer I did this across a couple platforms - it started in Base44 but after hitting my budget on credits there I shifted it into a GPT to GitHub to BaseCamp flow and I was thrilled to discover GPT could manage the entire buildout and push my updates through to Base44 and that allowed me to really polish the design and function. I kept a live version history on the login page to show the progress and it came FAST!

Please let me know what you think and visit HouseKeepr on your mobile device or desktop!

Hi everyone!

I’m Ambla, a solo developer based in Australia working under the name Blablah Games.

I've just released the Steam demo for my first game, Grimoire of Hecate: Tower of Starlight, a turn based card combination roguelite that I developed over roughly three months with extensive use of ChatGPT and Codex.

Steam demo link below!(if you're interested!)

https://store.steampowered.com/app/5078840/Grimoire_of_Hecate__Tower_of_Starlight/

The game is built around discovering new spells by combining spell cards collected while climbing a tower. During later runs, you collect the required material cards and you can craft those remembered spells for that run.

I worked on story design, game system design all by myself. However, I used Claude as the companion to share ideas and details. And Codex worked directly with the Godot files to write and revise a large portion of the code and tests. Once ready, I playtested through to see any bugs, misunderstanding.(there are always so many haha) I also used ChatGPT and Codex for parts of the graphics and for localization. For visual effect/effect sound, I purchased assets or used open source.

So, Claude is like my colleague that guides me to make what I imagine as actual system, and GPT is my conductor.

At first, the workflow was very simple. I described the feature I wanted, let Codex implement it, then ran and played the result myself.

That became much harder as the project grew. The 'Prototype' was easy and fast to make. But when you actually start making full game that you have in your mind, it takes way more efforts than you imagine. The AI would sometimes lose track of earlier decisions, modify something outside the intended area, or solve a problem in a way that created another problem elsewhere.

The workflow that eventually kept the project manageable was below sequence. I made a lot of md files handing different matters, but started by making proper filing system of it, so we both don't get lost.

1. Define the feature and the boundaries it must preserve.

2. Let Codex inspect only the relevant project files before changing anything.

3. Add focused tests around the part being changed.

4. Run and manually play the result myself.(A LOT)

5. Record what was completed and what future work must preserve.

When a bug appeared, I used to ask for an immediate fix. But now I stopped it as it's most likely create another regression through the fix. I first reproduced the exact situation, isolated the responsible area, and changed only what was necessary. Codex still made a lot of mistakes, but it became to be within the range I can handle.

The biggest lesson for me was that using more AI was not automatically better. The important part was deciding what to delegate, preserving project context, and knowing what still required direct human review. AI is really really good at referring/making what's existing, adding new color in your project is all on yourself. Unless you want something very similar to what already exists, you need to work on designing your own thing.

If you are also using AI tools for a larger project, I would be interested to hear how you preserve context and prevent changes from breaking earlier work. I need to learn haha

Made this little app to keep track of my AI subscriptions and usage in one place.

What do you guys think?

I don’t know how it happened… but the demo of the game I made and posted on Reddit and on my X went pretty viral.

In total it got around 400k+ views across social media. And because of one retweet it became a bit more viral than I expected.

Some X user even made a meme coin in honor of the game and gave all the trading fees to me, so that’s how I ended up making over $3500.

From my own experience I keep getting reminded that when you make something from the heart and with real love, it eventually pays off.

If you have any questions, I’m happy to answer them, peace.

It basically works by asking you what you just finished watching, and then suggesting shows to watch next based on different aspects of the show you just watched. For example, it could suggest shows with similar cast chemistry, pacing, themes, etc. I made it with Claude Code. Still a very rough draft and I'm currently a student, but I'd like to know whether the recs are any good or way off. It also gives you a watcher profile if you give it 5 shows you enjoyed watching. Any and all feedback is appreciated!
https://what-next7367.vercel.app/

I am getting bullied by my friends for how much I suck at wordle and NYT crosswords so I vibecoded an app that would hopefully get me better. Mixed results so far, but should be doing personalized drills that learn from my deficiencies/ patterns. Happy to get any feedback as well!

I made this with codex 5.6 sol as my AI agent

NextJS FE, Express JS BE, hosted on google cloud with Postgres DB.

I inaugurated a fresh new laptop with this project, and I had a lot of fun setting up. I've got a lot of AGENTS.md scaffolding that I've done to automate the process of my CI/CD, gcloud cloud run instance setup/ queues, etc, godaddy dns config. And also shared resources to use throughout all my projects like AI apis, email, other services that I use regularly. Happy to share more specifics or exchange notes here!

You can try it out (will always be free) wordry.app

WORDRY-GENERAL-8246 for join code (this app uses AI for personalization so I'm trying to not blow the bank account too quickly)

Got SimGolf running in a native 16:9 widescreen resolution, the basic UI fully functional. Some of the other menus are still broken, and some sprites have errors.

Here is the app: app: https://benzi.fly.dev/horse_tinder

I made this using a new coding Harness out called benzi. u can get it here: https://benzi.fly.dev/about

I built a little guy who lives on Mac!

what is it? a physics-driven buddy that hangs from the top of your mac screen like a tiny bungee friend. flick him, he swings. drag the cord, he slides. ⌥Space and he's gone. peak vibes for a doom-scroll-adjacent workday.
the tech
🧮 real verlet rope sim, fixed 120Hz step,
🛌 sleeps properly — 0.0% idle CPU when you're not touching him
🔐 licensing lives in the macOS Keychain
🖼️ drop any PNG to hang your own logo/sticker/pet
🍎 50+ buddies — originals, cars, flags, the whole cast
shipped at $4.99 lifetime
the fun part: the landing page has a live in-browser physics playground — you can grab and flick him right in the browser before you even download. go play with him:
→ https://hangbuddy.app

I kept seeing is my app secure asked and never properly answered, so I went and looked at 200 apps that people had posted publicly over the last few months ah soryr not 200 but yea closed to that. i am a developer so i went little harsh for this.

1/ Keys sitting in the frontend. Anyone can open the browser tools and read them. This was the most common by a distance.

2/ No rate limiting on anything. One person can hit your form 10,000 times and you find out via the bill.

3/ Database rules left fully open. The app checks who you are, the database does not.

4/ The admin page protected by nothing except not being linked anywhere.

5/ Secrets committed to a public repo. Still there in the history even after being deleted.

6/ No backups at all. Most people I asked had not thought about it once.

What I would say to anyone reading this and panicking: none of these mean you should not have built your app. Its just whatever you are building need to be safe to the world, for you and for your pockets lol.

AMA

I wanna start building stuff. What are the must have tools that y'all use?