Open-source exit ramp
Keep the speed. Lose the vibe-coding entropy.
Got something half-working in Lovable, Bolt, Replit, or a late-night prompt spiral? This starter gives you a sane codebase to move into before the whole thing turns into a haunted mess.
Hard-earned tips
A few rules people usually learn the annoying way
The whole point of this starter is to keep useful AI momentum without inheriting every bad habit that comes with shipping straight from vibes.
Rule 1
Do not push straight to main
Make a branch, open a PR, and merge with evidence. “It compiled on my machine” is not a release process, and “the AI said it looked good” is not review.
Rule 2
Run the checks before you trust the vibe
If Biome, Astro, the build, and the smoke checks have not run, you do not know what you have. You have a theory and a warm feeling.
Rule 3
Keep the browser on the safe side of the boundary
Client islands should talk to Astro endpoints, not directly to privileged services. The second you blur that line, the scaffold stops helping and starts becoming another cleanup project.
Want the full repo workflow? Read the
exit plan
and then the
documentation standards
.
AI guardrails
Tell the machine what repo it is in
Convention files that tell AI assistants your code style, design tokens, guard rules, and content schemas before they “help” you into a ditch.
Guard suite
Checks that say “absolutely not”
Secrets, bypass attempts, lint errors, lockfile drift, SOLID heuristics, and public smoke checks. The commit hook is the adult in the room.
Design tokens
No haunted CSS choices
Custom @theme tokens and DaisyUI semantic classes mean AI tools reach for the right class instead of improvising nonsense.
Doc superpowers
Documentation that still makes sense next Tuesday
A durable doc template plus a selective devlog standard so planning stays durable and implementation context stays findable.
This is the way out and forward
This starter is for people who do not want to throw away what AI helped them discover, but also do not want to spend the next six months living inside a repo that feels like an elaborate practical joke.
- Auth + BFF
- A clearly labeled demo surface showing what “browser talks to Astro, Astro talks to services” looks like in practice.
- SEO + LLMs
- OpenGraph, JSON-LD, sitemap, robots.txt, and llms.txt — so the public surface is structured, not improvised.
- Content
- Markdown stories, MDX site pages, and documentation standards — all typed with Zod schemas so copy changes do not quietly break the app.
- Quality
- Biome lint + format, strict TypeScript, Astro check, smoke coverage, and pnpm enforced. In other words: fewer surprises, fewer exorcisms.