Vibe coding is useful. It is also how you accidentally get a third SaaS theme, a second database vendor, and a README that still says "Create Next App".
Keep a kit
This site copies the HashTag neo-brutalist kit: 2px black borders, hard shadows, Cabinet Grotesk plus Satoshi. Color is the only thing that swapped — here, black and white.
If the agent cannot see design-context.md, it will invent glassmorphism. Put the kit in the repo.
Keep a playbook
New products here start on better-auth + the Postgres that already comes with the CWP account, Node on a VPS, PM2, no Docker on day one. SQLite is the exception (a tool that must be one file and no server). That is not because the tools are fashionable. It is because the last three products already run that way.
Supabase is optional and last. Do not copy #Talk's auth into a blog because the blog is "in the family".
Review the boring paths
Agents love the hero. They skip 404s, health checks, and env examples. Those are the files that keep a VPS deploy from becoming a weekend.
The rule: if you would not merge a human PR without /api/health and .env.example, do not merge the agent either.