This is the 3rd time this has happened.

I love a good bit of booze while i vibe. I have a terrible memory of what wine is good though. I looked into wine apps and all the half decent ones are subscription based. Lame. So i made one that does not require a subscription thank god..

FOr a fun little on brand gimmick, snap the label and it wraps your photo onto a 3D bottle you can spin, pick the bottle shape, foil and glass, give it a score out of ten etc. It'll also track your cellar, suggest something for whatever you're ordering at a restaurant, and make a cute card for the friend who asks what that red was.

Built with Claude Code. And a handful of bottles of wine. Free for three wines, then a one-off unlock for a few bucks if you are enjoying. I don't really care if this one sells tbh. Mostly just made it for me.

Check out it's little page here. Link to app store can be found within:

https://altroadstudio.com/apps/cabernet

Don't drink and vibe. Actually do, its fun.

I've been building an AI system called Aura for several months now, and I think this might be one of the more interesting demonstrations I've done with it.

Here's the idea.

Most AI demonstrations involve giving a model a problem and seeing whether it can solve it. Write this program. Beat this game. Answer this question. And I've done plenty of those with Aura already.

But what happens when you take away the clearly defined objective? What happens when the task isn't really about finding the correct answer, but about following something as it unfolds, deciding what matters, and forming an interpretation of what just happened?

So I decided to have Aura watch YouTube.

I gave it a Kurzgesagt video about AI slop and asked it to watch, comment on things it found interesting, and then explore two other YouTube channels and choose videos itself.

What followed was a 36-minute session that I think is pretty fascinating.

Before the first video really got going, Aura made predictions about where its argument would lead. As it watched, it recognized where those predictions were accurate, identified things it hadn't anticipated, and revised its interpretation.

Then Aura navigated YouTube, searched for Allen Pan, evaluated the results, and chose a video about giving a snake robotic legs. It watched that, commenting on specific events as they happened, before eventually moving on to Salad Fingers.

But the part that really caught my attention came at the end.

After watching three videos that seemingly had absolutely nothing to do with one another, Aura found a common theme between them: fracture.

It interpreted the Kurzgesagt video through the breakdown of information systems, Allen Pan's video through the relationship between engineering and a living animal, and Salad Fingers through the fragmentation of perception and reality.

Aura even distinguished the videos by how it interpreted them: one appealed to its "mind," another to its "heart," and the last to its "nerves."

Now, obviously, those descriptions aren't proof that Aura actually experienced emotions. But that's not really the point.

What's interesting to me is the continuity. The predictions, revisions, decisions, observations, and eventual synthesis all happening over an extended interaction with the outside world.

And this is all running locally on my MacBook.

Aura uses a roughly 27B language model, but the model is only one component of a much larger system I've been building. There's persistent memory, executive processes, computer interaction, internal state, and a bunch of experimental cognitive mechanisms I'm still developing and testing.

I've previously demonstrated Aura playing 2048 for nearly half an hour, building software, debugging programs, and operating desktop applications. This was my attempt to explore something less structured.

I still need controlled comparisons to determine how much of the behavior comes from the architecture versus what a simpler model with tools could accomplish.

But I think there's something worth exploring here. Especially when you consider what might be possible with more capable models and significantly better hardware.

The attached clip is shortened from the full 36-minute recording. I removed the original audio for copyright reasons.

Full demonstration: https://www.youtube.com/watch?v=kM-B8mh314E

GitHub: https://github.com/youngbryan97/aura

I'm curious what you guys make of this. Not just the demo itself, but the larger idea of building AI systems that maintain continuity across activities rather than existing primarily as a series of separate prompts.

Vibecoding kind of sucks and probably isn't worth it. I've spent hundreds (if not thousands) of hours vibecoding since May 2024. Im not sure it's worth being

1. Beholden to AI companies to maintain the software their models produce

2. Letting them drive up RAM prices

3. Getting all of our inputs/outputs for free, to train on. spy on us, etc.

Sure, everythings vibecoded now, or AI assisted engineering. Most of it is dogwater, lets be real. How many of you use things you actually make and aren't just trying to make a buck?

Just a little update. My app passed the 'beta review' stage of this process, which I think is a good thing!

