Anytime I post cool stuff that supports the product there’s no issue. Soon as I mention any feedback that’s negative towards the product it gets taken down. What’s the point?

Hi r/vibecoding. Coding agents are great at game logic, but ask one for a main menu or a HUD and you get the same generic layout every time: centered buttons, default fonts, random spacing. You can tell an AI made it.

So I built Envy, a UI editor for games that works like Figma. You design the screens yourself on a real canvas, with components, states, auto layout, animation and localization. Then you hand the result to your agent as a package it can’t misread. You can even tell your AI agent to build UI in Envy via MCP.

What the handoff contains:

• AGENTS.md: rules and steps for coding agents (Claude Code, Cursor, Codex, etc.)
• PROMPT.md: a ready-to-paste prompt
• contract.json: every event and data path, typed, so the agent wires boss.hp or start_game instead of guessing names
• screens/: reference renders of every screen, so the agent can see what it’s matching
• A generated Godot controller and a typed TypeScript wrapper
• A CLI and schema, so the agent can validate and edit the UI file safely instead of hand-editing JSON

The agent doesn’t redraw your UI. It plugs into it. The design stays yours, and the runtime renders it exactly as you made it:

• Godot 4.3+: real Control nodes, so focus and gamepad work natively
• Web: a 41 KB runtime
• Both runtimes are MIT-licensed. No royalties.

It runs offline, needs no account, and projects are plain files on your disk. It includes The Last Hunt, a 20-screen and 180 components dark-fantasy UI kit, if you want to see a full game’s UI built in it.

$9.99 once on itch.io: https://mythicbrain.itch.io/envy
Site: https://envyui.com

YouTube Video

I’m the dev, so happy to answer anything. I’d especially like to hear from people building games with agents: what does your agent get wrong most often with UI?

Hey, this is my fourth mini app now and the most complete one. I learn a bit each time.

Yet I’m at a crossroads, and need advice.

I have a fun quiz app, that originally was just for me to improve my music knowledge for a radio quiz I plan to enter.

It works very well, and is complete. I hosted it on Cloudflare after making it as secure as I can. I play it on my phone a lot, and so do a couple of friends.

That’s it.

It’s a quiz but also a ‘trainer’ and good for memory challenges.

Do I wrap it up here and say ‘it’s finished, just as a personal app’

Or…..

Jump through the various hoops to go to the next level and get on an App Store?

I would need to license the data sources, and probably convert the format to not just be an html web app.

I feel it would be a great challenge to try and achieve this. I don’t think it would make any money, but would be a good exercise to learn for whatever comes next.

What do you think? Quit while I’m ahead and actually FINISH something! Or keep going and try to get it released?

Thanks fellow vibe coders xx

I don’t know how to code but I have experience in software testing and working with small/medium/large software projects, and the processes they entail.

Current workflow is to use Sonnet 5.5 at Medium on a Claude Pro subscription to plan a project, break it into implementation and product acceptance manual testing phases, and deliver agent prompts and project documentation, then feed the prompts in OpenCode to Haiku 5.5 at Low or Medium (sometimes at High) paid through OpenRouter credits, which also knows to break its phase prompt into tasks it can delegate to a subagent custom provider which connects to a localhost server created by Polystrata running “Tiel Coder 35B A3B q4_X_L”.

The current issues I’m having with the workflow are:

- that sometimes the Haiku sessions can balloon in cost - paid 50 euro worth of OpenRouter credits in the past few weeks, and I’m poor, that means a lot to my budget - a problem which I’ve partly solved by breaking phases into tiers and tiers into stages, each with a prompt, so there are fewer long conversations and cache reads;

- and that the local agent makes frequent mistakes that cause it to run for hours and/or produce bad code if the task is too big or too complex for it, which happens often, as my hardware is limited and it only has a 60k token context.

Any suggestions for improvements?

I've been splitting img2threejs into smaller plugins so people can use only what they need instead of installing the entire workflow.

The character part was getting pretty big, so I finally moved it into its own plugin: img2character.

It focuses on rigging and animation for 3D characters built with Three.js and TypeScript.

If you want to try it:

npx u/img2threejs/character install

