Skip to content
stacks

Find popular tech stacks. Have your agent build it.

Explore stacks for new projects and fragments to add to existing ones. See what developers are using and how often their projects pass verification. Pick a setup, then let Claude Code, Codex, or Cursor build from its brief and check the result with stacks verify.

Agent + stacks

Demo
You:

Build an expense tracker with a React dashboard and a Python API. Keep it local for now.

Agent:

I’ll look for a stack that covers the API, frontend, and tests.

●Bash(stacks list --json)
{ "entries": [
  { "id": "python-react",
    "name": "Python API + React SPA", … },
  …
] }

Output abbreviated

●Bash(stacks show python-react --json)
{ "id": "python-react",
  "name": "Python API + React SPA",
  "deps": { "backend": ["fastapi", "uvicorn", …],
    "frontend": ["react", "react-dom", …] }, … }

Output abbreviated

Agent:

Python + React looks like a good fit. It pairs a FastAPI backend with a React dashboard and a typed API client.

You:

What’s included in that stack, and what is it well set up for?

Agent:

Here’s what it gives us: • API: FastAPI, Pydantic validation, and uv for Python dependencies. • Frontend: React Router, TanStack Query, Tailwind, and shadcn/ui. • API client: generated from OpenAPI, so frontend calls follow the backend’s types. • Checks: Ruff, mypy, ESLint, TypeScript, pytest, Vitest, and Playwright. It’s well suited to dashboards and internal tools with a Python API. For your expense tracker, that gives us a place for the forms, API routes, and tests. Database and auth aren’t included by default; we can add those when needed. Shall I set up the local starter?

You:

Yes, use that stack. Set it up.

●Bash(stacks new python-react expense-tracker --sandbox --json)
{ "stack": "python-react", "preset": "sandbox",
  "brief": ".stacks/BRIEF.md",
  "written": ["AGENTS.md", "Makefile", …], … }

Output abbreviated

●Read(expense-tracker/.stacks/BRIEF.md)
Build the FastAPI backend and React frontend.
Generate the API client from OpenAPI.
Run stacks verify; fix failures without weakening checks.

Output abbreviated

Agent:

I’m following the brief to create the backend, frontend, and tests, including a working request from React to the API. I’ll generate the API client and run the checks before starting the servers.

●Write(expense-tracker/backend/app/main.py)
from fastapi import FastAPI
…
def create_app() -> FastAPI:
    app = FastAPI(lifespan=lifespan)
    app.include_router(router)
    return app
…

Output abbreviated

●Write(expense-tracker/frontend/app/root.tsx)
import { Outlet } from "react-router";
…
export default function App() {
  return <QueryClientProvider client={queryClient}>
    <Outlet />
  </QueryClientProvider>;
}

Output abbreviated

●Bash(cd expense-tracker && make install && make generate-api)
Dependencies installed with uv and bun.
OpenAPI spec and typed client generated.
●Bash(stacks verify)
✓ lint, typecheck, test
✓ api-contract, readme-filled
✓ API health and frontend respond
Verification passed
●Bash(make dev)background
API   http://localhost:8000
Web   http://localhost:5173
Agent:

The starter is running at localhost:5173, with the API on port 8000. Next, I can add the expense entry form and dashboard on this foundation.

Example agent conversation. Playback can be paused.

From an empty folder to a running dev server in minutes

On your own, a new project starts with research: which framework, which test runner, which config format is current. Then you walk the agent through bootstrapping and fix what it skipped. With a stack, the research is already done by people who built the same thing, and you can see what's in it before you start.

On your ownabout 4 hours
  • Research frameworks and libraries1 h 15 min
  • Pick versions and wire config45 min
  • Prompt the agent and correct it1 h 20 min
  • Add tests, lint, and CI40 min
With a stack8–10 minutes

Estimated agent setup to first green verify for Expo app + Hono API

060 minutes2.0 hours3.0 hours4.0 hours
Illustrative setup times: about 4 hours on your own, or 8–10 minutes with a stack, from agent setup to the first green verify.

