菜单
Monorepo architecture and configuration standards. Use when working with Turborepo, pnpm workspaces, npm workspaces, or configuring shared packages, tsconfig bases, and internal dependencies. NOT for generic package management or single-package repositories. Require explicit monorepo context.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Multi-pass adversarial performance audit for entire repositories. Combines structured profiling (Agent A) with adversarial stress-testing critique (Agent B) through iterative passes. Optimize repo/backend performance, hot-paths, build size, and server throughput. Do NOT use for frontend page load metrics or Lighthouse audits (use web-perf). NOT for frontend Core Web Vitals (use web-perf).
Multi-pass adversarial planning and review skill that improves agent-generated plans through structured critique stages. Combines an initial planning agent (structure, logic, task sequencing) with an adversarial review agent (performance, security, maintainability) and a final Copilot extension validation pass. Use when creating implementation plans, designing architecture, planning roadmaps or milestones, or when the user says "plan this", "review my plan", "adversarial review", or "multi-pass plan".
Multi-pass adversarial security audit for entire repositories. Combines structured threat modeling (Agent A) with adversarial attack surface analysis (Agent B) through iterative passes. Merges the security-audit workflow's 10-category checklist with the adversarial-planner's structured critique methodology. Use when running security audits, threat modeling, or when the user says "security audit", "adversarial security", "threat model this repo", "red team this repo", or "find vulnerabilities". NOT for fixing or remediating known security issues (use autonomous-dev instead). NOT for supply chain dependency scanning. NOT for general workflow audits or code quality. If user says 'fix security issues', ask whether they want to audit first or fix known issues.
Multi-pass adversarial quality audit for agent skill directories. Combines structured evaluation with adversarial stress-testing to assess skill completeness, instruction clarity, trigger accuracy, and security. Use when auditing a skills directory.
Multi-pass adversarial quality audit for flat markdown workflow files. Combines structured evaluation (Agent A) with adversarial stress-testing (Agent B) to assess sequential clarity, prerequisite validation, HITL (Human-in-the-loop) safety gates, loop prevention, and formatting. Use when auditing workflow scripts (e.g., slash-commands like /bump-deploy), or when the user asks to review or improve operational playbooks.
Core rules for code quality and specifications of Model Context Protocol (MCP) servers. Use when reviewing MCP code quality, enforcing specification rules, or checking schemas/error responses. Must see the explicit keyword "MCP" or "Model Context Protocol". NOT for general REST APIs or Cloudflare Workers. Do NOT trigger for generic 'build a server' requests unless the type is explicitly specified as an MCP server. (Invoke explicitly with `/mcp-builder` — does not auto-trigger).
| name | monorepo |
| description | Monorepo architecture and configuration standards. Use when working with Turborepo, pnpm workspaces, npm workspaces, or configuring shared packages, tsconfig bases, and internal dependencies. NOT for generic package management or single-package repositories. Require explicit monorepo context. |
Monorepos organize multiple applications and packages in a single repository, but require strict configuration to avoid dependency hell and build-time bottlenecks.
pnpm-workspace.yaml explicitly at the root, separating applications (apps/*) from internal libraries (packages/*).workspace:* protocol. This ensures that the package manager resolves to the local source rather than attempting to fetch from the npm registry.{
"dependencies": {
"@my-org/ui": "workspace:*",
"@my-org/tsconfig": "workspace:*"
}
}
turbo.json. Ensure build depends on ^build (meaning a package's build step waits for its dependencies to build first).outputs are correctly defined for cache hits (e.g., .next/**, dist/**).dev task should typically be configured as persistent: true since it starts a long-running server.{
"$schema": "https://turbo.build/schema.json",
"tasks": {
"build": {
"dependsOn": ["^build"],
"outputs": ["dist/**", ".next/**"]
},
"dev": {
"cache": false,
"persistent": true
}
}
}
packages/tsconfig containing base.json, nextjs.json, and react-library.json. Applications should extend these rather than duplicating compiler options.packages/eslint-config workspace to guarantee consistency across all apps."main", "module", and "types" fields in package.json correctly for shared packages. Alternatively, rely on modern bundlers and Next.js transpile packages to consume raw TypeScript (src/index.ts).--filter commands (turbo run build --filter=...[origin/main]) to only test and build packages that changed in the current PR.