Local setup

Use the repository’s declared Node version (.nvmrc), package manager/lockfile, and documented scripts. Install dependencies with the lockfile workflow, then run the project’s typecheck/test/build commands before claiming a change is ready.

Do not copy production credentials into local files, terminal history, screenshots, or docs. Use approved local/test configuration. If the VPS-first guard applies to your machine/repo role, use the prescribed VPS command and stop if it denies the run; do not bypass it.

Before schema work, inspect current migration history and use a local Supabase environment for validation. Production database actions and provider changes require their own authorization.

Purpose and prerequisites

This is a safe developer setup procedure, not a production-bootstrap guide. You need approved repository access, the Node version declared in .nvmrc, npm, and authorized local Supabase tooling. Never copy a production secret into a local file, shell history, screenshot, or docs page.

Setup procedure

1. Start from the intended Git ref and inspect git status; preserve unrelated work.
2. Read .nvmrc, use that Node version, and install dependencies through the lockfile workflow declared by package.json.
3. Inspect available scripts with npm run; run the documented typecheck/test/build before claiming a code path is ready.
4. For schema work, inspect supabase/config.toml, migrations, and local history before rebuilding/testing an approved local environment.
5. For this handbook, use npm run docs:dev, npm run docs:build, and npm run docs:check from repository scripts.

Expected result and recovery

A reproducible local check is not proof of deployment, provider delivery, or production schema state. If a VPS-first guard denies a command, report its prescribed command and stop; do not bypass it. Treat migration mismatch with a linked environment as a release investigation, never a reason for a broad production push.