Start with a stack that fits.

The stacks CLI

Keep the coding agent you already use. Give it a stack with the setup decisions made and a way to check its work.

  1. 01

    Find the right starting point

    Your agent reads the available stacks and explains which one fits. You make the call.

    stacks list --json
  2. 02

    Build from a shared brief

    Stacks writes the tools, layout, and checks into a project brief. Your agent follows it to build the app.

    stacks new <stack-id> <directory> --sandbox --json
  3. 03

    Check the result

    The agent runs the declared checks and fixes failures before handing the project back to you.

    stacks verify

Try the CLI

npx @steamfield/stacks list --json

The CLI never calls a model. It writes the brief and checks the result; your agent does the building.

What are you building?

Projects started per week
Jul 5Oct 25
Weekly data table

Published preset counts per UTC week. Suppressed counts are excluded, not zero.

Week endingStackProjects
2026-07-05Expo app + Hono API560
2026-07-05TypeScript HTTP API with Effect505
2026-07-05SvelteKit app on Node505
2026-07-05TypeScript CLI with Effect460
2026-07-05Go CLI90
2026-07-059 more stacks840
2026-07-12Expo app + Hono API905
2026-07-12TypeScript HTTP API with Effect850
2026-07-12SvelteKit app on Node740
2026-07-12TypeScript CLI with Effect695
2026-07-12Go CLI160
2026-07-129 more stacks1455
2026-07-19Expo app + Hono API1200
2026-07-19TypeScript HTTP API with Effect1105
2026-07-19SvelteKit app on Node1155
2026-07-19TypeScript CLI with Effect1080
2026-07-19Go CLI205
2026-07-199 more stacks2035
2026-07-26Expo app + Hono API1525
2026-07-26TypeScript HTTP API with Effect1400
2026-07-26SvelteKit app on Node1345
2026-07-26TypeScript CLI with Effect1245
2026-07-26Go CLI265
2026-07-269 more stacks2575
2026-08-02Expo app + Hono API1625
2026-08-02TypeScript HTTP API with Effect1440
2026-08-02SvelteKit app on Node1465
2026-08-02TypeScript CLI with Effect1440
2026-08-02Go CLI285
2026-08-029 more stacks2705
2026-08-09Expo app + Hono API1780
2026-08-09TypeScript HTTP API with Effect1740
2026-08-09SvelteKit app on Node1450
2026-08-09TypeScript CLI with Effect1500
2026-08-09Go CLI325
2026-08-099 more stacks2865
2026-08-16Expo app + Hono API1975
2026-08-16TypeScript HTTP API with Effect1840
2026-08-16SvelteKit app on Node1640
2026-08-16TypeScript CLI with Effect1600
2026-08-16Go CLI340
2026-08-169 more stacks3075
2026-08-23Expo app + Hono API2095
2026-08-23TypeScript HTTP API with Effect1945
2026-08-23SvelteKit app on Node1740
2026-08-23TypeScript CLI with Effect1730
2026-08-23Go CLI375
2026-08-239 more stacks3240
2026-08-30Expo app + Hono API2145
2026-08-30TypeScript HTTP API with Effect2075
2026-08-30SvelteKit app on Node1855
2026-08-30TypeScript CLI with Effect1860
2026-08-30Go CLI435
2026-08-309 more stacks3430
2026-09-06Expo app + Hono API2225
2026-09-06TypeScript HTTP API with Effect2060
2026-09-06SvelteKit app on Node1905
2026-09-06TypeScript CLI with Effect1990
2026-09-06Go CLI525
2026-09-069 more stacks3695
2026-09-13Expo app + Hono API2445
2026-09-13TypeScript HTTP API with Effect2260
2026-09-13SvelteKit app on Node2220
2026-09-13TypeScript CLI with Effect2090
2026-09-13Go CLI615
2026-09-139 more stacks3805
2026-09-20Expo app + Hono API2500
2026-09-20TypeScript HTTP API with Effect2335
2026-09-20SvelteKit app on Node2255
2026-09-20TypeScript CLI with Effect2085
2026-09-20Go CLI760
2026-09-209 more stacks4080
2026-09-27Expo app + Hono API2665
2026-09-27TypeScript HTTP API with Effect2370
2026-09-27SvelteKit app on Node2370
2026-09-27TypeScript CLI with Effect2085
2026-09-27Go CLI855
2026-09-279 more stacks4360
2026-10-04Expo app + Hono API2660
2026-10-04TypeScript HTTP API with Effect2580
2026-10-04SvelteKit app on Node2460
2026-10-04TypeScript CLI with Effect2445
2026-10-04Go CLI1105
2026-10-049 more stacks4475
2026-10-11Expo app + Hono API2900
2026-10-11TypeScript HTTP API with Effect2850
2026-10-11SvelteKit app on Node2510
2026-10-11TypeScript CLI with Effect2380
2026-10-11Go CLI1210
2026-10-119 more stacks4210
2026-10-18Expo app + Hono API3000
2026-10-18TypeScript HTTP API with Effect2890
2026-10-18SvelteKit app on Node2850
2026-10-18TypeScript CLI with Effect2525
2026-10-18Go CLI1400
2026-10-189 more stacks4115
2026-10-25Expo app + Hono API3175
2026-10-25TypeScript HTTP API with Effect2950
2026-10-25SvelteKit app on Node2595
2026-10-25TypeScript CLI with Effect2755
2026-10-25Go CLI1440
2026-10-259 more stacks3755
Most started, last 28 daysProjects
Expo app + Hono API11,210
TypeScript HTTP API with Effect10,530
SvelteKit app on Node9,740
TypeScript CLI with Effect9,325
Go CLI5,030
9 more stacks14,650
npx @steamfield/stacks new mobile-expo

