Supercharging Bolt with "Cursor Rules"
Create auto-prompts for building with Bolt and other AI coding tools.
If you've been on X recently, you've probably seen more non-technical founders building their MVPs with AI tools like Bolt. But there's a catch—you still need to know what to ask for.
You may have heard of 'Cursor Rules'—configuration files that customise AI behaviour in the Cursor code editor based on your projects' needs. Developers have these tools to enhance their workflow, but what about the rest of us?
So I thought: what if non-technical founders had their own version of "rules" for AI coding tools?
Which is what I set out to build.
The knowledge gap problem
I love these new tools, but as a builder, I find myself writing "implement authentication with Supabase" or "set up Netlify deployment" over and over. And if you're not technical, how would you even know to specify these details?
You don’t know what you don’t know.
Should you use Firebase or Supabase? Tailwind or Bootstrap? Stripe or Paddle? And what configuration details matter for each?
What you'll learn
In this post, I'll walk you through:
How I built a Chrome extension that adds a sidebar of options to Bolt
My process of using Claude to help ideate a new tool
The challenges I faced and how I solved them (or didn't!)
How this meta-development approach can help non-technical founders bridge the knowledge gap
Ways you can use, modify, or be inspired by this tool for your own projects