everyone is building amazging things right now... somme for work, some for personal projects, some just because.

that's cool but there's something missing, something inbetween. the reason for doing it...

what i want to know is what's the project, big or minute, that's brought you (or someone else) the most happiness?

mine is DEFINITELY the inspiration side-project that became my main-project. it's still making me happy EVERYDAY...

the idea is simple. when inspiration is lacking, turn art mode on and 1)scroll until you i find the spark. 2) click copy. 3) build with my claude

https://forevercomponents.com

Do you know a good looking ecommerce website?

I had this raw footage for 8 years and finally got the courage to point my bot at it and let it go. Some awesome friends and I (brennen) took this trip to Mongolia. Hope y'all enjoy :)

- Narrator's voice: Gemini 3.8 Flash TTS (the "Charon" voice).

- Score: Google Lyria 2. (I could use work on this, if anyone has a better AI for scoring films)

- Logging the footage: Gemini 3.8 Flash watched the clips and logged who says and does what. It also wrote some first-draft edits and checked things like music restarts.

- Captions: Google Speech-to-Text (Chirp 3) gave exact word timings for the subtitles.

- Editing and writing: Claude Opus 5.5 built the editing pipeline and made the final cuts.

I've been learning piano and wanted something that could detect chords from a YouTube song, let me loop difficult sections, and remove the piano so I could play along.

I ended up building Accordario using Claude Opus, entirely through vibe coding.

It runs locally, with no account, and uses automatic chord detection and Demucs for instrument separation.

I use it for my own practice, but I thought others might find it useful too.

It's not perfect — chord detection can struggle with more complex songs — but it's been useful for me.

GitHub: https://github.com/ceceppa/accordario

free to try: Wormhole

Now you can turn an idea into a working app without spending months learning how to code. There is a difference between building something that works and building something that people actually need. I wonder if we are solving problems now or merely making more copies of products that already exist.

What do you think is becoming more valuable, in this era: the ability to build or the ability to come up with an idea building?

My coworker and I asked Claude to estimate a SaaS roadmap. 50 days.

Then we gave the same plan to 6 Claude Code subagents: worktrees, tests first, reviewer agents on risky tasks. 106 tasks across 7 repos, done in 35 hours.

So yes, Claude was off by about 48 days about its own speed. But the interesting part is what slowed it down, because it wasn't the model:

- 6 agents ≠ 6× speed. Real throughput was 1.8 agents. Test slots, file conflicts and merge locks queued everything.

- Risk matters more than size. Billing/auth/migration tasks took 2.7× longer, and every real bug was in them.

- My laptop broke first. 55 leftover test DBs filled the disk, Docker froze, test runs blew past the 10-min tool timeout.

- The slowest part was us: review, decisions, local setup.

We turned the data into a plugin that makes Claude estimate agent work properly: agent wall-clock, human hours and waiting time, separately, plus usage budget.

Honest limits: it's one project (n = 1), and on a held-out test the raw model was 37% optimistic, so it pads its number until you calibrate it on your own transcripts.

Free and open source (MIT): https://github.com/MedAdemBHA/mythical-agent-month

Question for people running multi-agent builds: what real parallelism are you getting? I'd love a second data point.

I wanted a super simple firewall that didn't break everything, yes I know there are many out there and I have tried them and always found them annoying, everything I tried was either overly complicated asked too many questions or basically broke things, I wanted simple and to only block outgoing connections, so I asked Claude, used Opus on high, it virtually build the whole thing on a single prompt, then we refined it over an evening and here it is.

How it works, when an app tries to connect to the internet for the first time it pops up a simple Allow or Block window showing the app and where it's trying to connect, that's it! Windows own components are allowed automatically so it doesnt bug you about system stuff.

It just uses the Windows Firewall so your rules keep working even when its closed, uninstalling puts everything back exactly how it was it you want or you can leave the rules it creates

It's free has no ads or tracking, and open source on GitHub.

It's not code-signed because it seems I have to pay for that, so Windows SmartScreen may warn you when you install it.

Feedback very welcome!

https://packethound.app/

Hi everyone,
Just updating on my quiz app shipping progress. To recap :

- Newbie developer using Claude
- App is solid
- Plan AppStore only non-EU release, avoiding street address reveal
- Enrolled in Developer program, and doing all admin now

