What problem does it solve? Keeping package.json and pnpm-workspace.yaml consistent across pnpm 11, Node 24, ESLint 9 flat config, and Vitest 4 is error-prone: a missing allowBuilds entry breaks every install with ERR_PNPM_IGNORED_BUILDS, a pinned port in a dev script binds a port nothing publishes, and legacy .eslintrc* files silently mislead. This Skill encodes the authoritative contract and the reasoning behind it so edits to toolchain files stay correct. ## Core Features & Use Cases - Version pinning discipline: Keeps packageManager, engines.node, and .node-version in agreement so Corepack, the devcontainer, and CI resolve the same pnpm and Node. - Install and build-script governance: Explains pnpm 11 allowBuilds decisions (prisma, esbuild, unrs-resolver, @tailwindcss/oxide), confirmModulesPurge: false, and why legacy onlyBuiltDependencies keys are inert. - Script and lint contract: Defines exact dev, dev:web, dev:email, lint, typecheck, format, test, and prepare scripts, flat ESLint config requirements, and .mcp.json path rules. - Use Case: When adding a dependency or a new script to package.json, load this Skill to verify the change against the contract before committing, avoiding CI failures and hung installs. ## Quick Start Ask the assistant to review your package.json and pnpm-workspace.yaml changes against the toolchain contract before committing them.