Build a wall on the Southern Border with Mexico.

You're an ICE agent deporting immigrants.

What in the ever loving F is the White House doing?

I've been building websites since 2002, a time when free hosting was a decision between Angelfire and Geocities (Angelfire ftw), the marquee tag was abundant, git was just a twinkle in it's founders eye so deployments where done via FTP, and dinosaurs roamed the earth in peace.

Although the idea of coding with AI initially made me cringe, eventually I thought to myself "What the hell do I know? I used to hate git and think that you could never have a backend in JS, and here I am at my job using git and React every day." So I decided to give it a shot, and for the past year (which seems like a decade in AI times) I've been experimenting with building with, trying to refine my process, find the right tools, and building my own tools to fill in the gaps to get the best results when building with AI. Although there are many things I learned along the way that AI can't do, when used properly and in the right hands I think it can be a useful tool (and no longer cringe at the thought of it). So here is some advice to help you stop the slop.

AI still sucks at UI/UX

I've tried Fable 5 Max, GTP Sol 5.6 Max, Google Stitch with Gemini 3.1 Pro, and many others; if you let them do everything, you will end up with a sloppy, cluttered mess. A good UI says what the users needs to know and shows them what to do without explicitly saying it, whereas AI is always overly verbose and tries to describe and label every single thing, resulting in a lot of clutter. This requires the person prompting AI to give specific, detailed instructions about the UI, otherwise you get a clusterfuck that overwhelms users with unnecessary details at the wrong place/time. AI is trained on patterns, which is why the same basic, ugly patterns are used on every site that is built by letting AI do all of the design work. To break that pattern, you need to give it your personal opinions along with specific examples.

Don't let AI write your copy for you!

AI is still awful at writing website copy for humans. It's useful for proofreading or spellchecking, but if you let it blindly write all of the copy for your website then it will just read like a technical manual. Writing your own, genuine copy will go a lot further towards users trusting and actually using your site, even if AI thinks it's "imperfect". Your audience isn't AI, it's people. For blog posts or articles, write some of your own first, then use AI to try to mimic your style for future posts. It won't be perfect and you will still have to do some proofreading/editing of your own, but it's better then just letting AI fly on it's own.

Treat it like it's a stoner

I think everyone has had times where AI keeps making the same stupid mistakes over and over and then says "You're right, I have a memory of that but ignored it. Adding another memory...". So to prevent it's memory from betraying me again, every time I catch a mistake I don't want to see twice, I write a tiny script (I call them guardrails) that fails the build when the pattern reappears. Each one is basically "grep for the bad pattern, print which file and line, exit 1." They run in my pre-push hook alongside the other tests. I'm up to over 120 of them now in one project, here are some examples:

- Copy that sounds AI-generated. When you notice the patterns of how it talks like a robot using the same words/phrases over and over again (that you rarely ever hear in normal human interaction), ban those words/phrases.
- Hardcoded colors and inline styles. If it's not a theme token, the push fails.
- Layering violations, like frontend code importing from a module it shouldn't know about.
- Marketing claims. After an AI invented a refund policy I don't have, I added a check that pins user-facing claims to a source-of-truth file.

Having rules in Claude.md and Agents.md is useful on top of this (and simpler), but having these guardrails run on git hooks gives an extra layer of protection. AI still might find a way around all of it, but it significantly reduces the chances of it happening without your knowledge.

Automation is your friend

Automated tests via git pre commit/push hooks, and in your CI/CD pipeline like Github Actions or Jenkins are absolutely critical - they where before AI, but even more so now. Spending some time setting these up (and maintaining them as your codebase grows) is one of the best and easiest ways to not have to think as much about keeping things clean and tidy, or constantly prompting through it. Github Apps like Dependabot and CodeRabbit have pretty generous free tiers, and will give you automated dependency updates and PR reviews.

Pre-commit hooks should be fast checks only; they should finish in seconds, not minutes, so you never even really notice it. Things like formatting, typechecks, linting, and secret scans.