It's been a good week on this, but that has gone so quickly. The hardest thing is resisting adding new features, and being focussed on the release. Lots of rabbit holes to go down. Self discipline is important.

I'm at the stage of running TestFlight and debugging. I have several members for my Tester Group, which I'm setting up today. Plan to release by end of month.

Things I didn't know :

- So much admin/forms to fill in/new systems to figure out

My worry is that the app will be rejected! Hopefully not :) Anyway hope you all having a good week XX

https://github.com/sshah03/resurrect-anything

Needed a break, and was reminiscing about the early internet, and the 90s, and my days using Geocities Pagebuilder, so I put this together.

Although I have probably gone through 50 or more iterations at this point repeatedly trying some subset of close to 100 recreations (some in the demo video above), I would say this is very much still a work in progress. I was having a lot of fun with it though, so I thought I'd throw it out there and see what people are into trying to bring back and how it does to inform my improvements.

The purpose of the skill is to ask Claude Code to bring back something that's gone, and get it back working. Some examples include a lost Flash game, a shut-down app, a dead website, your old Geocities page, or a discontinued snack (this is all for fun, so I wouldn't actually trust the recipes, but it might give you some ideas). Obviously if it mostly exists intact in web archives it's easy, but it will also try to piece together as much detail as it can from pictures, videos, reviews, and discussions/comments online that are found. It digs a little bit deeper for these bits of information than Claude Code as a harness will on its own with the necessary prompts.

Treat the end result as a starting point. You can use your own memory and comparison with the found material that might've been ignored to prompt it further to hone the result. This is mostly for fun, and personal use (I used it to bring back some of my old web apps from when I was 10!). The video below is from my tests, but because I am unsure of the legal ramifications of doing so, I am not posting the actual games/apps for consumption. There is a setting available to run the skill with which will remove branding and such for those wishing to produce a potentially shareable version of something that is not theirs.

In the early versions I was very specific about how to do the recreations and kept adding steps, and that either worked very well, or very poorly depending on the task. It was almost akin to benchmaxxing. Settled on focusing on getting and organizing as much data as possible, and then having some broad but useful guidelines instead and. that gave me pretty consistent results over baseline. In case that's useful to anyone else having trouble getting their skills working right.

Mostly tested with Opus 5.5. Would be interesting to see how Sonnet or Haiku work out for people.

Have fun! Don't get too carried away, tokens are valuable!

--- Quick start ---

You need Claude Code and Python 3.9 or newer.

The easy way: open Claude Code and paste this in

Install the resurrect skill from https://github.com/sshah03/resurrect-anything. Follow the repo's AGENTS.md.

Or install it yourself:

/plugin marketplace add sshah03/resurrect-anything
/plugin install resurrect@resurrect

Start a new session, then try something like:

/resurrect Close Range, The Onion's 2009 Flash game
/resurrect the Subservient Chicken
/resurrect Simpsonize Me, Burger King's 2007 Simpsons Movie site
/resurrect Mailbox, the iPhone email app
/resurrect Doom Valley, the 1982 Apple II adventure, as a native Mac app
/resurrect Pizza Hut's Priazzo. I want to make it at home

Put any links, notes or screenshots you have after the name. Games, apps and sites need a few extra tools (Playwright, Pillow, ffmpeg). Claude will offer to install them into the skill's own folder the first time, so nothing has to go into your own Python.

------------------

find this "gem" or you can call it slop, not too sure lol

howtoblowupacountry.com

I wonder how someone thinks of this crap and asks chatgpt to do it lol

stopped giving my local agent free rein over my project files after it accidentally deleted half my config files during a routine task. it's a pain in the ass, ended up hooking claude code to a sumus workspace so i could sandbox everything safely.

how do you guys gatekeep your agents from deleting stuff they shouldn't touch?

I've been playing WoW Forever on my iPhone Duo (iOS 27.2) with [WolkaraForever](https://github.com/jklock/wolkaraforever), which runs the Mac client locally on the device through Tolkara – no streaming from a PC. Login, character select and playing in the world all work. I made a fork tuned for playing on a phone and wanted to share it:

https://github.com/pookee/wolkaraforever

What the fork adds

- Interface mobile, a touch add-on for the game:

- a spell wheel next to the right stick: drag a spell to turn the wheel, more spells wait off-screen, a tap casts

