pnpm-workspace

Configure pnpm workspaces with filtering, catalogs, and shared configs for monorepos.

Updated Sep 5, 2026
One-click install
npx skills add https://github.com/pohlai88/afenda-xforge-v5 --skill pnpm-workspace-pohlai88
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pnpm-workspace
Source: https://github.com/pohlai88/afenda-xforge-v5/tree/main/.agents/skills/pnpm-workspace
Command: npx skills add https://github.com/pohlai88/afenda-xforge-v5 --skill pnpm-workspace-pohlai88

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Managing dependencies and running commands across multi-package repositories becomes error-prone without a consistent workspace setup. This Skill provides guidance for pnpm workspaces so packages link correctly, dependency versions stay consistent, and commands target exactly the right packages. ## Core Features & Use Cases - Workspace Setup: Define packages in pnpm-workspace.yaml, link local packages with the workspace: protocol, and centralize dependency versions with default and named catalogs. - Package Filtering: Target commands by package name, dependency graph, directory, or git changes using the --filter flag, including exclusion and combined selectors. - Shared Configs & Integration: Share TypeScript, ESLint, and Prettier configs across packages, and coordinate pnpm with Turborepo and Changesets for builds, releases, and Docker deployment. - Use Case: When adding a feature to one app in a monorepo, run pnpm --filter "web..." build to build the app and its dependencies in topological order without touching unrelated packages. ## Quick Start Ask the AI to set up a pnpm workspace with two packages linked via the workspace protocol and a shared catalog for React versions.

Frequently Asked Questions about pnpm-workspace

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
When should I not use pnpm workspaces?▼

Avoid pnpm workspaces for single-package projects or projects already committed to npm or yarn workspaces without migration. They also do not fit projects that require floating, per-package dependency versions rather than a shared lockfile.