01 · Web · MVP · Tool

Vite + React + Hono on Cloudflare Workers

A single-page app and a tiny edge API in one repo, with no framework magic between the agent and the browser.

Agent fit4/5 MVP · Ship it Reviewed 2026-10-04

The stack

Framework: Vite + React (SPA)
Runtime: Hono on Cloudflare Workers
Data: Cloudflare D1 or KV, or none at all
Hosting: Cloudflare Workers with static assets
Also: Tailwind CSS
TanStack Query for server state
Hono RPC client for end-to-end types

AGENTS.md + real projects on STACK IT FAST

Why agents do well here

4/5

Vite and React are the most common combination in training data; there are no framework conventions for the agent to get subtly wrong.
Hono's router is a few hundred lines the agent can read, and its RPC client gives the frontend the API's types for free.
A tool usually has one workflow, so the whole app fits in a couple of files the agent can hold at once.

Avoid at this tier

Server rendering; a tool does not need SEO and the SPA is simpler.
A database when local storage or a KV namespace will do.
A component library larger than the app.

How it fits together

A tool is one workflow done well. Put the UI in src/ and the API in worker/, share the request and response types through Hono’s client, and deploy both as a single Worker.

Folder layout

src/             main.tsx, App.tsx, features/<workflow>/
worker/          index.ts (Hono app), routes/, schema.ts
shared/          types exported from the Hono app
wrangler.jsonc

First five decisions

Lock these in before the agent writes the second feature. Each one removes a choice it would otherwise make differently every time.

01 SPA not SSR
02 Hono RPC for types
03 TanStack Query for every server call
04 D1 only if the data must outlive the browser
05 One wrangler deploy for everything

Also fits this cell

Same tier, same profile, a different stack. Pick one of these only for the reason given.

Rust + Axum + htmx + Askama (Server-Rendered Web App) (opens in a new tab)
The tool is forms and tables, you want a single binary, and you would rather have no JavaScript build at all.
Tauri 2 + React + Vite (Rust Desktop App) (opens in a new tab)
The tool has to run on the desktop: local files, offline by default, or OS integration a browser cannot give you.

When to move on

Stay here until the product forces the next tier. You are ready for Growth when:

Customers notice when something breaks
More than one person merges to main in a week
You have a billing provider and a support inbox
You need to know what changed and why, weeks later

Growth · Tool SvelteKit + Drizzle + Postgres Less code per screen than any React stack, with server loaders and form actions the agent can follow top to bottom. Next tier