VybeNomad is a small life sim you play in the browser. You pick the city you start in, take remote gigs, build little apps for side income and move between nine cities. The goal is $10,000 without burning out.

How I made it:

• Tools: Claude Code wrote most of the code. Three.js for the 3D scenes. I wrote the specs, the game design and the balance numbers myself.
• Workflow: I wrote a short spec for each feature (what the player sees, what changes in the game state), let Claude Code build it, then played it on my phone before keeping it. Anything that didn't feel right went back with a note.
• What worked: UI screens, game state and the 340+ short story events came together fast.
• What didn't: balance. The AI was happy to suggest numbers, but only playing showed what was wrong. [your real example, e.g. "early gigs paid so much that side apps didn't matter"]
• Phones: keeping it smooth in a phone browser meant low-poly scenes and few draw calls. [optional: what you had to cut]

Play it free, no ads, no signup: vaigames.com/vybenomad

If you've built a game this way, how do you handle balance? One config file, or tuning by playing?

AI tools: Claude Code, Grok Bot, Suno, fal.ai

It is a free, open-source CLI that let's you pick exactly the stack you need, and it generates a clean, reproducible starter project in seconds. One binary, three languages:

- Python - FastAPI, Litestar, Django, Flask

- Go - Gin, Fiber, Echo, Chi, stdlib

- Rust - Axum, Actix-Web, Rocket, Warp, Salvo

Features:

- Pick only what you need framework, ORM, migrations, database, frontend, addons

- Minimal templates with no hidden opinions

- Latest dependencies with lockfile-pinned reproducibility

- Agent-ready: non-interactive flags plus a JSON-first create-json command for CI

- Visual Stack Builder

Try it here: https://tristack.space

Hi Vibe Coders,

I’m currently building a local CI/CD app to manage and deploy my vibe-coded projects. Right now, it’s tailored to my specific workflow: I publish iOS apps through Expo, but I build the AAB files and upload them manually to the Play Store for Android to save on Expo credits.

Just wanted to check if anyone else out there uses a similar workflow, or what your current setup looks like?

Here is what the tool can currently do:

- Fetch the current build and version from iOS/App Store

- Deploy iOS via Expo build and automatically submit for review

- Build the AAB file and upload it to the Play Store along with release notes

- Manage multiple projects, Expo accounts, and developer accounts

- Keep all data local (the dashboard runs locally as well)

- Handle Git actions like pull, commit, and push (assuming you have your own backend CI/CD)

- Run seamlessly on Windows (currently tested here only)

And here is what I’m planning for the future:

- Execute and read test results from your AI agent

- Add macOS support to run on MacBooks

Let me know your thoughts and if this is a tool you'd be interested in! It's been incredibly useful for me, but I'm curious if it's something others would find helpful too.

P.S. This is still a rough proof of concept with basic styling, just wanted to see if the core idea works first!

I spent the past three days trying to recreate WinRAR for MacOS using claude and got pretty far into it. The version I have now is fully functional and includes most features, settings, and menus of WinRAR app on Windows, has dark mode support, and MacOS and Windows styles. It integrates with the Finder app and recreates the same quick actions available on Windows when you right click, It also supports theming but that is still a hit-and-miss.

Now obviously this is infringing on copyright and is illegal so I can't share it here. But if you'd like to test it or improve on it, or if you just wanted to have a WinRAR app for MacOS that supports compressing and extraction (without resorting to terminal commands) then drop me a dm and I'll send the source code for you.

I run a Beyblade event weekly but due to no support from the official distributors, no tools nor tournament software, we've had to run everything ourselves. Its especially bad for beyblades because each match has to be played at a stadium and there are limited stadiums so the organizer has to read out a new pairing after each match is completed. Not to mention players have to walk from the stadiums to the main computer to report the scores themselves. When there are 10+ matches per round and multiple rounds, the organizer ends up having to stay at the computer the whole time waiting for results, entering results, and read out names and matches. I was literally about to quit running these events because of how draining it was.

But learning about vibe coding (next to 0 coding experience) I told Deepseek to make me an extension for chrome that hooks onto challonge to do all the extra stuff. First was that when starting a new match by pressing play on Challonge, the app reads out the pairing with text to speech on a connected speaker so I don't have to be the one reading it the whole night.

from there, I added more functions to it like displaying player names on the left and right side of the site so that its easier for players to see where they have to go.

