My AI agent rewrote one of my GLSL shaders. On a Samsung A-series phone the scene went from 60 FPS to about 20, and I went back to my own version.
Claude Code and Codex have lived in my terminal since early 2025 (Copilot in VS Code before that), and they write a lot of the code for my studio's client sites. Most days that's a good thing.
The agents handle the Next.js skeleton, types, routing, forms, tests and refactors, plus sitemaps, robots.txt, schema markup and translations. My starter repo runs on 10 to 20 skills pulled from other people's work and checked before they went in, and a second agent reviews my plans before anything gets built.
Design direction stays with me, and so does a short do-not-touch list. You could keep a list like that for the risky stuff only and let the agent run free on admin panels, internal tools and short landing pages. I keep the same list everywhere, and for most of it I can point to the moment an agent got it wrong.
Anything that has to run on a real phone
GSAP timelines and shaders are the first thing on the list. One section had a ScrollTrigger pin that kept jumping, and I handed it to the agent.
The agent fixed the jumping pin so well that on the phone there was nothing left to pin. I saw it during my own phone test, in the evening, and spent the next two to three hours putting the section back together. The shader from the top failed the same phone test.
Several pages, one canonical
On one project the agent gave several Next.js pages the same title and the same canonical. I only found it when I ran an SEO cannibalization skill on the project. Titles and canonicals I set myself.
Nothing loads before consent
The project used Consent Mode v2. The agent put GA4 and the Meta Pixel straight into the layout anyway, and they loaded before the user gave consent.
I spotted it myself, and it's one of the reasons I built my own analytics setup skill.
The package I didn't check, and the copy
The agent suggested an npm package and I accepted it without checking, so that one is on me. It pulled in dependencies I didn't want.
Copy is the one job I still hand over and then take back. The agent writes the draft, I correct it, and on Polish sites I sometimes run my own skill that checks the text for AI tells. A client doesn't pay for a site that sounds like "Discover the future."
Same rules for the admin panel
A site looks AI-made when nobody had the nerve to tell the agent no. That includes the screens only your client's staff will ever open, so the admin panel gets the same list as the homepage.
Where I might be wrong
Shaders and GSAP may stop being a problem within a year, and then the list gets shorter. For now I keep it in my head and nowhere else.
So that's my list. What's one thing your agent doesn't get to touch anymore, and what happened the day it went on the list? If you think the admin panel rule is overkill, tell me what you let slide there and how it went.
Top comments (0)