monorepo-workspace-governance

What problem does it solve? In an npm workspaces monorepo, dependencies often get installed to the wrong package.json, root scripts get renamed and break guardrail checks, and code leaks across workspace boundaries. This Skill defines and enforces the ownership rules that keep the monorepo structure consistent. ## Core Features & Use Cases - Dependency Ownership Enforcement: Ensures each dependency is installed to the workspace that uses it (via npm install <pkg> -w @joyjoin/<workspace>), never to the orchestration-only root package.json. - Guardrail Compliance: Keeps required root scripts (check, check:clients, check:server, check:full, set-admin) aligned with scripts/check/check-guardrails.mjs, plus secret/env and legacy-identifier rules. - tsconfig Normalization: Maintains the solution-style root tsconfig with per-workspace references extending tsconfig.base.json. - Use Case: When asked to "add date-fns to the server", the Skill scopes the install to @joyjoin/server, verifies the root package.json stays clean, and runs npm run guardrails to confirm compliance. ## Quick Start Ask the assistant to add a dependency to a specific workspace or fix a failing guardrails check, and it will apply the workspace ownership rules and verify with npm run guardrails.