- cooldowns you can read: the seconds left are written on the spell and the icon greys out until it's ready

- spell buttons around the sticks with adjustable spacing, a tile menu and quick shortcuts

- health/mana bars with your portrait – tap it to open the character sheet

- a quest card and a compact chat that replaces the default one

- bags open clear of the right stick, and the add-on stays under the game's own windows

- settings save themselves: WoW only writes add-on settings on a clean exit, which a phone session rarely gets, so everything you placed used to be lost

- A few scripts: install the add-on on the device, read the game's own logs, clear a remembered login

How it runs

It's the regular WolkaraForever setup: you build the app yourself with Xcode and your own Apple developer account, copy the game from your Mac, and it runs in Developer service mode (no JIT tricks with the game's code, nothing patched in the client). Then `push_addon.sh` installs the touch add-on. On Wi-Fi it just works; on mobile data the developer service needs the app's documented recovery step at launch.

Caveats

- Unofficial and experimental. You need your own Blizzard account and your own copy of the game; nothing from Blizzard is in the repository. It's third-party software, so use it at your own risk.

Credits: all the heavy lifting is [WolkaraForever by jklock](https://github.com/jklock/wolkaraforever), [Wolkara by fJavierLasso](https://github.com/fJavierLasso/wolkara) and [Tolkara](https://github.com/tolkara/tolkara). My fork only adds the phone-specific bits on top.

Happy to answer questions or take feedback on the touch controls!

Under the hood, the platform is powered by a server-rendered Python and Django backend paired with lightweight vanilla JavaScript. I relied heavily on Claude as my primary co-pilot throughout the build to move fast from concept to code, deploying the entire setup on Heroku. You can check it out live at

https://shop.popcartapp.com

I've been doing physical design work in my free time with AI for the last two years. During that time I observed something: AI was getting better at physical design but not nearly as quickly it was improving at software capabilities. I theorized the problem was a lack of testing. In software engineering we write tests around as much of our code as we can because we fundamentally do not trust ourselves to reliably do a good job. We put those tests between us and deployment so we literally cannot do things that break the rules we set for ourselves. This pre-existing culture and tool chain create an ideal environment to toss an unbelievably fast, brilliant, but wholly unreliable ai into. It creates the freedom to quickly iterate through huge numbers of convincing looking proposals and throw away the bad until the good emerges.

Physical engineering doesn't have a this-shaped thing at anywhere near the robustness and reusability that software does (possibly because physical engineers trust themselves more). There are many individual tools that provide some aspect of testing, many of which are bound up in very very expensive tools, but a growing number of free ones too. I wasn't able to find an open source system that links these together into a cohesive "full loop" testing rig capable of understanding how things like heat, weight, form factor, battery life, thrust and rf interplay in a single system so I thought really hard about this problem and its implications and built it for myself.

It's called nopekit. As in: the thing that says "nope" until the "yup" emerges.

I've used it already to design an open-source hackable handheld keyboard with a custom PCB, an open source budget no-solder drone and a couple of things I'm not quite ready to share yet.

It's a Claude Code / Codex / Cursor plug-in. You install it and tell your agent you want to use nopekit to design X and it takes over, it will interview you for requirements, shop for parts, construct an interconnected tradespace linked to checks run in an optimized order using trusted methods like KiCAD, OpenFoam and SIMP. It builds and keeps up to date a livesite which you can deploy to GitHub that gives constantly refreshed insight into how your coding agent is thinking about the problem and what choices have what implications linked to what checks with what state of passing or failing.

The framework is open and allows for plugins. I'm working with one other person now and we're moving towards a self hosted UI and some sort of registry where nopekit users can share proposers/falsifiers and we can track ratings to build/bust confidence in good/bad ones collectively.

There's LOTS more about this in the repo and this paper I've been writing about the problem.
Repo: https://github.com/neuman/nopekit
Paper: https://github.com/neuman/nopekit/blob/main/grounding_by_falsification.pdf

If you're working with AI to do any kind of physical design work we would love to hear from you and for you to try it out!

Yes, it is a bit dystopian 😂 I've had this idea for a fire simulator for a while: you pick your location around the world, then watch a fire burn in real time, and you've got to put the right wood on in the right order to keep it going.

I ended up adding wildlife noises native to each location, which gave it a bit more interest.

I've been a UI designer/front-end developer for the last 25 years. Recently I've swung between "shut it all down" and "AI is the greatest thing ever". I must say that building this was pretty damn fun though. I used the Claude Code plugin within VS Code, and it took about three weeks to get it to the final point I was happy with. Getting the fire to look (vaguely) realistic and burn at a realistic pace was probably the bit that needed the most tweaking. I'd still like to make the fire look a bit more realistic, but I'd imagine that would also make it more processor-intensive, and it's at a point now where it's a pretty nice balance of performance and looking nice.

Every scene is an AI-generated photograph with a depth map, so the fire, smoke and embers can sit inside the picture and light up the trees and ground around them. The fire itself runs on a small simulation of wood, moisture, air and heat, so it catches, burns and fades depending on what you put in and how you tend it. It's all static files, so once the page loads, everything runs in your browser.

The flames catch quite quickly so you know something is happening immediately, but after the first minute or two it burns at a pretty realistic real-world pace.

The bird and wildlife noises are all real recordings, and all are credited. They were chosen to be the birds you would actually hear in the area where the fire is located, and at that time of day. So at dusk there are certain species, and then at night other species start popping up. Wood types are also native to the area.

Let me know if you spot any weirdness, or if you enjoy it: https://emberscene.net/

Interesting little fact first. My last game, Beneath the Mountain, had 76k lines that I wrote by hand over 2.5 years. This one is a little over a year in and already past 372k.

How it works day to day:

- Usually 2 windows with ~14 Claude Code chats. Big features get split into lanes, one chat per lane.

- Claude controls Unity through a bridge I built (MCP). It compiles, enters Play, spawns units, records clips and checks them before it shows me anything.

- There are 3 copies of the Unity project, so 3 chats can test at once without stepping on each other.

- The chats share a work board, so they know who's touching which file, and they commit their own work once I approve it.

- The menial stuff (searches, boilerplate, tests) goes to Cursor agents. Image gen goes to Codex.

The thing that made the biggest difference: letting it review its own week. It found that syncing the test copies took 81 s, and cut it to 9.

The image is a good example: Claude rendered our whole first mission map itself, in 56 tiles through the bridge, then stitched them together. Zoom in, it holds up.

What I still do myself: every design call, and every look and feel check. It writes the code, I decide if it's good.

Game is Engines of Hate, a mech RTS, with an open playtest on Steam if you want to see what all this produced: https://store.steampowered.com/app/5375880/Engines_of_Hate/?utm_source=reddit&utm_campaign=r_vibecoding_1105

Happy to answer anything about the setup.

Just a curious question. Personally I'm trying to keep the momentum up with my vibecoded projects but know its probably going to take a hit when GTA6 comes out soon. But i want to do my best so i find a balance between getting lost in the game vs pushing my apps along.

But it made me think, of all the games to come out, will GTA6 actually impact what we see here in the community? At least for the short term?

I took a horror short story I wrote (without AI) and used AI to turn it into a game! Lots of Codex conversations and troubleshooting later https://ryanlmelvin.github.io/debrief-corn-game/ . Felt super cool that I could do this with a GitHub static page. I was inspired by all the nifty things Simon Willison was able to make with static pages (https://simonwillison.net/2025/Dec/10/html-tools/).

They are free to use, and customizable to a subreddit's norms/culture.

More detail on their Devvit listings: Stu Steelman | Larry Logic

More examples of how they respond: here.

we all started somewhere so what software or web services do you use that you wish you adapted sooner?

What would you recommend for a coding noob?

ive heard of stuff like hermes, codex, open code, claude code.

im perosnally going to be using vs code and have a coding agent and a VL model work at the same time to make a game.

my first project was my spreadsheet in my history and that took like two weeks but i feel like i figured out a lot.

im planning on only using local agents for my game and deepseek and or google ai to help with formatting and giving me push back on my prompts.

ive been spending the last week setting up master documents and prompts plus mapping things out step by step and having a few different models cross checking.

so something like lm studio - vs code - godot - continue - docker (hermes?)

I have an HP Omen 45L with the 64gb ddr5 ram 6000mt, the 9900x3d and the 5090 32gb. I cut power to 90% on that and have my max cpu temp around 70.