
The first Astro boilerplate built for AI agents, not just developers
Hey Product Hunt!
Jens here, creator of Stardrive.
I've been building websites since the very early 2000s. Some time ago, I fell in love with Astro and the idea of building websites without the huge overhead you get from Next.js, Nuxt, or similar. Just super fast and secure.
Then came AI agents and it made even more sense!
But here's the thing: AI agents are awesome, but they don't build perfect (technically speaking) websites out-of-the-box. You need to guide them, tell them what's important, care about tiny little features you might not even be aware of. Every project, the same hand-holding.
So I packaged all of that knowledge into an AI-readable boilerplate - so your agent gets it without you explaining it.
What is Stardrive?
It's an opinionated, batteries-included boilerplate for Astro. Not a theme - a full production-ready foundation. You run one command and you have a fast, modern, AI-ready website with blog, events, FAQ, docs, i18n, dark mode, SEO, and a Cloudflare Worker ready to deploy.
Why Astro?
Astro ships zero JavaScript by default. Perfect Lighthouse scores as the default, not the unreachable goal. If you care about performance (and your users do), there's no better foundation right now.
What makes it different?
Every boilerplate claims to be "fast" and "modern." Three things actually set Stardrive apart:
1. It's built for the AI age - and that's not a bullet point, it's the foundation. Self-documenting code, llms.txt, Schema.org, and WebMCP. Your AI coding agent can read and understand the entire codebase on day one. No reverse-engineering, no "where's the config?" loops. Other boilerplates treat AI as a feature you bolt on. Stardrive treats the AI agent as a first-class user of the codebase. The site is a document agents can read.
2. One config file rules everything. Colors, fonts, i18n, branding, nav - all in theme.config.ts. Make it yours before your coffee gets cold.
3. It's actually finished. Not a starter with a trillion TODOs. Not a demo that breaks when you customize it. Blog, events, FAQ, docs, pricing tables, multilingual support with locale-aware routing and hreflang - all pre-built with typed content collections. Write markdown, ship pages.
What's the catch?
It's free and MIT-licensed. The "catch" is that I'm opinionated - Stardrive makes choices so you don't have to. If you want to fight every default, it might frustrate you. If you want to skip to the part where you're building your actual product, it's built for you.
Who's behind it?
I'm Jens Kuerschner - CPTO by day, boilerplate plumber by night. Stardrive powers all of my own content websites, so it gets battle-tested in production, not just on a demo server. It's maintained and lives at github.com/peltmonger/stardrive.
How to get started, if you only have 5min?
Check the demo page (also documentation at the same time) at astro-stardrive.com and click around. You do not need to like the style (as you will change it anyway), but do you like the feeling?
If you know how to work with a CLI, run
npm create stardrive@latestand follow the onboarding. You can also use pnpm or yarn.
If you hate CLI, just tell your AI agent to clone and init Stardrive from the repo. That's literally what it's built for.
What's next?
Try it, fork it, break it, tell me what's missing. I'll be in the comments all day.