For teams building on Node
The Node stack,
already decided.
A ready-to-run web application foundation - Next.js + Fastify - with login, tests and tooling already chosen, explained, and re-tested automatically every week. The weeks a project burns on setup debates go into the product instead. Start shipping.
start a new project on repositorystandards.com with the node stack
Say it to your coding agent. It reads the standard, interviews you for what it cannot work out, and adapts the picks to what you are building - rather than handing you a folder to reconcile. Already have a repository? Say take this repo onto repositorystandards.com with the node stack instead.
What is this?
Node Best Practices is the technology package of Repository Standards: a maintained set of choices for building web applications on Node - with a working application to start from, and guides for bringing projects you already run on board. Four things, concretely:
A working starter
A complete Next.js + Fastify application - login, tests, CI - that the agent adapts into your project. Not a tutorial. A CI run boots it.
See what is insideThe decisions, explained
Every technology choice - package manager, linting, testing, auth - documented: what we picked, why, and what to use instead when it does not fit your case.
Read the decisionsA guide for existing projects
Already on npm, ESLint or Jest? Step-by-step migration notes for every piece - staged so your build never breaks along the way.
Open the migration guideAutomatic verification
A contract file your tooling reads. One check tells you - and your CI - that the project still follows the standard. No opinions, a number.
View the contractPart of Repository Standards
Repository Standards is the guide for how a repository is run - documentation, decisions, specifications and verification, independent of technology. This package adds the Node layer on top of it. Use the standard to organize any repository; add this package when the repository runs on Node. Together: one setup, one set of rules, one check that both still hold.
developers
Sign-up to dashboard works in minutes - one command, then pnpm dev. Tests and CI come with it; you build features, not scaffolding.
architects & tech leads
Every choice ships with its reasoning and its alternative. Disagreeing is one recorded note, not another meeting - and one number tells you a repo is still on the road.
product - PM & PO
The sprints your team would burn on setup debates go into the product instead - and every technical decision is written down in plain words, so you can read the why without booking a developer.