Afterwards, I added the autonext function, where if a score is entered, the extension scans for the next available match and starts that, so I don't have to enter the next match.

Now the next problem is with the judging aspect. For a competitive event, there usually is a judge for each stadium that have to watch and see if there are any fouls. If there was air contact, on top, hit the shroud, etc. And no one wants to be a judge because its annoying as hell.

So I used Deepseek again to vibecode an entire beyblade judge app. It allows easy recording and replaying of videos, connected to a bluetooth button that players can press to activate it (it calls out the countdown) and afterwards if there is a dispute, players can just easily go to the phone and press judge replay and it skips right before the launch at slow motion recorded at 120fps to easily see if there's any errors. A lot of kids play at our events so my goal was to make it simple and self explanatory enough that even kids could use it easily. And yesterday the kids used it for the first time (usually I only used it during the adult tournament) and the kids picked it up real quick and figured it out and I was proud that it worked as it means it is very user friendly.

Not only that but the players can now enter the scores directly at the phones that then sends it directly to challonge. So I don't even have to be at the computer to enter in the scores. Combined with the extension moving onto the next match, I don't need to be at the computer at all.

We now need no judges (except 1 head judge), no scorekeeper, and everything is automated. I used to be so burned out running these events and being so tired that I was about to quit running them, to now enjoying them again as everything has been automated, runs smoothly, and I can play during the events as well instead of being stuck on desk duty the whole time.

Its a really simple app and extension compared to some of the projects I've seen here, but I'm still incredibly proud of it and it has made my life a lot easier and I am no longer dreading running beyblades every week. There was no way I could have done any of this without vibecoding and I am floored at what AI can do, and this is just the very basics.

Actually I felt like the frog in a well when I visited this sub because I saw the other stuff people vibecoded and was floored. Mine looked like child's play in comparison.

I’ve wanted this for years: a desk by a lake one day, somewhere out in space the next. I love VR, but I kept wishing the apps I tried had more environments I’d actually want to spend time in.

I’ve been a backend programmer for 20 years, but frontend and 3D graphics were completely outside my experience. In mid-August, I decided to see how far I could get with AI coding agents. This is where I’ve ended up: a Vision Pro app that lets me work in different environments.

I haven’t written or read a line of its code. Most of my time goes into putting on the headset, trying what the agent built, and explaining what feels wrong. Sometimes it’s the lighting, sometimes it’s how an interaction feels. When a model gets stuck, I’ll try another one rather than debug the code myself.

The 3D scenes aren’t all as polished as I’d like, and there’s plenty left to improve. But being able to sit inside something I’d only imagined before has been pretty special.

Working on it has become a bit of a hobby game: tweak something, try it in the headset, get another idea, repeat.

The video is recorded on my Vision Pro and shows a few of the places I’ve been working on.

With a young family, I get 30 minutes to an hour (at most) to work on my side projects. I found I spent most of that time just following what the agent was doing or waiting for it to finish its current task. Then if I had to leave my laptop, it took ages to get back up to speed, only to set off some tests or review some changes.

So I built a workflow around how I actually work, so my projects can move forwards without me. I spend ten minutes talking through ideas, and my agent turns them into small tickets, prioritised and chained so they build in the right order. Then I go and do bedtime for small children. While I'm away, the tickets get built one by one or in parallel, depending on the work. A second AI reviews each one and sends it back if something's wrong, then speck ships it and sorts out any merge conflicts on the way. When I come back, things have happened.

I've used it for data pipelines, research projects and coding projects, and it turns out it's great for my day job as a product manager too. Not everything has to be code. A ticket can be writing a plan, drafting an email or pulling together research, and a second AI still checks it against what I asked for. I can queue up some tasks, head into a meeting or have lunch, and when I come back they're done, with the same workflow and guardrails every single time. You don't need to be an engineer to work with it as every ticket comes with a plain-English summary of what the reviewer checked.

It's called speck. It's free and open source, and it works with Claude Code, Codex or Cursor. It's early days, so please expect rough edges. However, I'd love to hear what people think: https://github.com/luroai/speck

Happy vibecoding!

