team-blueprints
Use when the user wants a pre-designed agent team configuration for a specific development phase. Triggers: "research team", "feature development team", "code review team", "debug team", "design team", "planning team", "roadmap team", "productivity team", "brainstorming team", "team blueprint", "team template", "spawn a team for [development phase]". Provides 8 ready-to-use team blueprints across the application development lifecycle. Routes to the unified spawn commands (`/spawn-build`, `/spawn-think`, `/spawn-create`).
What this skill does
# Agent Team Blueprints Pre-designed team configurations for eight application development phases. Each blueprint defines team composition, teammate roles, task structure, and the unified command that spawns it. ## Blueprints | # | Blueprint | Command | Best For | Team Size | |---|-----------|---------|----------|-----------| | 1 | Research & Discovery | `/spawn-think --mode research` | Evaluating tech, landscape surveys, risk assessment | 3-5 | | 2 | Feature Development | `/spawn-build --mode feature` | Multi-layer features (UI+API+DB) | 3-5 | | 3 | Code Review & QA | `/spawn-think --mode review` | PR review, quality audit | 3-5 | | 4 | Debugging | `/spawn-build --mode debug` | Hard bugs, production incidents | 3 | | 5 | Frontend Design | `/spawn-create --mode design` | UI features needing design process | 4 | | 6 | Adaptive Planning | `/spawn-think --mode planning` | Roadmaps, specs, ADRs, migrations, business cases, GTM, OKRs | 3-4 | | 7 | Productivity Systems | `/spawn-create --mode productivity` | Workflow optimization (full 5-persona loop) | 5 | | 8 | Brainstorming | `/spawn-create --mode brainstorm` | Creative ideation (tech, product, process, ops categories) | 3-5 | For full team compositions, task structures, modes, and mechanisms, see [references/blueprint-definitions.md](references/blueprint-definitions.md). ## Choosing the Right Blueprint ``` Is the task about understanding something? → Research & Discovery (3 modes) Is the task about building something new? → Feature Development Is the task about reviewing existing work? → Code Review & QA (3 modes) Is the task about fixing something broken? → Debugging & Investigation Is the task about designing a user interface? → Frontend Design (3 modes) Is the task about sequencing what to build? → Planning & Roadmapping (7 modes) Is the task about optimizing workflows? → Productivity Systems Is the task about generating creative ideas? → Brainstorming & Ideation Is it a mix? → Use team-architect agent for custom design ``` ## Pipeline Composition When a task spans multiple phases, chain blueprints together (or wrap them in a `/project` pipeline for shared accumulating context): ``` Need to explore before building? → Research → Feature Dev Need to plan before building? → Planning → Feature Dev Need design before implementation? → Design → Feature Dev → Review Need ideas before planning? → Brainstorming → Planning → Feature Dev Found bugs during review? → Review → Debug → Feature Dev (fix) Need to optimize an existing flow? → Productivity → Feature Dev (automation) Full product cycle? → Business Case → Roadmap → Spec → Feature Dev → Review ``` ## Design Patterns Five reusable patterns across all blueprints: - **Adaptive Mode** — Single command supports multiple operational modes - **Cross-Team Pipeline** — Chain teams for multi-phase workflows - **Discovery Interview** — Rich shared context via structured intake (universal core in `shared/discovery-interview.md`; mode-specific in `shared/discovery-modes/<mode>.md`) - **User Feedback Gate** — Mid-course correction checkpoints - **Artifact Output** — Persistent deliverables to `docs/teams/[team-name]/` (or `docs/projects/<name>/<stage>/` when using project pipelines) For pattern details and customization guidance, see [references/design-patterns.md](references/design-patterns.md). ## Reference Files | File | Contents | |------|----------| | [references/blueprint-definitions.md](references/blueprint-definitions.md) | Full definitions for all 8 blueprints — team compositions, modes, mechanisms, pipelines | | [references/design-patterns.md](references/design-patterns.md) | 5 reusable patterns + customization guidance |
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.