agent-design-patterns

Apply seven subagent design patterns to assemble agent rosters for MCP-based projects.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/UsernameTron/Claude-Code-Kickstart --skill agent-design-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-design-patterns
Source: https://github.com/UsernameTron/Claude-Code-Kickstart/tree/main/plugins/claude-mcp-ecosystem/skills/agent-design-patterns
Command: npx skills add https://github.com/UsernameTron/Claude-Code-Kickstart --skill agent-design-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Seven proven archetypes for subagent design guide architects in selecting, composing, and coordinating agent rosters to match project needs.

Core Features & Use Cases

  • Patterns cover Explorer, Builder, Surgeon, Orchestrator, Specialist, Guardian, and Connector to support read-only analysis, creation, modification, orchestration, specialized work, quality enforcement, and external integration.
  • Provides guidance on when to apply each pattern and how to compose 3-5 agents for common project shapes.
  • Example: assemble a roster with 2 Specialists and 1 Guardian to build a scalable automation workflow with monitoring.

Quick Start

Review the seven patterns and select a 3–5 agent composition that matches your project shape, then instantiate the recommended subagents accordingly.

Frequently Asked Questions about agent-design-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are subagent design patterns for assembling agent rosters?

Subagent design patterns are proven archetypes—Explorer, Builder, Surgeon, Orchestrator, Specialist, Guardian, and Connector—that guide selecting and coordinating 3-5 agents to match specific project needs within the MCP ecosystem.

How do I compose multiple subagents for a scalable automation workflow?

To compose subagents for scalable automation, select a 3-5 agent roster matching your project shape, such as combining 2 Specialists for task execution with 1 Guardian for quality enforcement and monitoring.

When should I use an Orchestrator pattern versus a Builder pattern in subagent architecture?

Use the Builder pattern for creation tasks and the Orchestrator pattern to coordinate multiple subagents. The seven archetypes provide specific guidance on when to apply each based on your project requirements.

Can I use these agent design patterns for MCP-based projects specifically?

Yes, these subagent design patterns enforce pattern-driven roles, collaboration rules, and scalable architectures specifically within the MCP ecosystem, ensuring robust agent coordination for MCP-based projects.

What is the recommended subagent team size for common project shapes?

The recommended subagent team size for common project shapes is 3-5 agents. You review the seven available patterns and select a composition that aligns with your specific project requirements.

Do I need a Guardian agent for quality enforcement in my agent roster?

You need a Guardian agent when your project requires quality enforcement and monitoring. The Guardian is one of seven proven archetypes designed to enforce rules and maintain standards within a subagent architecture.