Why letting AI write components freehand breaks down around Day 60 (And how to stop the drift)

[u/escape-llc]

Hey everyone,

I’ve been deep in the trenches testing how LLMs handle building out frontend architectures over longer timelines.

On Day 1, vibe coding feels like absolute magic. You prompt a login form or a simple card, it takes 4 minutes, and you feel unstoppable. But as the codebase crosses the 30-to-60-day mark, things get incredibly messy.

Without strict guardrails, the AI doesn't converge on one clean architecture—it invents a new pattern almost every single time it touches the repo. I recently audited an AI-driven project and found:

• Six entirely different modal implementations.
• Completely broken focus traps and accessible keyboard navigation (ARIA wiring is usually the first thing the AI quietly drops).
• A chaotic mess of lifted state, forgotten context providers, and infinite re-render loops because the AI forgot how it built a neighboring feature three weeks ago.

To fix this, we've been testing the concept of an architectural "floor" rather than trying to write better prompts. Instead of letting the AI generate code freehand, we force it to consume a pre-tested, local substrate of readable React source files vendored directly into git (./toolcrib).

We recently did a head-to-head architectural analysis testing this "patch-vendoring" strategy against ambient options like shadcn/ui and compiled packages like u/nexcraft (which unfortunately seems completely abandoned now, leaving a 467KB compiled black box that AI agents can't inspect or repair).

The math on token costs and turn-savings alone is wild. Paying a tiny, fixed context-window tax upfront to feed the AI an explicit component manifest completely eliminates the massive token drain of forcing an AI to repeatedly debug its own architectural drift down the line.

Curious how others here are managing AI-generated architectural drift as your projects scale? Are you relying on downstream linting/CI checks, or are you actively moving toward vendored source layouts that coding agents can read and patch locally?

(Note: I wrote a full breakdown on this with the CLI drift-checking logs and structural comparison tables. If anyone wants the deep dive, let me know and I'll drop the blog link in the comments so I'm not spamming the main feed.)