skills/antfu/pnpm/SKILL.md
Node.js package manager with strict dependency resolution. Use when running pnpm specific commands, configuring workspaces, or managing dependencies with catalogs, patches, or overrides.
npx skillsauth add aiskillstore/marketplace pnpmInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
pnpm is a fast, disk space efficient package manager. It uses a content-addressable store to deduplicate packages across all projects on a machine, saving significant disk space. pnpm enforces strict dependency resolution by default, preventing phantom dependencies. Configuration should preferably be placed in pnpm-workspace.yaml for pnpm-specific settings.
Important: When working with pnpm projects, agents should check for pnpm-workspace.yaml and .npmrc files to understand workspace structure and configuration. Always use --frozen-lockfile in CI environments.
The skill is based on pnpm 10.x, generated at 2026-01-28.
| Topic | Description | Reference | |-------|-------------|-----------| | CLI Commands | Install, add, remove, update, run, exec, dlx, and workspace commands | core-cli | | Configuration | pnpm-workspace.yaml, .npmrc settings, and package.json fields | core-config | | Workspaces | Monorepo support with filtering, workspace protocol, and shared lockfile | core-workspaces | | Store | Content-addressable storage, hard links, and disk efficiency | core-store |
| Topic | Description | Reference | |-------|-------------|-----------| | Catalogs | Centralized dependency version management for workspaces | features-catalogs | | Overrides | Force specific versions of dependencies including transitive | features-overrides | | Patches | Modify third-party packages with custom fixes | features-patches | | Aliases | Install packages under custom names using npm: protocol | features-aliases | | Hooks | Customize resolution with .pnpmfile.cjs hooks | features-hooks | | Peer Dependencies | Auto-install, strict mode, and dependency rules | features-peer-deps |
| Topic | Description | Reference | |-------|-------------|-----------| | CI/CD Setup | GitHub Actions, GitLab CI, Docker, and caching strategies | best-practices-ci | | Migration | Migrating from npm/Yarn, handling phantom deps, monorepo migration | best-practices-migration | | Performance | Install optimizations, store caching, workspace parallelization | best-practices-performance |
development
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
tools
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
testing
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
tools
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.