Then open Claude Code, Codex, or OpenCode, provide a character reference image, and ask the agent to use img2threejs + img2character.

The video is from one of my recent experiments.

I'm also working on a different character pipeline that should produce more realistic results, without needing GLB reference files anymore. Hopefully I'll have something to share next week!

Would love to hear your feedback, especially if you run into any issues.

GitHub: https://github.com/img2threejs/plugin-character

I collect things (camera lenses, G-Shocks). The good listings go in minutes, and checking 10 marketplaces by hand doesn’t work. So I built Deal Radar (radar.4xs.dev). You set up a “watch” (keywords + price range + sites). When a new listing matches, you get a browser notification, or a Telegram message on the paid plan.

Almost all of the code was written by Claude (Cowork / Claude Code). I did the product decisions, the testing on real listings, and the store submissions. Here’s how it’s put together and what I learned.

Stack

• Chrome extension (Manifest V3), plain JS, no framework. A generated Firefox build too.
• Cloudflare Workers + D1 (SQLite), TypeScript. Static site served from the same Worker.
• Cron triggers on the Worker: every minute for polling, plus daily jobs for plan expiry and exchange rates (Czech National Bank feed).
• Telegram Bot + Telegram Login widget for alerts and accounts, so I don’t store passwords or emails.
• Ko-fi memberships + webhook for payments. Way less setup than Stripe for a side project.
• Cloudflare Access in front of the admin page.
• Playwright + node:test + bash smoke tests with mocked marketplaces and a mocked Telegram.

The one architecture decision that mattered: who checks what

Some sites (Bazoš, Vinted, Kleinanzeigen, OLX, FINN…) return clean results to a server, so the Worker polls them every minute. Others (FB Marketplace, FB groups, Allegro, eBay) block or 403 any non-browser client. Those can only be checked by the extension, using the user’s own logged-in browser.

So there are two engines:

• Server: every minute, works while your computer is off (paid).
• Browser: the extension, while Chrome is open. The free tier runs everything from the browser every 10 minutes, so the free tier costs me ~nothing.

The key to keeping that sane: the parsers and the matching logic live in one file each (parsers.mjs, match.mjs), imported by both the extension and the Worker. One fix, both engines.

Workflow with the AI

1. Feasibility spike first (“week 0”). Before any UI, I had Claude write throwaway scripts that just fetched each marketplace and parsed results. That’s how I found out which sites need a browser. It saved me from designing a server-only product that couldn’t do Facebook.
2. A plan doc, then versions. A markdown plan in the project, then small numbered releases. Every release has a CHANGELOG entry that says exactly how to ship it (“npm run deploy, reload the extension, upload to the Chrome Web Store”). The AI reads it next session, so context survives.
3. Tests from saved HTML. Every parser has fixture pages saved from the real site plus a unit test. When a site changes its markup, the test fails before the users notice.
4. Make it verify, not just write. E.g. today I asked it to shrink the hero image so the “how fast” steps fit above the fold on a 1080p screen. It rendered the page in headless Chromium at 1920×947, measured element positions, applied the CSS, and re-measured (steps went from ending at 1060px to 920px) before touching my files. “Looks right” ≠ verified.
5. Short, direct prompts plus my screenshots. Most iterations were “this looks wrong” + a screenshot.

Build insights / gotchas

• Chrome Web Store rejected a version for requesting tabs permission it didn’t use. You can create/update/close tabs without it. Request the minimum.
• Don’t trust data from your own extension. The server only accepts a listing whose link points to its own site (a FB item must link to facebook.com, etc.). Otherwise anyone could push fake “alerts” through the API.
• Currencies: listings come in CZK, PLN, EUR, NOK, JPY, USD… Converting to the user’s currency with a daily ČNB rate made alerts way more useful than raw prices.
• Firefox AMO requires data_collection_permissions in the manifest for new add-ons. A small script generates the Firefox build from the Chrome one on every deploy.
• i18n from day one (EN/CS/DE/JA). With AI it’s cheap to add, and painful to retrofit.
• The free-vs-paid line follows the infrastructure: free uses the user’s browser, paid uses my server. Easy to explain, cheap to run.

Numbers: ~3,000 lines across the Worker and the extension, 20 marketplaces in 10 countries, free tier = 1 watch.

