What problem does it solve?
Provides a single, opinionated approach to diagnose and fix cross-package coordination problems in pnpm workspaces and Turborepo monorepos, eliminating back-and-forth about whether an issue is "build", "CI", or "dependency" related. It reduces wasted time by owning workspace-level decisions like shared configs, package boundaries, install scopes, caching, and catalog version resolution so teams don't re-explain architecture on every incident.
Core Features & Use Cases
- Workspace organization: Guidance for splitting apps vs packages, namespacing, and using a single root lockfile to preserve deterministic installs.
- Dependency management: Enforce workspace:* protocol, hoist shared devDependencies, use peer deps for frameworks, and adopt pnpm catalogs for centralized versions.
- Turborepo & caching: Configure dependsOn, outputs, env/globalEnv, persistent tasks, and remote cache to avoid silent cache misses and speed CI.
- Troubleshooting & gotchas: Practical checks for missing outputs, filtering behavior in pnpm, tsconfig references, tailwind v4 sources, and steps to debug cache mismatches.
- Use Case: Add a new package to packages/, run pnpm install, and let the skill validate workspace patterns, turbo.json outputs, and caching configuration to prevent build regressions.
Quick Start
Describe the interacting packages, the failing task or config (for example build, lint, or install), and ask the monorepo skill to diagnose workspace protocol, lockfile, turbo outputs, and caching implications.