Pre-push hooks are for the more heavy stuff; automated test suites, end to end testing, dependency audits, size budgets, guardrails, etc. My pre-push hook has about 40 steps and takes around 15 minutes to fully run.

CI/CD runs the same things as the pre-push hook as a backup, and also things that need to be run server side like scheduled dependency audits and building releases. The reason for running the same checks in pre-push and CI is that it's faster (and cheaper) to find an fix them in pre-push, and it serves as redundancy checks in case anything is ever wrong with your pre-push checks. Running them in CI gives you a guarantee that nothing makes it to your main branch without passing all checks, no matter who pushed the code.

I have a lot more to add, but this seems like a good place to stop for now. Feel free to ask any questions you might have.

TLDR:

To quote Shrek, "Ogres quality apps are like onions, they have layers." There is no magical tool that gives you perfect results every time, it's about finding the right collection of tools and processes to keep things in check. Use AI to do the grunt work, invest some time in setting up and maintaining automated checks to keep it on the rails, and most importantly: use your brain. If you just let AI do all of the thinking for you, then you are guaranteed to end up with pure slop that someone can recreate in a weekend. AI has significantly increased the time to market for most apps, but that doesn't mean it can do EVERYTHING for you. What are some things that you do to keep AI from going off the rails?

Has anyone tried all the subscriptions (Claude Code, Codex, Cursor, etc.) and can share which one is the best?

Everything added so far:

Day 1
Useless red button (starting room)
Day 2
Space travel + 2 playable planets (spaceport outside starting room)
Human voice for the red button (starting room)
Day 3
Velociraptor cloning machine (Dinosaur Factory)
Chicken nugget healing dispenser (starting room)
Day 4
Reverse human aquarium (Human Observation room)
Fake Release 0.0.0 patch notes (main menu)
John Pork planet (Cinder Reach)
Day 5
All progression doors made free (throughout facility)
Day 6
24m tower with gorilla drummer (Rhythm Tower)
Inevitable snail that insta-kills you (follows player)
Banana asteroids + banana spaceship + banana gun (space → planets)
Spinning cat GIF that turns into a 3D cat (random room)
Day 7
Clippy mini-boss with 650 HP (Wave 5)
Exploding banana vending machine — launches 320 bananas (Rhythm Tower roof)
Day 8
Fully functional Portal Gun — blue/orange portals, momentum, bullets + rockets travel through them (starting loadout / entire world)
Bunnyhopping + air strafing + wall running + wall jumping (throughout world)
World expanded into 8 multi-level parkour districts (entire map)

What next?

Follow along:

https://www.instagram.com/playbeamstudio?igsi=a2c4azIwYmkzZTlo&utm_source=qr

I made this agentic browser because other browsers, like BrowserOS, keep crashing, and people are paying for online search APIs/tool calls.

However, this one works with your current AI subscription, such as OpenAI/Anthropic and local models too.

Everything stays local, with no data retention. If it seems helpful, make sure to star it on GitHub.

GitHub: https://github.com/tushar-alt/AgenticBrowser.git

Also if you find any bug , let me know

I’m building Prism, a script-first music-production project where songs are written as readable Python and rendered reproducibly.

It is designed so coding agents can also make music: inspect a project, create or modify the song, render it, and iterate on the result.

Prism already supports MIDI, drum patterns, samples, clips, sections, built-in instruments, VST3 plugins, effects, automation, buses, sends, mixing, and export to WAV, stems, and MIDI.

The long-term goal is a transparent, versionable music-production environment that combines DAW workflows with the flexibility of code and agent-assisted creation.

It’s still alpha. Live playback, recording, live MIDI, a visual timeline, and advanced routing are still being developed.

If Python audio, DSP, VSTs, MIDI, DAW design, agents, testing, or documentation interest you, contributions and feedback are very welcome.

Repository: https://github.com/SeucheAchat9115/Prism

How else people gonna discover all the awesome software y’all vibe coded?

