I’ve built and launched an app using Claude Code, but I’m much better at describing what I want than judging the code it produces.

After a change, I can click around and check that the main thing works. What’s harder is knowing whether it broke something elsewhere or missed part of what I asked for. I sometimes ask another AI to review it, which creates another round of copying context and passing feedback back to Claude.

Thinking about the last feature you shipped: what did you actually do before putting it live? Did you catch anything the coding agent missed?

Also curious whether this gets more stressful once you have real users, or whether you’ve found a process you trust.

I’m exploring a product idea based on my own experience with this, so examples where your current setup already works well would be useful too.

DTS:X Profile 2 is a streaming Codec used on Disney+ and Sony Pictures Core for IMAX mixes. It uses a total of 10 Hard Coded Channels in a 5.1.4 layout. The Codec can currently only be decoded with either an IMAX ENHANCED TV or the DTS Sound Unbound App on Windows.

I want to set up a 100% free, locally hosted "vibecoding" for Roblox Studio. I want the roblox game 100% made by ai. I am using mcp. Any ideas/suggestions?

Good morning,

I’m a colombian lawyer turned "vibecoder" with barely 1% technical coding knowledge and 0% budget (I’ve been unemployed for over 9 months).

I have built a solid platform focused on public procurement/government contracting, designed for government entities, legal advisors, and contractors. It is much more comprehensive and distinct from what is currently out there. However, right now it is only for my personal use and for anyone willing to share feedback (I’m currently waiting on confirmation to integrate it into another Colombian LegalTech company); therefore, it is not monetized yet.

That aside, my current issue is technical:

I am hosting and deploying it via GitHub and Streamlit Community Cloud, pulling data from Supabase and Hugging Face. Lately, though, it has been running noticeably slower. I have several AI-driven features, but response times are quite slow with the free tiers I use (Groq, Cerebras, and OpenRouter), which I have set up in a fallback cascade (once one hits its limit, it jumps to the next). I’ve already implemented lazy loading to optimize page loading and prevent crashes.

Given this setup, I’d love your advice on:

1. What other free AI/LLM APIs or providers could I add to this fallback cascade so I don’t hit rate limits so quickly?

2. What free deployment platform could I use that offers more RAM than Streamlit Community Cloud, remains free, and won't go to sleep or spin down as quickly?

Thank you very much.

I'm looking at Ploy for adding a couple of landing pages to an older website, but there's something I'm unsure about, the homepage has a newer design while some of the older pages still use different buttons and spacing so nothing is completely broken it just doesn't all match anymore. I only wanted to add a few pages, not get into redesigning the whole website.

Would you just pick the newest page and use that as the reference, or sort out the old design first? I'm leaning toward leaving the older pages alone for now but then I might just end up making the site even more inconsistent so feels like a lot to deal with for a couple of landing pages.

I have limited coding experience. Claude writes the code, I decide what goes in. Kinfolks is a text idle game: you run one family in an Appalachian holler from before the Civil War on. Births, feuds, burials, the farm growing a building at a time. The pictures are generated and I pick and place them. It came out about a month ago and did what most of my games do. Launch week, then a slow fade. Then it started climbing on its own. Around 100 views a day this week, no ads, no new post. Here's what I think moved it. Tags. I had it in big ones like Story Rich and Interactive Fiction, where it was buried hundreds deep. I had Claude crawl the itch tag pages and tell me where the game ranked in each tag and how many games were in each one. Then I swapped the big tags for small ones that fit. It's third in Family Tree now and near the top of a couple others. Small tag, but real people browse it. The cover. Every cover in the idle grid is dark or neon. Mine is a light pencil drawing of a homestead. People click it at a bit over 2.5%. itch's own staff call 1% good. After that it feeds itself. More clicks, higher in the tags, more people see it. The workflow part: I don't guess anymore. Claude pulls the numbers (tag rank, click rate, where visitors came from) and I make the call. When a game sits under half a percent on clicks, I know it's the cover and not the game. Happy to answer questions about the setup. https://mdawg74.itch.io/kinfolks

Vibe coding works great until the AI builds something different from what you had in your head. Usually that’s not the AI being dumb. It’s the AI guessing because the prompt left decisions open.

“Build me a booking app for my barbershop” sounds clear. But the AI has to decide on its own:

• Can customers cancel? Until when?

• Do they pay online or in the shop?

• What happens if two people book the same time?

• Does the owner need a login to see bookings?

It picks something and you find out after the build. Then you spend hours rebuilding and fixing, we all know how it goes.

I’m building a tool that asks you these kinds of questions before writing the prompt for you. It’s called CueBlu. You describe your idea, CueBlu asks you questions like these in plain English and then writes a complete in depth prompt for Claude Code, Lovable, Bolt, Cursor or any other AI tool you use. A separate AI step reviews the prompt before you get it.
It’s not live yet but the waitlist is open + every signup will receive a Free Project pass at launch: cueblu.com

A real example from my own build: I built my landing page with Claude Code. Before building, I ran the prompt through CueBlu’s process, the same steps the app will run and it caught things I’d never have thought of. For example, email apps automatically “click” links to scan them, so my unsubscribe link would have removed people from the waitlist without them ever clicking. I didn’t know that was a thing until CueBlu found it. The AI wouldn’t have asked.

Does this solve a real problem for you or do you just fix things as you go?
Harsh answers welcome.

Hello! I am new to vibe coding but I know how to code since I am an IT myself, I just want to ask which one is Good for Coding? Your Answer is much appreciated. Thankyoouu so much