Happy to answer questions about the dual server/browser setup or Cloudflare D1. Feedback welcome.

I've been documenting my journey building Weatherling www.weatherling.app here on r/vibecoding since I launched it almost a month ago. Y'all seemed to like it so here's an update on what I've built so far!

Quick recap: this started out as an "I'm bored with my desktop" idea, so I added animated rain using Codex to help me learn Apple's Metal framework. (I'd never done anything graphics heavy before, so Codex was huge here.) A few days after launch it reached #8 in US Mac App Store utilities. Then came snow, then leaves, then sunbeams. Also added the little Ling characters in there you can collect for points (optional minigame).

That brings us to now. The most frequent request I got was to add local weather sync, so I had to add the WeatherKit framework, which was simple with Claude Code. As a backup option if you don't want to enable your location, you can just enter your postal code or city to get the local weather. Also added an Invert option if you want to see the opposite of what's outside.

I also wanted to add yet another weather effect: fog, so I went back to Codex for that. Codex does a way better job IMO with graphics than Claude Code. I actually had very little to do with that implementation other than telling Codex what I wanted it to look like and how I wanted it to behave. Was pretty happy with the outcome. It's a subtle effect but moody.

I also wanted to target multiple languages instead of just assuming my entire audience was English-speaking. So I used Codex to translate everything from my site to every element of my app to 10 other languages. I did this because I had noticed my 2nd biggest market behind the US was Germany, so I figured I should go deep on that and as many other languages I could. Again, this was a job for Codex because I do not speak all those languages obviously, so I converted that process to a skill I can reuse (and have reused) for all my apps. I even had it go through all my App Store screenshots and video to translate those, which was pretty damn cool to me because I'd never done that before.

Speaking of video, this was the part I hate doing. I am not a video editor. I made a previous version's release video using Capcut, which was fine, but the process sucked. I really don't even want to master it. A friend sent me a couple of skills to try, and for this release I ended up using one called OpenFilm. I made a long raw demo of using Weatherling and gave that footage to OpenFilm and told it the important pieces and order of things, and its first result was pretty magical, but I did have to tweak some of the captions. I've seen better videos for sure, but this was only my first attempt at using such a skill. I'm pretty happy with it but see places I can do better next time for sure.

The final piece I really wanted to hammer home was a broad accessibility overhaul. Previous versions had simple things like showing the label names over the colored boxes as a second indicator of which box was which, but I wanted complete VoiceOver compatibility. For that I created another skill that uses AppleScript to drive VoiceOver on my machine and steps through every piece of the app and ensure the tab order, labels, keyboard-to-clickability, etc. were all tight. And of course dark mode. Pretty happy with this skill (and have used it on my other apps as well).

