메뉴
Manage monorepos efficiently with consistent build tooling, scoped changes, and dependency hygiene. Use when working in or setting up a monorepo with multiple packages or applications.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | monorepo-workflows |
| description | Manage monorepos efficiently with consistent build tooling, scoped changes, and dependency hygiene. Use when working in or setting up a monorepo with multiple packages or applications. |
| license | Apache-2.0 |
| compatibility | Works with coding agents that support Agent Skills. |
| metadata | {"agentpacks.version":"0.2.0"} |
A monorepo scales when tooling enforces boundaries and CI only builds what changed.
package.json + unified lockfile. All packages share one version. Simple but forces coordinated releases."dependsOn": ["^build"] in Turborepo, targetDefaults in Nx.cache: false only for true side effects: deploy, publish, external API calls.turbo build twice; the second run must be 100% cached with no outputs re-executed.turbo run build --filter=...[HEAD^1] or nx affected.import/no-internal-modules) or TypeScript path aliases — no reaching into a sibling's src/ directly.madge --circular or the Nx graph checker in CI on every PR.pnpm-workspace.yaml, workspaces in package.json) in sync with actual package directories."dependsOn": ["^build"] for build tasks.src/ imports — only through declared exports.Create, critique, and operationalize engineering strategy documents using diagnosis, tradeoff exploration, guiding policy, coherent actions, and operating cadence. Use when an engineering leader needs strategy for a team, platform, architecture, migration, reliability program, or multi-quarter technical investment.
Run engineering leadership reviews across strategy, delivery, quality, architecture, launch readiness, security risk, and performance health.
Inspect GitHub pull requests for leadership-relevant release risk, quality gates, ownership, and follow-up actions.
Keep dependencies secure, minimal, and up to date. Use when auditing a project's supply chain, adding new libraries, evaluating upgrades, or hardening a CI pipeline against dependency risks.
Design and implement GraphQL APIs with correct schema design, resolver patterns, N+1 prevention, federation, and security. Use when building or evolving a GraphQL layer.
Make ML experiments reproducible and comparable by tracking hyperparameters, metrics, artifacts, and environments. Use when training models, tuning hyperparameters, or promoting models to production.