メニュー
Use for pnpm dependency management, workspace configuration, catalogs, patches, overrides, or package-resolution problems. Do not use for routine `pnpm test`, `pnpm build`, `pnpm lint`, or `pnpm type-check` commands.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Choose an appropriate test level and use red-green-refactor when test-first work is requested. Use when the user asks for TDD, red-green-refactor, test-first development, integration tests, or help deciding coverage. Prefer integration tests for meaningful behavior across boundaries, unit tests for nontrivial isolated logic requiring little or no mocking, and no new test for trivial behavior adequately covered by types or existing tests.
Expert guidance for Effect-TS architecture, typed error design, Layers, services, concurrency, resource management, and meaningful Effect refactoring. Use when the user explicitly asks for Effect patterns or the task materially changes Effect architecture. Do not use merely because a file imports Effect or a repository uses Effect.
Prepare, publish, and maintain GitHub pull requests with template-faithful descriptions, fewer pushes, and CI follow-through. Use when creating, updating, pushing, or checking a GitHub PR, or when the user asks to open, ship, publish, or polish a PR.
Review software implementation plans before execution. Use when a programming plan, technical approach, implementation checklist, or execution brief needs approval, critique, validation, or readiness review before an execution agent starts work.
Selectively stress-test a plan or design by asking only high-leverage questions that could materially change the outcome. Use when user wants to be grilled, stress-test a plan, pressure-test a design, or mentions "grill me".
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
| name | pnpm |
| description | Use for pnpm dependency management, workspace configuration, catalogs, patches, overrides, or package-resolution problems. Do not use for routine `pnpm test`, `pnpm build`, `pnpm lint`, or `pnpm type-check` commands. |
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 |