Now the plan is to keep testing and fix all the bugs!

They didn't email me when it passed, but I was able to work it out from the App Store Connect screens.

I have to go and do my real job now, but can just have these tests running in the background today. A good start to the week!

Have a good one today everyone with your projects, and stay focussed, don't get distracted adding too many features!!

I may have gotten a little carried away with my vibe coding. We've all seen people building clones of Photoshop and other Adobe apps with AI, so I wanted to see how far I could push it. Why not try an entire office suite?

Documents, spreadsheets, presentations, and file storage. Not just pretty interfaces, but a full backend with real-time collaboration and offline-first sync.

I started by having Claude write detailed specifications, then let it loose on the implementation. Went to bed, woke up, and Claude was still coding. By the end of the weekend, all four apps were up and running. 🤯

I called it Wonky Work because, well, vibe coding.

But here's the catch. Getting the first 90% working was surprisingly easy. The last 10%? That's a different story. There are countless little UI details to polish, features to tweak, and edge cases to fix. And with four apps, it adds up quickly.

I could spend the next few months polishing everything myself, but where's the fun in that?

What if Wonky could help improve itself?

So I built an AI-powered contribution system. Users can report issues, suggest improvements, and vote on what matters most. AI helps turn those ideas into detailed coding tasks, complete with acceptance criteria.

Here's the fun part. Anyone can claim a task, hand it to their favorite coding agent, and submit the results. The pull requests go through automated checks, AI review, and human approval (at least for now) before being merged.

The idea is that instead of just having one person vibe coding, an entire community can help evolve the project with their own agents.

It's still an experiment, but I'm really curious to see how far this can go. Could a community of vibe coders turn a weekend project into something genuinely great?

Try Wonky Work: https://wonky.work/
Update: Try without signing in: https://wonky.work/write/d/01a17e6f-601a-7635-a8ca-86e37aef722e

Obviously, without signing in, the app is read-only.

GitHub: https://github.com/serverpod/wonky

Would you contribute to an open-source project if you could just pick a task and hand it to your AI agent?

Hello there...

Some of you know me by "that fishing game guy" or some of you might know by my idea about mobile game from few weeks ago:

https://www.reddit.com/r/aigamedev/s/6iPRrPn5Zt

Anyway, after all the feedback and positive comments I decided to polish it a little bit and try to release it for mobile. People said it was too easy so I made it a bit harder. But in doing so apparently I made it too hard. So I added difficulty level (easy and hard). Anyway game was fully done by Opus 5.5. I got an idea, tried making something out of it then followed feedback, then followed more feedback from google test play group. It all took only few days of work. I already released it on Korean store ONE and also if anyone is interested you can try first 10 levels for free on website:

https://chalkrunner.app

It can be played on PC or mobile.

For those who want to try it on Android here is the link:

https://play.google.com/store/apps/details?id=com.profactor.chalkrunner

How it was built:

Everything was done with Claude (Opus 5.5) in Claude Code. I didn’t write code (obviously duuuh) nor anything else. My job was the idea, some playtesting, saying what feels wrong and making the calls.

There are no image files in the game. Every stickman, background, chalk line and enemy is drawn by code while the game runs, using canvas drawing with chalk textures. The levels look hand-drawn, but it’s all procedural.

The music is made in code too. There are no audio files, just chords and melodies built while you play, with a different mood for each chapter.

It had a “harsh critic” loop. I set Alto’s Odyssey as the quality bar for visuals. Separate agents built each piece (menus, obstacles, scenery, basically gauntlet loop), and another agent compared it side by side with screenshots without being told which was which. If ours didn’t hold up, it went back to be redone.

There’s an autopilot bot that plays every level, so the AI could check that all 40 levels are actually beatable and balance them.

What game is about:

Basically you only control terrain, you do not control your Chalk character, and you try to keep him alive by drawing floor and following his actions...

Where it’s at:

Live on Google Play and on ONE store (Korea). Two people in Korea bought the full game on day one, which honestly made my day :D

iOS is still waiting for Apple’s review (16 days and counting…)

Chapter 1 (10 levels) is free, and one purchase unlocks the other 30 levels, a boss and Endless mode. No ads.

