Pnpm
pnpm fast package manager with content-addressable storage. Use for efficient installs.From its SKILL.md
npx -y skills add G1Joshi/Agent-Skills --skill pnpmAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 12 stars12 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.5 KB, 369 tokens by cl100k_base, as published. Nobody here has run it
pnpm
pnpm is fast and disk-efficient. It uses a Content Addressable Store and hard links to avoid duplicating packages. v9 (2025) adds Catalogs.
When to Use
- Disk Space: Saves GBs by storing one copy of
lodashglobally. - Speed: Installation is instant if packages are already in the store.
- Monorepos: Excellent workspace support with strict isolation.
Quick Start
# Enable via Corepack
corepack enable
corepack prepare pnpm@latest --activate
pnpm add next
Core Concepts
Content Addressable Store
~/.local/share/pnpm/store. All packages live here. Projects assume node_modules structure via symlinks.
Strict Resolution
Unlike npm/yarn (classic), pnpm does not flatten node_modules. You cannot access dependency-of-dependency unless you declare it.
Catalogs (v9)
Define version groups in pnpm-workspace.yaml. e.g. catalog:react-18 ensures all packages use exact same versions.
Best Practices (2025)
Do:
- Use CI Caching: pnpm is fast, but setup
pnpm-storecaching in GitHub Actions to make it instant. - Use
pnpm -r: Run commands recursively across the monorepo. - Use
only-allow: Addpreinstallscript to force team to use pnpm.
Don't:
- Don't shame hoist: If legacy tools break with symlinks, use
shamefully-hoist=truein.npmrcas a temporary fix.
References
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.