Decide the setup once.

A stack records how a project should be built. Your agent turns that plan into a working project, with the tools and checks already chosen.

See the agent workflow
Tools and layout
The stack specifies the framework, project structure, and conventions. The agent follows the same plan each time you start a project.
Current dependencies
The agent resolves current versions and configures them together in your workspace. The stack describes the choices without pinning a snapshot of generated files.
A checked result
The stack lists the required checks. stacks verify runs them and reports what passed and what still needs work.

Popular and reliable are different lists

Projects started and successful verification tell you different things. Compare each stack's green rate with its interval and sample before choosing what to build.

All 14 stacks
06,44612,891 projects, 28 days
Dot: green rate. Bar: its 95% interval. Select a stack to inspect its evidence. Stacks without published counts or rates are omitted from the plot.
Outcome data table
StackProjects, 28 daysGreen rate
Expo app + Hono API11,21079% (78–80%, n=7,085)
TypeScript HTTP API with Effect10,530hidden: too few projects
SvelteKit app on Node9,740hidden: too few projects
TypeScript CLI with Effect9,325hidden: too few projects
Go CLI5,03067% (66–69%, n=3,430)
Python API + React SPA4,39086% (85–87%, n=2,750)
Go HTTP API3,94074% (73–76%, n=2,470)
Next.js app on Node3,615hidden: too few projects
Astro blog2,56569% (67–72%, n=1,625)
React Router on Cloudflare Workers4071% (54–83%, n=35)
Astro site + Effect API35hidden: too few projects
React Router with Effect30hidden: too few projects
FastAPI service (Python API)25hidden: too few projects
Tauri desktop app with React10hidden: too few projects

What it isn't

A template engine
Only files that never change between versions ship with a stack. Everything else is written down as decisions.
An agent
The CLI never calls a model and never runs a command from a stack. Your agent does the work.
A package manager
Stacks don’t pin versions. Picking current ones is the agent’s job, on purpose.
A migration tool
stacks add puts a fragment like CI or Postgres into an existing repo. It won’t restructure what’s there.

See what's in the registry before you install anything.

npx @steamfield/stacks list
Browse stacks

Computed 31 Oct 2026, through 30 Oct 2026. Numbers describe stacks projects, not the ecosystem.