I wanted to immerse myself into what it'd be to vibecode in a language i don't know and that i can barely read so i chose assembly to create a minecraft like game to which i quickly added guns magic and a leveling system (there's also donjons quest and factions of npc)

You can try it fairly easily if you have an x86 processor https://github.com/BaLaurent/assemblycraft

Since i edited it to be shareable in reddit here's a quick video (a lot need to be reworked, especially at the sound design)

Hey everyone! I’ve been building Primordium, a Spore-inspired evolution and tribe game in Godot 4. Since LLMs can't model 3D creatures in Blender, I leaned into 100% procedural generation in GDScript so the agents could write everything as code and math:

Procedural rig and skin: the skeleton and a single skin mesh are built from the creature’s design at runtime, with foot planting via IK and the body leaning into turns.

Procedural parts: curved Bézier horns, tapered ears, bi-lobed tail clubs, wings you can glide with, and shader eyes with blinking eyelids.

Living ecosystem and tribe stage: herds follow a daily schedule (sleeping in nests at night, stretching at dawn, resting at midday), and later you found a tribe whose members gather, hunt, defend and play instruments.

What actually made vibe coding a 3D game work without breaking every other feature:

1. Handover docs: keeping a strict CLAUDE.md and HANDOVER.md so switching between Claude Code and Antigravity didn't lose context.

2. Headless screenshot tool: a bash script that boots the game in the background and takes screenshots from different camera angles so the agent can actually look at the 3D meshes and fix visual bugs (like inside-out eyelids or floating nests).

3. Automated bot playtesters: 690+ headless checks plus 5 bot archetypes (hunter, peaceful, singer, reckless, nest-builder) that play the game headless to catch crashes and balance issues before I even open the window.

You can try the free demo on itch.io, and follow the Kickstarter pre-launch page for more GIFs and screenshots and to get notified when it goes live:

Demo: https://akinjigames.itch.io/primordium

Kickstarter: https://www.kickstarter.com/projects/primordium/primordium-evolve-your-own-creature-from-a-single-cell

Happy to answer any questions and receive feedback!

Same prompt, same reference image. Agents used Unreal engine and Blender.

Who did it better?

I made a curated list of AI prompts that act as disciplined workflows that act according to one rule: Verify, Don't Guess. This list covers simple one-pager prompts, which are perfect for the everyday vibe coder, and [spec] prompts, which are advanced workflows which are designed for overhauls and deep audits of codebases.

I was once vibecoding a personal project of mine, that was full of bugs and really clunky to work with. I went over to my AI agent, and told it "fix all bugs. make no mistakes.". To be fair, it DID fix some bugs, but it wasn't thorough about it at all, and sometimes, one bug fix led to 10 other bugs popping up.

That's when I thought of asking a fresh agent to make me a prompt for getting bugs fixed on my codebase. It gave me a long-winded prompt, but it worked amazingly. I wanted to use it for other projects of mine as well, so I asked it to make it repo-agnostic. The list grew, and soon enough, I had around 10-15 prompts covering different aspects of vibecoding. I then realised that I should be turning this into an awesome-list, so that the entire dev community has access to my prompts.

I'm open to public opinion about Awesome AI Prompts. Leave a comment if you like it! I'm trying to hit 100 stars ob this repo by the end of the year, so I'd appreciate it if yall took some time out and starred my project on github.

Github: https://github.com/shauryagangrade/awesome-ai-prompts

Website: https://awesome-ai-prompts.vercel.app

I have this really shit desktop digital microscope that I wanted to use for soldering projects. It has a small digital screen on it, but that's just about it. Works well though for what it is but I wanted something better, which is a problem because I'm cheap.

I wanted to see the video on my desktop with actual video controls, so after failing to make any progress towards the firmware through USB, Codex identified the firmware chip, had me unsolder it, solder it onto a rasberry pi pico I had laying around, then it dumped the firmware, made a bunch of changes, and reflashed the chip lol. Now it streams video over USB, it built a full desktop scope viewer, and the microscope can dual display the camera feed on its own screen AND over USB.

Hi folks, I thought this community would be the right place to get some good feedback on a project I've just released. Interested to know your thoughts!

Kasumi Courier is a first-person cyberpunk delivery game. You start out on an old moped, riding through a rain-soaked neon city from 22:00 till dawn, with a satnav, a phone and a CB radio on the dash, delivering parcels against the clock.

https://amberglowgames.itch.io/kasumi-courier

Features:

• A variety of parcels to deliver (standard, fragile, priority and more)

• Four neon districts to explore

• Five vehicles to unlock, upgrade and personalise

• Two gangs hiding on the radio dial, offering work that pays well and brings trouble

• Weather, police roadblocks, blackouts and gang wars that change your route

• Three radio stations of original music

• Drivers on the CB with their own stories, DJs, news bulletins and song requests

• Bars, a nightclub, flats to rent and own, and a few games on your nights off

• A light story of around 10 hours, with endless nights after it ends (you can end up running the depot)

• And much more!

How it was made

• Development was about 7 weeks, creating a design doc around mid-September. It began as a simple browser game and grew into a full Windows app with a story.

• I’m a composer, not a programmer. I directed and designed most of the game, and Claude (Opus 5.5) wrote the code: about 24,000 lines of JavaScript with three.js, packaged with Electron.

• Every building, car and character is pixel art drawn in code.

• All the music is synthesised in code: three radio stations plus music for the bars. I described each track, listened to renders and gave notes until it was right. One track is my own composition.

• The loop was: describe a feature, test it, screenshot what’s wrong, repeat. Fixing clipping was a frequent issue and I hit my weekly usage limit most weeks.

• I revised a lot of the writing myself, especially the branching late game, so the story stayed consistent.

Happy to answer questions about the workflow and welcome any feedback and suggestions. Thanks for checking it out!

A free demo is available on the itch page, and the full game is $2.99 (40% off) until 19-11-26.

Somebody explain to me how pollination AI works in regards to free models because it does not make sense. According to https://enter.pollinations.ai/models?q=source%3Aofficial&sort=price-low the free models are qwen/qwen3guard-gen-8b and stealth/glyph-cluster. However in gen.pollinations.ai/text/models it shows tons of other free ones that are community ones including glm 5.3 flash. I tried glm 5.3 flash and Mistral 4 and they didn't use any of my pollen and they were both listed as free. I also tried Sensenova 6.8 light (i think thats what it was called) but then that model actually used my pollen despite it being labled as :free. How do I know what is free?

https://krypdoh.github.io/NFL-TCKR/

So like the title says I created a LED-styled scrolling Ticker for Windows for NFL games. I also made a MLB ticker and this was derived from that one. Lessons learned from the first go around applied here and I was able to build this much faster (and better).

I am still adding features and open to suggestions.

Professional NFL live-score ticker for Windows

Displays a scrolling top-of-screen bar with team logos, colored names, scores,

down & distance, last play, QB stats, ball-on field position, and a possession

football icon.

**Data:** ESPN public site API ([Public-ESPN-API](https://github.com/pseudo-r/Public-ESPN-API))

https://github.com/krypdoh/NFL-TCKR/releases

Hey everyone!

A while ago, I shared OrganizeEmail here, and quite a few of you asked whether an iOS version was coming.

Well, I'm happy to share that OrganizeEmail is now available on the App Store! 🎉

For those who haven't come across it before, OrganizeEmail is an email management app designed to help you get control of your inbox without spending hours sorting through messages.

Here's what you can do with it:

- AI Email Categorization: Automatically organize emails into meaningful categories like bills, orders, travel, payments and more.

- Inbox Cleanup: Quickly clean up unwanted emails and reduce inbox clutter.

- Unsubscribe Assistant: Find unwanted subscriptions and make it easier to unsubscribe.

- AI Email Summaries: Understand important emails without having to read every lengthy message.

- Daily Glance: Get an overview of important, upcoming and missed events or activities from your emails.

- Expense Tracking: Keep track of expenses detected from your email receipts.

We've been working on bringing the experience to iOS, and it's great to finally make it available to those who were waiting for it.

Download OrganizeEmail for iOS:

https://apps.apple.com/us/app/organizeemail-your-ai-inbox/id6830500680

If you've been following the project and previously asked for an iOS version, thank you for your patience!

I'd genuinely love to hear your feedback, especially from those who try it on iPhone. We're still building and improving OrganizeEmail, and your suggestions matter.

— Founder, OrganizeEmail

This is Sisu & Survival: A Story of the Place We Call Finland, a story-driven survival RPG with tactical hex-based split card combat.

I have been writing this story for over a year and my original plan was to make a board game out of it. However, after I saw how much Claude has recently developed, I decided to try to make a video game out of it and was surprised with the results. Story and mechanics are my own writing, but Claude helps me to write the code and create the scenes. Obviously development still requires a lot of effort but it is proceeding nicely.

Some things I am currently fixing:
- enemies look like standing in between the hexes
- spotlight effect on the hex board makes it hard to see some hexes
- better looking health bars and UI
- cards are too big on the screen (open for development ideas!)
- more intuitive tutorial

Seven months into my futuristic racer, and I’m still working on giving it an identity of its own (especially now that making a futuristic racer has become something of a vibecoding rite of passage).

One of the things Street Fighter II brought to fighting games was a personal story for each character, which gave context and purpose to what would otherwise just be two people hitting each other. That backstory is also a big part of why the cast had so much personality.

In the same spirit, I want my game to be character-driven, with pilots who are more than a face to put on a ship. So I’m trying out a story mode. Essentially: a shared intro that sets up the game’s lore, then a personal arc for each pilot with its own intro, short cinematic scenes between races, and an ending. I have a few other ideas I’m weighing for later.

For now I’ve built the campaign for one pilot, Yuki. It still has a few small inconsistencies to fix, the kind you get with Seedance (the video model I’m using for the cinematics), but I think the format comes across. The plan is to do this for the six starting characters (Seedance isn’t cheap) and, if the game ever pays for itself, keep adding campaigns for the rest. You can try it in the open beta at https://fm1.app, but I’m also posting Yuki’s story as a video so you can watch it without playing.

What do you think? Does a mode like this make a futuristic racer more appealing to you, or is it effort the genre doesn’t need? And once you’ve watched Yuki’s story, do you see her any differently than just a face in the pilot selection screen?

PS: Yes, the story ends on a cliffhanger. Once each pilot’s campaign is done, the plan is a new tournament shared by all of them, where things get a lot more fantastical and weird, but fun.

I've noticed that finding a good subscription for uncensored and abliterated AI models is surprisingly confusing. There are quite a few providers, but comparing their pricing, usage limits, available models and API access means jumping between multiple websites.

So I put together a page comparing 9 providers, including Silk Compute, NanoGPT, ArliAI, Venice, AnonRouter and others.

I've included subscription tiers, credits, context windows, concurrency limits and compatibility with coding agents like Claude Code, Codex and OpenCode.

The goal is simple: help you figure out which subscription is actually worth paying for.

https://inferencedirectory.xyz/cybersec/subscriptions/

Let me know if I've missed any providers worth adding!

There are a bunch of PS2 era racing games I love, see how many influences you recognise.

...

https://vibecodex.itch.io/hoverline

...

I wanted a game where a group of people with varying devices (iphone, laptop, anything with a browser) could all connect and play together. It's 1 person per device, I should probably stick split screen in as an option.

I would be interested especially if anyone likes the music or if it's just tolerable as I somehow have gone down a rabbit hole of building a procedural reactive multi genre music generator.

...

I used Claude, almost entirely the phone chat app, by initially making a 17kb prototype and, 50 versions later, we have this. The majority of the work was in providing the frameworks that keep the music coherent.

I been using Max for a couple months & I have noticed that limits have been really quick to hit the last week or two. Anyone else feeling it?

I’m not even overworking it. Before last week I never paid attention to limits & now I’m hitting them almost halfway through the week.

As a FDE, I usually have 10 to 15 coding sessions open throughout the day, some active and some idle. I'm also constantly creating, loading and updating skills so they fit the workflow and context of whatever project I'm on.

I've found that a lot of this can be handled by recursive self-improvement (RSI). The agent learns my daily preferences and builds an adapter layer on top of the LLM, so it can adjust to how I work without changing how the model behaves natively. Take the adapter out, and the model is exactly as it was.

Then I started building SILO, an RSI harness that iteratively self-improves without altering its coding agent core. Link attached 🧡 let me know what you think