Set up

The right setup for your project

Answer 2 questions: what will people ask you about this project, and what does the product do? You get a step-by-step plan that your coding agent follows for you.

Find the right tier

Pick the lowest one on the list that is true. Each tier includes everything in the ones above it.

It is a spike or prototype that may not survive 2 monthsA landing page, a design exploration, something you may well delete.01Somebody outside the team will ask how far along it isA client, a PM, a board. Now it is worth measuring how much is built.02More than one app or team builds on the same design systemOr: 2 people could disagree about who approved a rule.03The product will outlast the current teamSomeone will take this over from you, so the reasons behind it need to be written down.04

And which of these are true of it?

These do not depend on the tier. Tick any that are true today, and the plan adds the steps that go with them.

A model’s output reaches a userAn answer, a summary, some generated copy. Normal checks cannot judge that, so you get tests that score the AI’s answers, whatever tier you are on.+ EvalsPeople sign in, and what they see depends on who they areThen there is data some people must not see. You get one place that says who can see and do what.+ AccessSome of it is paid forPlans, seats, limits, trials. If someone gets what they did not pay for, that is lost money. It also needs screens of its own, like hitting a limit.+ EntitlementsIt ships in more than one languageOr it definitely will. A phrase missing from one language file shows up as blank text for real users.+ Locales

Select a statement to see your setup plan.

Browse all 4 tiers

Tier 1 · Prototypes & landing pages

A light setup for work that may be thrown away. You get one file of project rules, a few basic checks, and a place to note decisions.

1 personWeeks6 steps

Tier 2 · A product with a fixed scope

Write down what the product must do, then measure how much of it is built. When someone else joins, or a second agent, the work still looks like one product.

1 to 3 peopleMonths21 steps

Tier 3 · Apps with a shared design system

Several apps share one design system, so shared parts must stay shared. Every rule notes who approved it, and each app gets its own progress number.

3 to 8 peopleA year or more28 steps

Tier 4 · Products built for the long term

The people will change before the product does. So the repo keeps a running log of what changed and why, and each work session leaves notes for the next one.

4+ peopleYears35 steps

Whatever the tier

Some things matter at any size, like signing in or payments. Each one adds its own steps to whichever tier you picked. To add one by hand, put ?with= and its id on the end of a plan address.