pnpm — Claude Code skill: Node.js package manager
Skill for working with pnpm, a Node.js package manager with strict dependency resolution. Use it when your project relies on workspaces, version catalogs, patches, or dependency overrides.
npx skills add antfu/skills --skill pnpm -a claude-codeWhat pnpm does
pnpm is a fast, disk-efficient package manager that uses a content-addressable store to deduplicate dependencies across projects. It prevents phantom dependencies by default and scales from single projects to monorepos via pnpm-workspace.yaml.
Version 12 is a Rust rewrite of v11 that keeps commands, flags, and lockfile format identical. Configuration lives in pnpm-workspace.yaml with camelCase keys; .npmrc is reserved for registry credentials only. The skill covers dependency installation and management, version catalogs, patches, overrides, the global virtual store, task orchestration across monorepo packages, and experimental Python and Cargo support alongside npm.
In CI, always run pnpm ci with --frozen-lockfile to prevent unexpected updates. When migrating from npm or Yarn, watch for phantom dependencies—pnpm will reject them by default.
What it helps with
- set up a package manager for a monorepo
- centralize dependency versions using catalogs
- patch third-party packages without forking
- speed up CI installs with store caching
- orchestrate build and test tasks across monorepo packages
Example prompts for the agent
- Configure pnpm for a monorepo with shared version catalog
- Apply a patch to a package using pnpm
- Install dependencies in CI and cache the pnpm store
How to install pnpm
1Skills CLI (Vercel)
npx skills add antfu/skills --skill pnpm -a claude-code2Manually: put the files in place
~/.claude/skills/pnpm/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/pnpm/
1Skills CLI (Vercel)
npx skills add antfu/skills --skill pnpm -a codex2Manually: put the files in place
.agents/skills/pnpm/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add antfu/skills --skill pnpm -a cursor2Manually: put the files in place
.cursor/skills/pnpm/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install antfu/skills pnpm2Manually: put the files in place
.github/skills/pnpm/SKILL.md1Skills CLI (Vercel)
npx skills add antfu/skills --skill pnpm -a gemini-cli2Platform CLI
gemini skills install https://github.com/antfu/skills --path skills/pnpmManually: put the files in place
.devin/skills/pnpm/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add antfu/skills --skill pnpm -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set8
The whole set →Similar
Questions about pnpm
How do I install the pnpm skill in Claude Code?
Run npx skills add antfu/skills --skill pnpm -a claude-code twice. The skill will appear at ~/.claude/skills/pnpm/SKILL.md.
What does the pnpm skill do?
It gives your agent knowledge of pnpm commands, configuration via pnpm-workspace.yaml, workspaces, version catalogs, patches, overrides, and task orchestration.
How does pnpm differ from npm?
pnpm uses a content-addressable store (saves disk space), forbids phantom dependencies, and configures through pnpm-workspace.yaml instead of package.json. For CI, use pnpm ci with --frozen-lockfile.
Source text
SKILL.md · MIT
--- name: pnpm description: Node.js package manager with strict dependency resolution. Use when running pnpm specific commands, configuring workspaces via pnpm-workspace.yaml, or managing dependencies with catalogs, patches, overrides, config dependencies, or the global virtual store. metadata: author: Anthony Fu version: "2026.9.25" source: Generated from https://github.com/pnpm/pnpm, scripts located at https://github.com/antfu/skills --- pnpm is a fast, disk space efficient package manager. It uses a content-addressable store to deduplicate packages across all projects on a machine, and enforces strict dependency resolution by default, preventing phantom dependencies. **pnpm v12 is a Rust rewrite** of v11: stable, and keeps v11's commands, flags, settings, and lockfile format — so most guidance here applies to both. A handful of v12 behaviors differ (git deps resolve via HTTPS, project-aware global bins, other package managers, `packageImportMethod: auto` hardlinks first on Linux, `--resolution-only` removed) — see best-practices-migration. **Configuration model (important):** pnpm settings live in `pnpm-workspace.yaml` (and the global `config.yaml`) using **camelCase** keys. `.npmrc` is used **only** for authentication/registry credentials, and the `pnpm` field of `package.json` is no longer read. When working in a pnpm project, check `pnpm-workspace.yaml` for settings/workspace structure and `.npmrc` only for auth. Always use `--frozen-lockfile` (or `pnpm ci`) in CI. > The skill is based on pnpm 12.x, generated at 2026-09-25. It covers v11+v12 behavior (config split, isolated global packages, `allowBuilds`, `pmOnFail`, global virtual store, native release management, workspace task orchestration, and experimental Python/Cargo support) where current docs describe them. ## Core | Topic | Description | Reference | |-------|-------------|-----------| | CLI Commands | install/add/remove/update, run, dlx/pnx, workspace, runtime, publishing (version, view, sbom, stage) | [core-cli](references/core-cli.md) | | Configuration | pnpm-workspace.yaml settings (camelCase), global config.yaml, packageConfigs, .npmrc auth | [core-config](references/core-config.md) | | Workspaces | Monorepo support: filtering, workspace protocol, shared lockfile, packageConfigs | [core-workspaces](references/core-workspaces.md) | | Store | Content-addressable store, virtual store, node linker modes, frozen/read-only store | [core-store](references/core-store.md) | ## Features | Topic | Description | Reference | |-------|-------------|-----------| | Catalogs | Centralized dependency versions; catalogMode, catalog: in overrides | [features-catalogs](references/features-catalogs.md) | | Overrides | Force versions (incl. transitive & peer deps); packageExtensions | [features-overrides](references/features-overrides.md) | | Patches | Modify third-party packages; patchedDependencies in pnpm-workspace.yaml | [features-patches](references/features-patches.md) | | Aliases | Install under custom names (npm:) and registry aliases (namedRegistries) | [features-aliases](references/features-aliases.md) | | Hooks | .pnpmfile.mjs hooks (readPackage, updateConfig, beforePacking), finders, resolvers/fetchers | [features-hooks](references/features-hooks.md) | | Peer Dependencies | Auto-install, strict mode, rules, dedupePeers, peers check | [features-peer-deps](references/features-peer-deps.md) | | Config Dependencies | Share hooks/settings/catalogs/patches across repos via configDependencies | [features-config-dependencies](references/features-config-dependencies.md) | | Global Virtual Store & Shims | Shared node_modules, git-worktree multi-agent setups, isolated global packages, project-aware bins, other package managers | [features-global-virtual-store](references/features-global-virtual-store.md) | | Supply-Chain Security | Build approval (allowBuilds), minimumReleaseAge, trustPolicy, lockfile integrity | [features-supply-chain-security](references/features-supply-chain-security.md) | | Task Orchestration | Cross-project task graphs (tasks/dependsOn), concurrency groups, priority, pnpm pipeline | [features-task-orchestration](references/features-task-orchestration.md) | | Release Management | Native versioning: pnpm change/version -r/lane, lanes, epics, fixed groups | [features-versioning](references/features-versioning.md) | | Multi-Ecosystem | Python (pypi:) and Cargo (crate:) dependencies alongside npm (experimental) | [features-multi-ecosystem](references/features-multi-ecosystem.md) | ## Best Practices | Topic | Description | Reference | |-------|-------------|-----------| | CI/CD Setup | GitHub Actions, GitLab, Docker, pnpm ci, store caching, frozen lockfiles | [best-practices-ci](references/best-practices-ci.md) | | Migration | npm/Yarn → pnpm, phantom deps, and pnpm v10 → v11 → v12 upgrade notes | [best-practices-migration](references/best-practices-migration.md) | | Performance | Install optimizations, allowBuilds, global virtual store, workspace parallelization | [best-practices-performance](references/best-practices-performance.md) |
© Anthony Fu · MIT · antfu/skills