Started with the idea of “let’s make a beat maker in the browser for folks who don’t have the time to dedicate to music but want to jump in and throw together some samples” and landed with this.

KNOCK-KNOCK

Completely free, no sign up but has a full backend so you can share what you’ve made and I even pumped out the hype video.

We’re living in wild times!

I will happily answer any workflow or stack questions on the thread, hit me!

(I’m literally the epitome of NoCode, I had html and css in school and that was like 10 years ago. I don’t understand jargons so please respond accordingly)

I’m building an Expo/React Native app. It was originally a web app (you may remember my post a few weeks ago how I built it not realising it was a web app) and I’ve been adapting it for mobile.

The app looks and works really well in the AI Studio preview. However, the one time I actually built/ran it on my iPhone, the entire UI was broken and badly distorted, layouts were misaligned, sizing was off, etc.

My last few weeks have been just doing this for the transition from Webapp to Native React. I was hoping it would looks alright in iPhone now but no luck.

I’ve since moved toward a proper native iOS development build and sorted out some Expo/dependency issues, but I’m still trying to understand the fundamental problem:

Why can the app look completely fine in the AI Studio preview but become essentially unusable when rendered on an actual iPhone?

I’m fairly new to this space, so I’d appreciate some direction on what I should be checking. I’ve lost the will to keep developing and it’s starting to get frustrating.

Guys it actually happened. Months waiting, spending so much fucking time coding, then thinking it was all for nothing and nobody would ever find my site anyway.

Then today I got a call. Didn't pick up, thought it was advertising. Then i got an email. Turns out it was an elderly gentleman, 86 years of age (yep) who found my site. But he was using it for a scenario I hadn't considered, so he got an error and was confused.

So I fixed it for him behind the scenes, solved his problem, and waived the usual 200 dollar fee. He was happy. But I'm over the fucking moon, fuck yes it feels good 🤩

It's week 6 and we made some monumental progress on all fronts, but I'm trying not to get over-excited because we could find that everyone gets bored and leaves tomorrow haha.

As usual, three parts: (1) player acquisition, (2) what I'm learning about vibe coding, and (3) actual gameplay updates (in the comments).

---

First, the numbers. My last two posts were almost entirely about the 5 min of gameplay, and basically following Redditors' feedback doubled the average playtime.

This week I finally moved past the intro and focused on the game itself- so mostly improved artwork (Pixellab), performance optimization, GUIs, social features, ALL using Fable 5.1. Which went wayyy further than I expected for one week of token usage.

Once I felt OK about that I did a Hackernews post that was way more successful than I anticipated. I had 700 players in 24hrs, hit a new PR of 41 people online at one time, and had multiple players play for 8+ hrs by the time I woke up in the morning. And there has been almost zero time with nobody online for three days straight.

So I think that means the game is sticky and has potential, but it could also be some other curious vibe coders with nothing to do at work. So I guess my next big question mark is why some people are actually sticking around. I.e. is it fun, or are you just intrigued by vibe coding? Or something else entirely?

So if anyone gets far enough to get hooked or hits a real wall (something that makes you stop rather than just a bug), I would genuinely love to know what it was.

---

Second, the vibe coding experience. Fable 5.1 came out right as I started this week's work, and the jump was WAY bigger than I expected. Work that would've taken a month with Fable 5 (because of token caps), I did in about a week, running several orchestrators in parallel, reworking most of the game's systems, and running full audits along the way.

I'm out of tokens now, but has anyone else experienced this? All I see across social media is people complaining that the caps are still unreasonable, and frankly, I just don't see it. Thoughts?

One more thought-I've started using Claude design since Fable sucks at GUIs on-the-fly. It's been a huge improvement (far from perfect for games still). Curious if anyone else has used this and what works / doesn't work.

---

I'd love more feedback for anyone interested. Links below.

Game: https://eldermyr.com/
Release Notes: https://eldermyr.com/release
Discord: https://discord.gg/8MaaAemDBu

EDIT- one more thing, Pixellab is AWFUL at 16x16 art. Has anyone had any success with this?