Workflows

A local setup that does not fight you

The small decisions that make a project pleasant to work on: one command to start, one place for secrets, and checks that run on save.

Updated16 Sept 2026

A good setup removes small frictions that add up to hours. These are the ones that matter most.

One command to start#

Someone new should be able to clone the repo and run one command. If that takes a page of instructions, that page belongs in a script.

bash

git clone <your-repo>cd <your-repo>pnpm installpnpm dev

Install the tools once. Pick your system and the guide remembers it.

bash

winget install OpenJS.NodeJS.LTSnpm install -g pnpm

bash

brew install nodenpm install -g pnpm

bash

sudo apt install nodejs npmnpm install -g pnpm

Then install and start the project with your package manager:

bash

pnpm installpnpm dev

bash

npm installnpm run dev

Keep a .env.example with every variable and what it is for. Never commit the real .env.local.

Run the formatter and type checker automatically. Reviews should be about ideas, not about semicolons.

These guides stay current because readers tell us what is off. One tap is plenty.