Monorepo (pnpm / Turborepo / Nx)

Spine's monorepo template captures the project-level contract that agents usually miss at the repo root: package boundaries, app ownership, build graph rules, affected-only CI, release constraints, and when to compile against a specific workspace instead of the root.

Who this template is for

Teams consolidating apps and packages under one repo, platform teams standardising shared packages, and agencies with repeatable client stacks split across apps and packages.

Get started

$ npm install -g project-spine@beta
$ spine init --template monorepo
$ spine compile --brief ./brief.md --repo . --template monorepo
✓ wrote spine.json
✓ wrote AGENTS.md, CLAUDE.md, copilot-instructions.md, project-spine.mdc
✓ wrote scaffold-plan, qa-guardrails, sprint-1-backlog

What spine compile emits

• Workspace layout contract for apps/* and packages/*
• BuildGraph guidance for cached, affected-only checks
• ChangeGate rules for package boundaries and dependency direction
• QA guardrails covering root vs workspace test/typecheck commands
• Agent instructions warning when framework detection at the root is low-confidence

Good fit if

• pnpm workspace, Turborepo, or Nx repos with multiple deployable apps
• Shared UI/domain packages consumed by several frontends
• Teams that need agents to respect package boundaries instead of editing everywhere

Pairs well with

• api-serviceHealth checks, typed contracts, error envelopes, and operational guardrails from day one.
• app-dashboardRole-aware dashboard context, compiled. No more reinventing the auth shell.
• design-systemTokens, primitives, Storybook, docs — compiled into rules every consumer repo inherits.