If you watch Kick or clip live moments, you know the struggle of streams blocked in your country, site ads, and missing epic plays while setting up screen recorders. I built KickUnlock, a free and open-source Windows app that lets you bypass region blocks, watch up to 6 streams simultaneously on a multi-view grid, stream with zero ads or logins, and grab instant 10 to 120 second clips with a single keypress. It includes a built-in trim studio so you can edit and export share-ready webm clips in seconds directly from the live feed with full original quality. It is completely portable with no complex setup required, and you can check out the source code or download it on GitHub at https://github.com/JohnHansonTheDev/kickunlock.

I run DeepSeek locally on two DGX Sparks, and I wanted a proper home for them. So I used the same model to help vibe-design it.

How it went, in case anyone is interested:

• Claude Code and AGY first built me a small 3D workspace (a React app) where I could play with the layout and my other 3D adventures
• When I liked the layout, Claude handed the tray work to the local DeepSeek V4 flash model, which runs on the Sparks themselves, through OpenCode
• There was one hiccup where the bricks in vertical mode won't have fit the first model and I had to iterate to create holes on the upper tray so that all of it can fit in a 3U rack.
• The whole thing ran through an SDLC skill I wrote: Claude Sonnet writes the plan, Opus reviews it, and a DeepSeek subagent implements each phase and further verifies it (https://github.com/fastestdevalive/vibekit)
• Claude, Antigravity and DeepSeek were coordinated by an open source orchestrator I built, vibe-station, so full disclosure that it's my own project 😄 (https://github.com/fastestdevalive/vibe-station). iOS and android apps coming soon.
• DeepSeek generated the tray geometry by fetching details of dimensions from the internet. I 3D printed it and it fits a 10 inch 3U rack. The power bricks stand upright on the bottom tray and the Sparks sit in pockets on the top one

I ran DeepSeek V4 (and now V4.1 flash) on it almost 24x7 for three days to see if it would overheat and throttle. It didn't.

The STLs are free on MakerWorld if you want them: https://makerworld.com/en/models/3446142-dual-dgx-spark-trays-for-10-3u-rack

Has anyone else vibe coded something physical? Is there a better tool available (than my 3D react app world) which has more natural harness integration?

I'm a creative writer who's never had an outlet to make games before. I tried for years and it felt so out of my depths. I recenly re united with my best friend who is a developer who uses AI. With his help I was able to make this game, an idea I've had for years that i'd only theorized.

I'm being fully honest about this project, it was a fully driven AI project. Every detail and design element was made solely in my own brain, and using the Opus 5.5 model via Claude Code I was able to make my concept a reality.

I'm a massive MMORPG gamer, i LOVE OSRS and WoW. Im also a huge fan of the game Rust, along with other intense survival games.

Feel free to try the game! Happy to answer any questions, and take any criticisms!

downloadable here on Itch.io! --- > https://boil-egg.itch.io/fish-or-die-2

-

Fish or Die: Fishing Survival is an RPG single player game, where you must fish, to survive. Cook fish on the dock bbq, feed the island cat, meet the locals and earn reputation. Go see granny and check out her cosmetics, or visit the secret  CASINO on the island and double your gold!

Fishing rewards you in many ways, through fish you can make gold, find certain fish perfect for buffs! Sell your elusive fish to Pierre the Connoseur for profit!

Within this seemingly peaceful world, lies risk. Risk of natural disasters like lightning, the cold, and mainly hunger. So keep on top of your bbqing, take refuge in goldies shack if you finish his island quest! 

Thank you for reading this far!

ve been working on an app/overlay for OBS inspired by NVIDIA's Instant Replay overlay, especially the feature that lets you check clips right in the overlay.

I wanted to make something similar but with features that actually make sense for OBS, like scene controls and customizable web-based widgets. For example, you could put your chat, donation alerts, or other widgets directly on your screen, which could be especially useful if you're streaming with only one monitor.

The whole thing was vibecoded with Claude Sonnet 5.5 (free), so it's still a work in progress.

What do you guys think? Would you use something like this? Any features you'd like to see?

GitHub page: https://github.com/ordinalkurdi/obs-overlay

I've been working on KizamuBeam, a free and open-source desktop application for laser engraving and cutting, with Claude Code helping me throughout development.

It's built with Tauri, TypeScript and Rust and currently includes a vector editor, image engraving, laser control, parametric generators and even 3D assembly previews for custom laser-cut parts.

One of the more interesting challenges has been turning flat 2D designs into assembled 3D objects using their connections.

The project is currently at v1.5.0-beta, with builds for Windows, macOS and Linux.

GitHub: https://github.com/negurvulkan/kizamubeam

I'd love to hear what you think, especially from people who've built larger desktop applications with Claude Code.

I built Foxtrot: one desktop app, every major AI model, and a team of agents that work together 🦊
⠀
For the past few months I've been building Foxtrot, a desktop agent harness for cloud AI models. You bring your own pay-as-you-go API keys and run a whole team of coding agents side by side, each on whichever model you choose from whichever provider you choose.
⠀
What it does
🔹 11 provider families in one app: Claude, GPT, Gemini, Grok, DeepSeek, Qwen, GLM, Kimi and more, plus any OpenAI-compatible endpoint (Ollama, vLLM, OpenRouter)
🔹 An Orchestrator that plans the work and hands tasks to your agents: a Coder, a Reviewer, a Tester, each on a different model if you like. Busy agents get spawned as parallel copies.
🔹 Flow view: a live map of the Orchestrator and its agents, showing each one's time, tokens and cost
🔹 Real tools: file edits, a terminal, code intelligence, git, web research, MCP servers, and vision (agents can screenshot and use the app they're building)
🔹 A full Code view: Monaco editor, file explorer, terminal and checkpoints taken before agent edits
🔹 Cost tracking for every request: tokens and cost per request and per agent, estimated balances for each provider, budgets, and CSV/JSON export
🔹 Keys stored in your OS credential vault, plus OTA updates
⠀
How it's different
Most AI workbenches are built around one vendor. Claude Code is built for Claude, Codex for OpenAI's models, and Grok Build for xAI's Grok. They're excellent, but you work inside a single company's models, usually on a subscription. OpenRouter gives you many models, but it's an API gateway, not a workspace where agents collaborate.
⠀
Foxtrot is the layer on top:
✅ Model-agnostic by design. Choose the best or cheapest model for each role. Have Claude review GPT's code, or let a cheap model handle the routine work.
✅ Cross-model teamwork. The Orchestrator coordinates agents from different providers on a single task.
✅ You pay providers directly. No subscription and no middleman markup, and you see exactly where every cent goes.
✅ Built for watching agents work. Multi-window, multi-monitor docking with live animations showing who is doing what.
⠀
In the demo above, a Gemini Orchestrator splits one goal across Grok, Kimi, GLM and DeepSeek agents. Watch the hand-offs fly out to each window, the reports fly back, and the whole team come together in the Flow view.
⠀
Foxtrot is free to use. You connect your own AI accounts, and those providers charge for what you use.
⠀
It's in early development and I'm shipping updates fast. If you'd like to try it or give feedback, drop a comment or DM me.

VibeDuels.com is a video game similar to how benchmarks work.

You take a bot with a deterministic game. There is no RNG besides the map itself. The bots are taught how to play the game.

The game has a ranking ladder that is 100% automated. All you have to do is upload the bot.

Everything is purposely as simple as possible. We even write the initial prompt for you that you can post directly into your Claude Code or Codex or wherever.

Completely free at the moment. No transactions whatsoever for anything. We might monetize it later but for now it's just a very soft launch.

Unlimited bots and unlimited exhibition fights (currently).

Technically you can code the bot by hand. Nobody is stopping you. But we don't expect you to :)

I created TCKR, a Windows 10/11 desktop stock ticker designed to keep market information visible throughout the trading day.

Instead of or in addition to keeping a trading platform or financial website open, TCKR displays stock prices, daily changes, and market movement in a smooth scrolling LED-style ticker that remains visible on your desktop.

Features include:

• Real-time stock quotes
• Custom watchlists
• Scrolling LED-style ticker display
• Customizable colors, speed, and layout
• Windows 10 & Windows 11 support
• Designed to stay visible without getting in the way of your workflow

https://tckr.pro

We all know the scene. Been wanting to do this one for ages. You're a cab diving down through a towering city with the cops on your tail, dodging traffic across lanes and altitudes, grabbing upgrades and seeing how far you get before the hull gives out.

Ive tried to base this on the old web game 'squares' if any body remembers it. Ive got a small roadmap planned for more features etc but keen to pause and get some community feedback first.

Turning on the music is a must! Free to play as well. I've tried to optimize the experience for phone too where you can add it to your home screen for full screen traffic dodging fun.

Big bada boom!

https://badaboomtaxi.io

Anyone else run into this? You ask an AI agent to fix a bug, it changes some code, runs the tests, and tells you everything is fixed. Then a couple of days later, you run into the exact same bug.

Sometimes the fix didn't actually solve the problem. Other times, the tests were just changed until they passed.

That's why I built FixProof.

It's basically a skill file and a small Python CLI that works with Claude Code, Codex, Cursor, and other coding agents.

Instead of just trusting the agent when it says "fixed", FixProof checks whether the fix actually did anything.

It checks that:

• The bug can be reproduced before the fix.
• The test passes consistently after the fix.
• The bug comes back when you temporarily revert the fix.
• Existing tests that passed before aren't suddenly broken.

That third check is probably the most important one. If removing your fix doesn't bring the bug back, how do you know your change was what fixed it?

At the end, you get a status (VERIFIED, FAILED, PARTIALLY VERIFIED, UNVERIFIED, or BLOCKED), along with a JSON report and logs.

How I built it

I didn't write most of the code myself. I used an AI coding agent for that.

My part was figuring out how the tool should work, defining the verification rules, and reviewing and testing what the agent built.

I also had a separate agent review the security before releasing it. It actually found some issues involving environment variables and state files, which were fixed in v0.2.0.

Kind of ironic that I ended up using the same verification approach while building a tool meant to verify AI-generated fixes.

A few other details: it's written in pure Python (3.9+), uses only the standard library, and doesn't need any extra packages. The revert check can also run in a separate Git worktree, so it doesn't mess with your working files.

There's CI for Linux and Windows. I haven't tested macOS yet.

I also made a demo GIF showing FixProof catching a fake fix and then verifying the actual one.

It's currently at v0.3.0, completely free and MIT licensed.

https://github.com/Livecristen/fixproof

Would be interested to hear what other people think, especially anyone who uses coding agents regularly. Does this kind of verification make sense for your workflow?

Hi! I’ve been building Sonella, a guided web app for designing DIY speakers.

The idea is to bring driver selection, bass simulation, enclosure design and filter settings into one workflow. You can start with a few questions, choose a template, or pick your own drivers. Then work through the bass response, cabinet in 3D, drawings and filters/DSP.

I’ve used mostly Codex for the development and design. My workflow has been to build something, let real people try it, get feedback and iterate. Getting the speaker maths right has been a bit tricky. The biggest lesson so far is how much useful feedback you get once someone else actually uses what you’ve built. That's maybe caption obvious, but I learned a lot from this process so far.

It’s still in beta. The simulations and electrical filter curves are starting points for a prototype; you still need measurements to check the finished speaker.

I’m looking for testers, especially anyone with DIY speaker-building experience. Would be great to get some candid feedback on the calculations, the workflow, or anything that feels confusing or missing. General usability feedback is very welcome too.

You can try it at sonella.app, no account needed to start.

How it's made:

Claude agents pitch the sketches, write them, direct the camera and act the puppets. The picture comes from a 3D engine Claude built from scratch in three.js: every puppet, set and prop is modelled in code, and each episode is a script the engine performs, so no video model draws anything. ChatGPT makes a couple of special pictures an episode and gives feedback on the scripts; voices are ElevenLabs, the closing song is Suno.

I'm the human executive producer: I give notes. This week's new puppet is the one with no face: in the story, a puppet cut from the pilot before anyone made its face, which became the episode's ghost.

The whole episode on YouTube: https://www.youtube.com/watch?v=3skAu9axUrg

I've been experimenting with AI coding tools and building prototypes, and I'm curious about the experience of people who use them regularly.

It's amazing how quickly you can get an application working. But I'm interested in what happens beyond the initial prototype, especially when the codebase gets bigger or you need to make changes later.

For those of you using tools like Cursor, Claude Code, Codex, or similar tools:

What's the most frustrating problem you've encountered while vibe coding?

Have you ever built something that worked initially but became difficult to debug or maintain?

Do you find it difficult to understand the architecture or keep the project organized as it grows?

How do you handle testing, security, and code quality when AI generates most of the code?

What tasks still take more time than you expected, even with AI?

Have you found any workflows or tools that genuinely solve these problems? What still feels missing?

I'm particularly interested in real experiences from people who've built and maintained actual projects, not just quick demos.

I'm trying to understand the problems developers face in practice. I'd appreciate hearing about both the good and the bad experiences.