The Architecture Reset

Every vibecoded app hits the same wall somewhere around the thirtieth file. One component is eight hundred lines, state lives in six places, and every change breaks something unrelated. The model can't fix it, because it can't hold the whole thing in view at once.

What's inside

• The three signs you've hit the wall, and how to tell which one you're looking at
• Splitting an 800-line component without losing a weekend to a rewrite
• Where state actually belongs, as a decision tree rather than a debate
• A folder structure a model can navigate on its own, so it stops inventing files that already exist
• Feeding an existing codebase to a model without blowing the context window, and the two files that stop it reinventing your utilities
• What not to abstract yet — the opposite failure, and how to avoid causing it

Who it's for

You shipped something real and now you're nervous about touching it.

Format

PDF, 13 pages. Every procedure is incremental — the app keeps running at each step.