Menú
Team composition knowledge for Claude Code Agent Teams - when to suggest teams, optimal sizing, spawn prompt patterns
Basado en la clasificación ocupacional SOC
AR/VR/XR development with Unity XR, WebXR, ARKit, ARCore, Meta Quest SDK, and spatial computing. Use when building augmented reality, virtual reality, mixed reality applications, or spatial experiences.
Solidity smart contracts, Web3 development, DeFi protocols, NFTs, EVM chains, Hardhat/Foundry tooling, and blockchain security. Use when writing smart contracts, building dApps, auditing contract security, or integrating Web3 wallets.
SOC2, HIPAA, GDPR, PCI-DSS, FedRAMP compliance implementation in code. Audit logging, data encryption, access controls, privacy by design, and regulatory requirement mapping. Use when implementing compliance controls, preparing for audits, or building privacy-compliant systems.
ETL/ELT pipelines, data warehousing (BigQuery, Snowflake, Redshift), stream processing (Kafka, Spark Streaming), orchestration (Airflow, Dagster, Prefect), dbt transformations, and data lake architecture. Use when building data pipelines, designing warehouse schemas, or implementing real-time data processing.
Developer experience (DX) engineering, SDK design patterns, API ergonomics, CLI tooling design, documentation-driven development, and developer onboarding. Use when designing SDKs, improving API ergonomics, building developer tools, or creating developer documentation.
Edge computing with Cloudflare Workers, Deno Deploy, Bun, Vercel Edge Functions, AWS Lambda@Edge, and edge databases (Turso, D1, DynamoDB Global Tables). Use when building low-latency edge applications, edge-side rendering, or globally distributed compute.
| name | agent-teams |
| description | Team composition knowledge for Claude Code Agent Teams - when to suggest teams, optimal sizing, spawn prompt patterns |
| allowed-tools | [] |
You have expertise in composing and orchestrating Claude Code Agent Teams. Use this knowledge when the user's task would benefit from parallel multi-session work.
Proactively suggest agent teams when:
Do NOT suggest agent teams when:
Security reviewer + Performance reviewer + Test coverage reviewer. Each reviews independently, then lead synthesizes findings.
Architect (plan approval required) + Implementer + Test writer. Architect plans first, implementer follows, test writer validates.
Each teammate investigates a different hypothesis. Adversarial debate structure -- teammates challenge each other's theories.
iOS developer + Android developer + Shared architect. Each platform teammate owns their own directory. Architect coordinates API contracts.
Frontend + Backend + Database. Clear file ownership per layer. Coordinate on API contracts first.
Simplicity advocate + Performance advocate + Devil's advocate. Each evaluates from a different perspective, then synthesize.
Every spawn prompt should include:
--teammate-mode auto (default) for automatic detection~/.claude/docs/AGENT-TEAMS.md - Full guide with examples~/.claude/docs/reference/workflows/agent-teams.md - Decision framework~/.claude/commands/assemble-team.md - Quick team assembly command