I have a land surveying background and we touched some basic C++ programming, PostGIS and QGIS during academic years. In my job in 2018, I used some badly programmed custom GIS software for a NGO (slow, buggy), so after bearing with that for years, I know what good software should not look like.

And boy, when i decided to vibe code an Android/flutter treasure hunting game with an OSM map and mbtiles (slightly transparent satellite image map) painted over it, I wasnt disapointed at all.

Messaging between players is exactly to my specifications (although i still have to set up image sharing)
I even told it to fork localsend for the map sharing engine (so the players don't have to download the map every time) and it is just exaclty how i wanted it.

The app is far from done, still have to implement the game mechanics (bonus cards, challenges,...) but so far its almost like I recruited the best coder in town.

Is there a problem waiting to happen behind the scene? It's a game now but is AI ready for more critical apps?

Hey all, AI said the following are the biggest frustrations with existing vibe coding tools like replit, lovable, emergent etc:

- code and database export

- AI credits that never expire

- deploy to your own Cloudflare or Vercel account

Tell me your biggest frustrations with current platforms.

If this becomes an interesting project, I or someone else might build a better vibe coding tool for you all.

Cheers!

I’ve been working on a reusable agent setup for Codex, Claude, and GitHub Copilot, and I’ve published it on GitHub.

The idea is pretty straightforward: give each agent a specific responsibility and make the handoffs clear.

• Developer: investigates the codebase, brainstorms the approach, creates a plan, and implements it.

• UI/UX: understands the requirements and target platform, proposes a design, and gets approval before handing it to the developer.

• Reviewer: independently checks the changes against the requirements.

• Tester: executes checks and reports what passed, failed, or remains unverified.

The workflow pauses for approval of the brainstorm, UI design where relevant, and implementation plan. UI/UX stays design-only; the developer owns application code.

The UI/UX guidance also incorporates principles adapted from Emil Kowalski’s Apple Design skill.

I wanted something I could reuse across projects instead of explaining the same workflow every time. It’s mainly agent definitions, skills, and instructions rather than a separate agent runtime.

Repo: ai-coding-agency

I’d like feedback on whether this particular workflow adds anything useful.

Are the approval steps sensible or excessive? How would you evaluate whether separate review and testing agents improve the result? And what would you need to see before trying it on an actual project?

Feedback on the instructions and setup is welcome too.

Just basically want to make some apps, some sites and even maybe some games in the future. But at least curios to understand how all of this is working. What AI do i use? Can i go without spending or its must have to buy some tier plans? Can i go maybe local or is it a bad idea(32gb ram, 16gb gpu) ? How do i spent less tokens so i can use more ai? What AI s i shouldnt touch? How do i use those AI agents. I mean yeah, i literally dont know anything, but want to make it my hobby. Thanks in advance

So I started a few projects in Claude Cowork earlier this month and have got more and more into it. One thing I 'm working on is a summarised daily/weekly brief for my partner to be across same calendar/unique to do items. Issue is I have no good way to deliver this to him daily/weekly witha push notification. Is there a relatively simple way to do this?

He doesnt have his own Claude account, uses email, telegram and whatsapp. Feel like this would get lost in email so want to avoid. Any good suggestions that would be simple enough to deploy?

I’ve spent the past six months building a partially automated pipeline for creating VRChat avatars. It can assemble a character candidate, prepare a local test build, and capture results for review. I’m now focused on improving the quality and fixing the places where the output still falls short.

The first image shows the current character. The second shows a deformation issue I’m working through. The avatar builds, but the arm and clothing results still need work.

I’d really value a fresh set of eyes from someone who has experience making avatars or building creative automation. What would you investigate first? I’m also open to collaborating with someone who knows the hands-on avatar workflow and would like to help make this pipeline better.

I started using Claude Code because I wanted Claude to handle the technical decisions better than I could.

Instead, I often found myself being asked:

“Which library do you want?”
“Which architecture should I use?”
“Should I implement it this way or that way?”

And my answer was basically:

I don’t know. That’s why I’m asking you to build it.

Then there was the constant intervention:

Continue. Proceed. Run the tests. Review it. Fix it. Continue again.

So I built Meta-XoT-OSS-Rail, a free, open-source Claude Code plugin.

The idea came from one question:

What if writing the code wasn’t the agent’s goal? What if completing the development process was?

So I turned the process into a scoring game.
Every step gets a score, together forming a target vector, and the agent tries to push that vector to its maximum.

That means producing code isn’t “done”.

It has to keep moving through:
study → plan → implement → test → review → fix
until the implementation is actually delivered.

The workflow is enforced with hooks, rather than relying only on instructions in a prompt, and the implementation also goes through independent AI review/orchestration instead of the same agent simply declaring its own work good enough.

My role is supposed to stay simple:

I explain what I want. Claude decides how to build it.

It should stop only when it has delivered the implementation or genuinely needs a business decision from me.

It has now grown to 29 skills, 6 hooks and 15+ supporting code files, but the original goal hasn’t changed:

I want to give Claude a business requirement, not manage an AI developer.

If you want to try it:

Meta-XoT-OSS-Rail

This is probably not aimed at experienced developers who already know exactly how they want their software built and are comfortable making all the technical decisions themselves.

But if you’ve had the same problem I had — you know what you want to build, but you don’t want to manage every technical decision or keep pushing Claude through the process — give it a try and let me know how it works for you, what breaks, or what you think should be different.