note 07
Which tools to use
You do not need a shopping trip. You need one set of tools that can make the kind of thing you picked — usually a website a friend can open.
01
What “tools” means here
The languages, files, and host under your project. It is a toolbox, not a personality and not a team jersey. You pick it so the thing can exist — not because a thumbnail said it is what people use this year.
02
Pick the kind of thing first
Website, phone app, or a script that runs and quits? That choice mostly picks the tools for you. A website project will not become an App Store icon because you asked later. If you are not sure what kind you want, read the What kind of project note before this one.
03
A default that works
For a site: Next.js is fine. This site is Next.js, and Cursor already knows it. Vercel puts it online. A folder of HTML files is also fine if that is what you asked for. You do not have to defend either choice to anyone.
04
The agent will suggest fancier tools
Redis. GraphQL. A monorepo. Three new languages. “While we are here.” That is a trap. “No. Same tools. Only the button.” is a complete sentence. If it started a phone project and you wanted a page, say so and start over small.
05
Stay on one set until a friend can open it
Switching tools feels like progress. It is usually a new empty folder. Finish the small thing. Then you are allowed to get bored and try a different set on purpose.
You will hear that your stack is wrong. It is not wrong if a friend can click it. Fancy comes after something works.