Launching today

TurboStack
The first AI-native SaaS starter kit (Next.js + Elysia)
6 followers
The first AI-native SaaS starter kit (Next.js + Elysia)
6 followers
Starter kits break when you use AI. TurboStack fixes this. It's the first AI-Native SaaS Boilerplate designed for Cursor & Windsurf. We include strictcursorrules context files so your AI follows the architecture, not hallucinations. ⚡ The Stack: Next.js 16+ (App Router) ElysiaJS (on Bun Runtime) Turborepo & Prisma Better Auth & Polar.sh Get End-to-End Type Safety and a clean Monorepo that scales. 🚀 Launch Offer: $100 OFF for the first 50 users!









I’ve been using AI coding assistants heavily, and the “architecture drift” problem is very real. You start with a clean setup, ask for a couple of features, and suddenly the boundaries are blurred, types are leaking, and the structure turns into spaghetti.
I love the idea of treating the starter not just as boilerplate, but as a blueprint with guardrails for AI. The .cursorrules and .windsurfrules approach makes so much sense — giving AI explicit architectural context instead of hoping it “guesses right.”
Also really interesting combo with Bun + Next.js + Elysia while keeping type safety intact.
Curious to see how this evolves. Congrats on the launch, Musa — this feels very aligned with how modern dev workflows are shifting 🚀
@eren_can1
Really appreciate this thoughtful feedback 🙏
What you mentioned — architecture drift — is exactly the problem Turbostack is designed to prevent.
Inside the project, there’s a dedicated /ai folder that contains multiple structured rule files. These don’t just define basic constraints — they explain the full project architecture, boundaries, design decisions, type flow, and how each feature should be implemented with AI.
The goal is simple:
Instead of letting AI “guess” how your system works, we teach it the system.
These rules document:
How features should be added
Where business logic belongs
How types must flow across layers
What not to touch
How to avoid breaking architectural boundaries
And this is just phase one. Beyond rule files, I’m working on more advanced, structured AI skill modules — moving from static guardrails to a smarter AI collaboration layer.
AI shouldn’t degrade your architecture.
It should help you protect and scale it 🚀
Thanks again for the support — this is exactly the shift modern workflows need.
Recipify
Hi, 👋
Congratulation with the launch! 🙌
It seems promising! ✨
I would love to see a live demo and a walkthrough video, when possible. 🙏
Good luck! ✌️
@hayatbiralem Hi 👋
Thank you so much for the kind words and support 🙌
We actually have a live demo available! You can check it out here:
👉 https://demo.turbostack.pro/
A full walkthrough video is also on the way — I’ll be sharing it very soon.
Really appreciate you taking the time to comment! ✨