A stack is not a list of logos. It is an order of operations.

The tools below are ordinary — you have heard of all of them. What makes this a stack is the sequence: each one hands the next a thing it can actually use, so you never stop to translate between steps.

Here is the run, start to finish.

1. Mobbin — start from patterns, not a blank canvas

The slowest part of a new site is the first hour, staring at nothing.

Mobbin is a library of real product screens, so you start by looking at how ten teams already solved your problem. You are not copying. You are skipping the part where you reinvent a pricing page badly.

Pick three references before you open anything else. It changes what you ask for later.

2. Claude Code — get the first draft out of your head

Describe the page in plain words and let it produce something to react to.

The first output will not be right, and that is the point. Reacting to a wrong draft is far faster than generating a right one from nothing — you know immediately what bothers you, which you rarely know in advance.

Use it to get to a position you can argue with.

3. Figma — make the decisions that are expensive to change

Spacing, hierarchy, type scale and the states nobody thinks about — empty, loading, error, too-long name.

These are cheap to settle in Figma and costly to discover in code. This is the step people skip when the AI draft looks good enough, and the step they pay for two weeks later.

4. Cursor — turn decisions into components

Now the design is settled, the build is mostly transcription, which is exactly what an AI editor is good at.

Work component by component rather than page by page. A page prompt gives you a page you have to unpick; a component prompt gives you something you can name, reuse and delete.

5. Astro — because most sites are content

Astro ships zero JavaScript by default and lets you opt into interactivity per component.

That is the right default for the thing you are probably building:

  • Marketing sites and landing pages
  • Blogs, docs and changelogs
  • Portfolios and agency sites
  • Anything where search traffic matters more than app-like interaction

If the page is mostly words and pictures, a framework that sends a runtime to every visitor is a tax you are paying for nothing.

6. Sanity — so you stop being the CMS

The moment a non-developer wants to change a headline, you either give them a way to do it or you become the bottleneck forever.

Sanity gives you a typed content model and an editor people will actually use. Model the content properly once — sections, not a soup of free text — and the site stops needing you for copy changes.

7. Cloudflare — ship it

A built Astro site is static files. Cloudflare serves them from the edge, handles the domain and the certificate, and does not charge you for traffic you were hoping to get.

Deployment should be the least interesting part of the week. With this stack, it is.

The order is the point

Swap any single tool and the stack still works. Swap the order and it does not.

Design before you build. Settle content structure before you style it. Deploy from day one rather than at the end, so shipping is never an event.

That sequence is the thing worth copying.

Is Astro a good choice in 2026?
Yes, for content-led sites. Astro ships no JavaScript by default and lets you add interactive components only where they are needed, which keeps marketing sites, blogs and documentation fast without extra work. For an app with heavy client-side state, reach for Next.js instead.
Do I need Figma if AI can generate the UI?
Yes. AI is good at producing a plausible first draft and poor at deciding spacing, hierarchy and edge-case states. Those decisions are cheap to make in Figma and expensive to discover in code, so the design step saves more time than it costs.
Why Sanity rather than a Markdown folder?
Markdown is fine while you are the only editor. The moment someone else needs to change copy, a typed content model with a real editor stops you being the bottleneck for every wording change.
Can I use Vercel instead of Cloudflare?
Yes. A built Astro site is static files, so any static host works. Cloudflare is the pick here for edge delivery and bandwidth that does not punish you for traffic.