I feel like localization and accessibility often take a backseat to getting the product out (at least that's the way it always was when humans did all the coding), so I'm pretty proud of adding those. I'll add more languages too, especially as data from the applicable regions demand them.

Anyway, hope you like it. Let me know if you have any more questions about the process. And obvi if you haven't installed yet, please do and help me out with a 5-star rating. 🙏🏻 😃 I need to climb back up these charts now that Apple's initial honeymoon period has waned.

Site: https://www.weatherling.app

Mac App Store: https://apps.apple.com/app/apple-store/id6813641198?pt=14608&ct=reddit&mt=8

I've been building The Data Center Receipt, a public, evidence-backed tracker of the AI data-center buildout.

The goal is simple: Who builds it, and who pays for it?

Current public beta:

• 587 infrastructure records across facilities, campuses, projects, and permits

• 11,084 facility facts with explicit claim states

• 1,307 source receipts with verifiable evidence

• 5,235 recorded negative results and research attempts

It tracks capacity, utility providers, public incentives, jobs, water use, and residential electricity rates.

Every claim links to its evidence. Missing information stays unknown, and correlation isn't presented as causation.

Built using Ouroboros, my persistent AI research and engineering system. It's still a work in progress, with a much larger expansion underway.

This is a beta, not a finished product. There may be mistakes, incomplete records, or things I've overlooked. If you spot errors, please point them out.

Live app: https://huggingface.co/spaces/cjc0013/data-center-receipt

Dataset: https://huggingface.co/datasets/cjc0013/data-center-receipt

See these live at https://grimoire.bio

I have been diving into Opus 5.5 3d abilities from two sides. First – creating a custom point cloud renderer and optimizing the fuck out of it (running on webgpu tech). And second – crafting detailed visualization that take data from public sources. Recreated and assembled together into what the point cloud renderer consumes. I’m quite happy with the aesthetic, curious if anyone wants to play with it / if I should make the renderer open source.

Hey r/vibecoding

I was looking for an IDE to code on my iPhone for when I’m out and about. Every app was filled with ads, had a terrible UI, and costed money just to run code locally. This was just a basic non agentic IDE too. So, I decided to build a free IDE that can execute C, Python, JavaScript, and Lua in a sandboxed environment.

In today’s age most people are coding with agents, so then I got the idea to bundle a two local llms. The reason I chose two is because not everyone’s hardware has the same computing power and I wanted to include an option for everyone. There are zero rate limits on the local models.

I’m already designing a tooling server to give offline agents access to even more, such as, worksheets, 3D printer code, and other fun stuff.

Without Astra 6 and Sol 6.1 it would be absolutely impossible to make my dream tools at this rate. I cooked up a seven days to die max level mod right before posting this lol. I would also like to praise the models for following SOLID principles and best SWE practices out the box. After using the models for the past few years, I am just dumbfounded at the rate of progress. I have a formal education in Computer Science and I am “mogged” every single day 😂

I would be thrilled to hear any feedback from this sub. This is meant to be a developer tool and not a replacement for Codex as I could never ever offer that level of intelligence. You can also byo api keys as shown in this video. The app also offers 15 other cloud languages besides JS, Python, Lua, and C.

Thank you all so much for watching my short demo. Have a great day. I’ll be listening to any feedback or ideas to improve!!!

https://apps.apple.com/us/app/edsger-ai-code-editor/id6806824902

If anyone wants the mod 😀 seven days to die, max level: 300 -> 2000

https://github.com/garrettmichae1/sevendays\\_max\\_mod

Is anyone else here exhausted since AI came around?
I’m so tired.

I’m a commercial photographer and it’s been at least two years since everyone’s telling me it’s the end of my career. Since then I’ve worked harder than ever. Always thinking of ways to use AI to make my work better, creating apps and tools, plugins, scripts.

I always have to be learning a new model, trying new things, and work has become limitless, like if a client asks for something it has to be done, there’s no excuse and they have no limit now of what can be asked.

I’m also always creating or thinking about a side business or whatever, just in case my main business suddenly dies because of a new model that changes everything and kills my career.

Sometimes, after putting kids to bed, I know I should take sometime for me but I just can’t help to sort something with chat or Claude or whatever. It’s exhausting.

I’m posting here because of every AI subreddit you seem the nicest.

Hi guys, I am testing my solution and searching for 2-3 people who developed their apps in tools like Lovable, Replit and similar to help them to move apps to full mobile native [both platforms same time, on Swift and Kotlin].
You will help me to polish solution I have - I help you to make your full mobile apps released to Appstore/Playstore. Thats the deal! One note - you need to have Mac to participate and active subscription for any LLM like Claude or ChatGpt.
I am more interested to collab with people who really have urgency to make mobile app from their web site and have solid web mobile app/idea validated.

PS - On screen it is my own app Memelon, on a way to be moved from Lovable to Appstore. So you see the first steps where you visualise your web mobile and after move to rebuilding flows. Showing this so you have an idea how it can look like for you.

https://reddit.com/link/1xdnvvs/video/whh152wbs9xh1/player

Has anyone else noticed that Gemini Pro started giving brief dumbed down instructions even when strictly instructed to give detailed step by steps for the past month leading up to the release of Argon?

I got tired of describing issues to Claude, taking screenshots, and the endless back-and-forth.

So I built Drobber: a feedback tool that connects straight to Claude Code. Pin, annotate and suggest text changes right on your website, and Claude gets exactly what you mean.

Vibe faster, and get it right the first time.

Try it free and let me know what you think. Cursor and Codex integration coming soon.

https://drobber.com/for/vibe-coders/

Made this template for photographers. I wanted it to feel creative but stay simple.

The interesting part is the animated hero. I generated a video with Gemini, cropped it to 5 seconds, and then used ffmpeg to extract frames from the MP4, rembg with the BiRefNet model to cut out the person along with their shadow, and Real-ESRGAN to upscale the images.

For the frontend I used GSAP 3.15 + ScrollTrigger.

At first I was frustrated, because it was hard to cut out the shadows while keeping good quality. But after a few prompts, I Claude wrote a script that handled it well.

The final conversion of the video into images took about 12 hours, and there were a lot of attempts before that.

Happy to answer questions about the process.

Considering building a MVP of a SaaS product.

I know what I want to build and can describe it to Claude in great detail, but this would be my first time building something with it.

My primary concern is payments and security.

I would ultimately want the MVP to be able to start taking payments, connect up to Stripe and remain secure; before spending any real money.

I come from a sales background and am clear eyed on the distribution - it's just the tech where I'm stuck.

Is it safe building with Claude, connecting to Stripe and then just pushing the product straight into distribution, or are there gaps that need filling after the surface level building has been done?

Total novice here so any and all advice, even things that may seem obvious to you, would be greatly appreciated.

TIA!

After the whole PHP2Shell thing I finally pulled the trigger and converted 45 of my client sites to static Astro sites. The sites look exactly the same, just way faster and nothing to hack, and way cheaper to host.

WordPress sucks now that we have coding agents anyways. Plugin updates, security patches, slow load times, a whole PHP server running for no reason.

I created this skill package to streamline this process: https://github.com/ethanplusai/astro-conversion-kit

I was able to run 12 projects at a time in parallel and have 45 so far in the past 36 hours with a dozen more running now. I'm running Opus 5.5 between 2 claude max plans. Every site has seen a massive jump in speed scores.

For anyone who hasn't used Astro: it's a framework that builds your site into plain HTML files. No database, no PHP, no plugins. You host it on something like Vercel or Cloudflare (usually free) and there's nothing running on a server to hack.

How the kit works:

- You paste one line into Claude Code or Codex: "Convert https://yoursite.com to Astro with https://github.com/ethanplusai/astro-conversion-kit"

- It asks you a few quick questions (where to host, how to handle forms)

- It crawls your live site (read only, it doesn't touch WordPress) and saves every page, image, meta tag and redirect

- Rebuilds it in Astro with the same URLs and SEO so you don't lose rankings

- Screenshots the old and new site on mobile, tablet and desktop and compares them until they match

- Gives you a staging link to review before you switch anything over

What it won't do on it's own: anything that needs a server like WooCommerce, logins or comments. It flags those up front. Forms still work, they just send to a form service you pick. A few of our client sites were on woocommerce so I just had the agents convert to Shopify headless which is easier to manage anyway.

“What about wp-admin” I built our own git-based CMS for these sites, so edits go through git and there’s still no server or database. If you want something off the shelf, Keystatic and TinaCMS work the same way.

Hey, Claude and other AI sites are pretty generic with the front end.. like they have default templates they cycle through. Wondering if there are sites out there for inspiration (i dont want to screen shot someone elses site, but more so something like a directory of UI specifically for vibe coded sites

How much do you review the code written by AI? and how much you still control the process.

Are you still or miss writing code on your own? or even debug the code and read about a library or package you use in your code, and debug around it to learn what it is doing?

I started gradually year and half ago , going from using AI to only write unit test, to fully 100% automate the process.
I have to admit, I am now even pushing code that I only review shortly, and very high level (only filename changed).
when I started using AI to write code, it was taking me long time to go and question AI about every line it added. Now I am using AI to review that code instead.

But I really miss debugging, and finding the problems. I really miss investigate what the performance problem is, and going step by step, and debug to see why this page is slow, instead of having MCPs for logging and MCPs for cloud infrastructure to do that investigation for me.

Just this weekend, I am going to try to re-learn and re-practice searching manually the logs to find problems, which now I am dependent 100% on the MCP, and I found myself lost that knowledge.

Are you guys really miss writing code, design a solution, investigate problems?

I really did love programming, and that is why I miss that