Picture by Writer
I used to hate vibe coding. I believed I may write higher code, design cleaner methods, and make extra considerate architectural selections alone. For a very long time, that was most likely true. Over time, issues modified. AI brokers improved considerably. MCP servers, Claude expertise, agent workflows, planning-first execution, and long-horizon coding instruments turned vibe coding from a gimmick right into a sensible solution to construct actual methods.
In some unspecified time in the future, I gave in. Since then, I’ve been utilizing Claude Code and OpenCode to construct methods that I’d usually take into account too complicated for fast iteration. These embody fee platforms, stablecoin wallets, ebook studying functions, and full-stack production-ready net methods. What shocked me was not simply the velocity, however the consistency of outcomes as soon as the fitting construction and instruments had been in place.
The true drawback most individuals face with vibe coding is just not writing code.
It’s choosing the proper tech stack.
Frontend, backend, authentication, databases, storage, e-mail, funds, and deployment all include numerous choices. And not using a clear stack, even sturdy AI coding brokers battle to make good selections. When an agent is given a well-defined and opinionated tech stack, it will possibly reliably construct an end-to-end utility with far much less friction.
That’s what this text focuses on.
I’ll stroll by way of my go-to tech stack for vibe coding trendy functions. That is the stack I reuse as a result of it really works. We’ll cowl how the items match collectively, what every device is chargeable for, and the way to go from zero to a production-ready system. I can even share a Claude Code pattern immediate and non-obligatory instruments that assist flip a working prototype right into a system prepared for manufacturing.
# My Tech Stack and Why This Stack Works
On this part, I’ll break down the precise tech stack I take advantage of for vibe coding and clarify why these instruments work so properly collectively when constructing actual functions.
The Stack
- Subsequent.js (App Router) -> Frontend and layouts
- shadcn/ui -> UI parts
- Server Actions + Routes -> Backend logic and webhooks
- Supabase -> Database, auth, storage
- Resend -> Transactional emails
- Stripe -> Funds and subscriptions
- Vercel -> Deployment and previews
This stack is deliberately easy. You should utilize the free tier of each platform listed right here, which makes it ideally suited if you’re beginning out. You’ll be able to deploy a full utility to Vercel totally free and join managed companies with out upfront value.
Why This Stack Scales With out Getting Messy
Two Subsequent.js primitives do many of the heavy lifting because the app grows:
- Server Actions deal with kind submissions and server-side mutations. They maintain knowledge writes near the UI and take away loads of boilerplate that usually seems early.
- Route Handlers deal with webhooks, well being checks, and customized endpoints. This offers you a clear place for exterior methods to speak to your app with out polluting your UI logic.
Supabase provides you database, authentication, and storage with a safety mannequin that lives near the information. When you allow Row Stage Safety early, authorization stays constant because the system grows and also you keep away from painful migrations later.
Resend retains transactional e-mail easy and environment-driven.
Stripe Checkout paired with webhooks provides you a dependable solution to convert funds into actual entitlements as a substitute of scattered function flags.
Vercel retains preview and manufacturing deployments aligned, so you might be testing in actual environments from day one.
This stack works properly for vibe coding as a result of it’s opinionated, predictable, and simple for an AI coding agent to cause about. As soon as the boundaries are clear, the system nearly builds itself.
# Construct Plan from Zero to a Paid MVP
This construct plan is designed for vibe coding with actual instruments. The aim is to get a production-ready skeleton first, then add functionality in small phases with out breaking earlier selections. Every part maps on to the stack you might be utilizing, so an AI coding agent can comply with it finish to finish.
Part 1: MVP Basis
Construct the total product loop with minimal scope.
- Arrange Subsequent.js (App Router) challenge with Vercel deployment
- Dashboard shell and navigation utilizing shadcn/ui
- Authentication flows utilizing Supabase Auth (signup, login, reset)
- One core user-owned desk in Supabase Postgres
- CRUD screens powered by Subsequent.js Server Actions
- Preview deployments on each change by way of Vercel
On the finish of this part, you have already got a usable app operating in manufacturing, even when the function set is small.
Part 2: Knowledge Security and Entry Management
Lock down person knowledge earlier than including extra options.
- Allow Row Stage Safety on user-owned tables in Supabase
- Outline learn and write insurance policies based mostly on possession
- Use constant patterns like owner_id, created_at, updated_at
- Validate entry guidelines by way of actual UI flows, not simply SQL
This part prevents future rewrites and retains safety aligned with how the app truly works.
Part 3: E mail and Storage
Add belief and file dealing with.
- Transactional emails by way of Resend (welcome, verification, resets)
- Non-public storage buckets utilizing Supabase Storage
- Add flows that respect the identical possession guidelines as your database
- Signed URLs or managed entry based mostly on person id
That is the place the product begins to really feel full as a substitute of experimental.
Part 4: Billing and Entitlements
Flip utilization into income.
- Create Stripe Checkout periods and redirect customers
- Deal with Stripe webhooks with Subsequent.js Route Handlers
- Retailer subscription or buy state in Supabase
- Gate premium options based mostly on saved entitlements
- Make webhook dealing with idempotent utilizing processed occasion IDs
By the tip of this part, you’ve gotten a paid MVP that may scale with out altering core structure.
# Claude Code Starter Immediate
You’ll be able to change “E book Store + Reader MVP” with your personal concept utilizing the identical Claude Code immediate.
Construct a **E book Store + Reader MVP** utilizing this stack:
- Subsequent.js App Router
- shadcn/ui
- Supabase (Postgres, Auth, Storage)
- Resend
- Stripe (Checkout + webhooks)
- Vercel
## Purpose
Ship a production-ready E book Store and Reader with paid entry.
## Construct
- Public pages: touchdown, pricing, ebook record
- Auth: enroll, sign up, reset password
- Protected app: reader dashboard
## Knowledge
- `books`, `chapters`
- Row Stage Safety so customers entry solely their very own knowledge
## Options
- CRUD by way of Server Actions
- Reader view with progress monitoring
- Non-public storage for ebook property
- Welcome e-mail
- Stripe Checkout + webhook-based entitlements
## Output
- Clear app construction
- Minimal dependencies
- README with setup, env vars, migrations, Stripe, and Vercel steps
- Handbook verification guidelines per function
All you might want to do is swap Claude Code to Plan Mode, paste the immediate, and alter the thought or regulate the scope based mostly in your wants.
When you begin, Claude will plan the system first after which start constructing step-by-step with out friction. It can additionally information you thru organising required companies, creating accounts on third-party platforms, and producing API keys the place wanted.
This makes it straightforward to go from an concept to a working utility with out getting caught on setup or selections.
# Optionally available Instruments
These instruments are usually not required to ship the primary model, however they aid you take a look at, monitor, and harden the appliance because it grows in actual utilization.
| Class | Software choices | What it helps with | When so as to add it |
|---|---|---|---|
| Unit checks | Vitest | Quick checks for utilities and server logic | As soon as core CRUD works |
| Part checks | React Testing Library | Catch UI regressions in kinds and states | After the dashboard stabilizes |
| Finish-to-end checks | Playwright | Full person flows: signup → create → pay | Earlier than including extra options |
| Error monitoring | Sentry | Stack traces, launch well being, alerting | As quickly as actual customers arrive |
| Logs | Axiom or Logtail | Searchable request logs, webhook debugging | When webhooks and billing go stay |
| Efficiency checks | Lighthouse (CI) | Catch sluggish pages and outsized bundles | Earlier than advertising and marketing launches |
| Schema and migrations | Drizzle Package or SQL migrations | Repeatable schema modifications | The second you’ve gotten 2+ tables |
| Background jobs | Inngest or Set off.dev | Async work: emails, exports, cleanup | When workflows increase past requests |
| Price limiting | Upstash Redis (or related) | Defend auth endpoints and webhooks | When site visitors turns into actual |
| Product analytics | PostHog (or related) | Funnels, activation, function utilization | After you understand what you measure |
# Remaining Ideas
Trendy growth and engineering instruments are evolving quick. Most of them at the moment are designed with AI integration in thoughts, providing good documentation, APIs, and MCP-style entry so AI brokers can work with them immediately and construct software program sooner than ever.
In case you are an information scientist who has by no means touched net growth, or an entire newbie who needs to construct one thing actual or launch a startup, I strongly advocate beginning with this tech stack. It requires minimal setup and allows you to deploy a working utility nearly instantly.
It took me practically three months to check and evaluate instruments earlier than deciding on this stack. Beginning right here will prevent that point.
If you would like extra flexibility later, you possibly can break up issues out. For instance, use Neon for the database, Clerk for authentication, and maintain all the things else the identical. Spreading duties throughout instruments makes it simpler to exchange one half with out breaking the remaining as your system grows.
Begin easy, ship early, and evolve solely when you might want to.
Abid Ali Awan (@1abidaliawan) is a licensed knowledge scientist skilled who loves constructing machine studying fashions. Presently, he’s specializing in content material creation and writing technical blogs on machine studying and knowledge science applied sciences. Abid holds a Grasp’s diploma in know-how administration and a bachelor’s diploma in telecommunication engineering. His imaginative and prescient is to construct an AI product utilizing a graph neural community for college kids combating psychological sickness.
