Skip to content
NEW v0.2.0 — Tracks, roadmaps and tiered stacks
STACK IT FIRST
Install the skills
Browse the site
01 · Web

Web

Sites and web apps, from a landing page an agent scaffolds in an hour to a multi-tenant product it maintains for years.
9 stacks 4 questions 3 skills

The web is where agents are strongest. The frameworks are old enough to be everywhere in training data, the ecosystem has converged on TypeScript, Tailwind and Postgres, and almost everything can be verified by loading a page. That also makes the web the easiest place to over-build: an agent will happily add a state manager, a design system and a microservice to a landing page if the codebase suggests it.

The roadmap below picks a tier first, because how much has to keep working while the agent changes things matters more than what the product does. It then picks a profile, because SEO sites, SaaS products and tools grow their complexity in different places and want different frameworks.

Stage 1

Where are you?

The tier is about how much has to keep working while an agent changes things, not about budget. Answer for the product as it is today, not as you hope it will be in a year.
  1. 01

    MVP · Ship it

    One deployable, free tiers, and a codebase small enough for an agent to read end to end.

    0 to a few hundred · You, plus an agent

    Open tier
  2. 02

    Growth · Charge for it

    Managed Postgres, real auth and billing, and tests the agent runs before every change.

    Hundreds to tens of thousands · Two to five engineers, each with agents

    Open tier
  3. 03

    Scale · Run it for many

    Typed service boundaries, an API contract as the source of truth, and boring infrastructure.

    Tens of thousands and up · Six or more engineers across teams

    Open tier
Stage 2

What are you building?

The profile decides where the complexity lives: in the pages, in the account model, or in one focused workflow. That in turn decides which framework an agent should be reasoning in.
Walk the roadmap
Tier SEO-driven content & search SaaS logged-in product Tool utility & internal
01 MVP Ship it Astro + Tailwind + Cloudflare Pages 5/5 Next.js + Drizzle + Supabase 5/5 Vite + React + Hono on Cloudflare Workers 4/5
02 Growth Charge for it Astro SSR + Postgres on Cloudflare 5/5 Next.js + Prisma + Postgres 5/5 SvelteKit + Drizzle + Postgres 4/5
03 Scale Run it for many Next.js + Postgres + edge caching 4/5 Next.js front, NestJS + Postgres + Redis back 4/5 Go + Postgres + React 4/5
Web rules

Five rules for this track.

On top of the nine cross-track principles.
  1. 01

    Server-first, islands second

    Render HTML on the server and hydrate only the parts that need state. An agent reasons about a page far better when most of it is plain markup and data-fetching code, not component trees with effects.

  2. 02

    File-based routing is a map the agent can read

    When the URL structure is the folder structure, the agent finds the right file on the first try. Avoid custom routers and dynamic route registries.

  3. 03

    One way to fetch data

    Pick server loaders, server components, or a typed client and use it everywhere. Mixed data-fetching styles are the most common source of agent-introduced bugs in web apps.

  4. 04

    Tailwind and a small component kit

    Utility classes keep styling local to the markup the agent is editing. A dozen well-named primitives beat a large component library it has to look up.

  5. 05

    Schema at the edge of every boundary

    Validate forms, route params and API responses with the same schema library. The agent can then trace a field from the database column to the input element without guessing.

The nine cross-track principles