monorepo-architect-skill

Managing package.json exports in a Node.js monorepo involves strictly defining public APIs by adding new export entries without removing existing ones. This ensures package boundaries remain stable and feature additions adhere to established architectural rules.

Running scoped builds and tests for a Yarn workspace requires using `yarn workspace` with `--scope` and executing tests via `npx vitest run`. This limits operations to affected packages rather than running tasks across the entire project root.

Avoiding the `cd` command in a monorepo prevents directory navigation errors by enforcing root-level operations. Instead of changing directories, you execute scripts and package management tasks using `yarn workspace` or the `--cwd` flag.

Using npm instead of Yarn is not supported in this architectural workflow. The monorepo maintenance rules strictly enforce Yarn exclusively for all package management, script execution, and build tasks to ensure environment consistency.

Enforcing architectural rules across multiple monorepo packages is achieved by governing Node.js code design and feature additions through strict command enforcement. This mandates scoped Yarn operations and manages package.json exports to prevent deviations from established patterns.