Developer Onboarding

Clone the private Indigo-Trigger/sable repository. Use Node 22, npm, Git, and GitHub CLI. The Supabase and Vercel CLIs are needed for service-specific inspection and local API development. Open the repository root in your editor or coding agent. In Claude desktop's Code tab on macOS, open this root folder. The standalone Claude CLI is not a prerequisite for the npm commands below. Give the agent the developer-kit setup prompt when it is available to you. If the kit is unavailable, ask the agent to inspect the existing clone, run offline checks, and verify a development data target. The developer handles account sign-in and permission decisions; the agent runs setup and reports results without requesting credential values. For an optional repository configuration check, run npm run doctor:claude -- --desktop --offline; it does not assert desktop sign-in or tool permissions.

nvm use
npm run bootstrap
npm run doctor -- --offline
npm run check

bootstrap installs root, web, Supabase, and docs dependencies from committed lockfiles. It does not link a cloud project or retrieve secrets. doctor identifies missing local tools and can check service access when run without --offline. doctor:safety is an optional, read-only local target check; use npm run doctor:safety -- --connected before connected development. Basic code and tests need no cloud target. check is broader than the current CI jobs: it also runs the web production build and developer-tooling tests. Once Vercel local development access is ready, npm run dev:sable serves static pages and API routes together.

For focused work, use npm --prefix web test, npm --prefix web run build, npm --prefix supabase test, npm --prefix docs-site run build, or npm run env:check. The full developer guide explains worktrees, the command map, code locations, and access boundaries.

For a new task, fetch origin/main, inspect branch and working-tree state, then create a branch or isolated worktree from the fresh remote ref. Preserve active changes. Run focused checks and npm run check before opening a PR. Never share a worktree with another editing agent.

This standalone repository owns the production Git release path after the IND-12 cutover. A merge is release input; verify each deployed service's source commit before claiming it is live. The IND-12 cutover record is historical. Never deploy, promote, redeploy, or change a production alias directly from a workstation; never apply a production migration, Edge Function deploy, or Trigger deploy locally.