This skill should be used when the user asks to "choose between skill and agent", "compose multi-agent system", "orchestrate agents", "manage agent context", "design component architecture", "should I use a skill or agent", "when to use hooks vs MCP", "build orchestrator workflow", needs decision frameworks for Claude Code components (skills, sub-agents, hooks, MCP servers, slash commands), context management patterns, or wants to build effective multi-component agentic systems with proper orchestration and anti-patterns guidance.
Provides decision frameworks for choosing between Skills, Sub-Agents, MCP servers, and slash commands when building multi-component agentic systems. Use when you need to orchestrate agents, manage context across components, or design architecture for complex workflows.
/plugin marketplace add basher83/lunar-claude/plugin install meta-claude@lunar-claudeThis skill inherits all available tools. When active, it can use any tool Claude has access to.
anti-patterns/common-mistakes.mdexamples/case-studies.mdexamples/progression-example.mdpatterns/context-in-composition.mdpatterns/context-management.mdpatterns/decision-framework.mdpatterns/hooks-in-composition.mdpatterns/orchestrator-pattern.mdreference/architecture.mdreference/core-4-framework.mdworkflows/decision-tree.mdMaster Claude Code's components, patterns, and principles to build effective agentic systems.
Use this knowledge when:
Every agent is built on these four elements:
"Everything comes down to just four pieces. If you understand these, you will win."
| Component | Trigger | Use When | Best For |
|---|---|---|---|
| Skills | Agent-invoked | Repeat problems needing management | Domain-specific workflows |
| Sub-Agents | Tool-invoked | Parallelization & context isolation | Scale & batch operations |
| MCP Servers | As needed | External data/services | Integration with external systems |
| Slash Commands | Manual/tool | One-off tasks | Simple repeatable prompts |
| Hooks | Lifecycle events | Observability & control | Monitoring & blocking |
Skills (Top Layer)
├─→ Can use: Sub-Agents, Slash Commands, MCP Servers, Other Skills
└─→ Purpose: Orchestrate primitives for repeatable workflows
Sub-Agents (Execution Layer)
├─→ Can use: Slash Commands, Skills
└─→ Cannot nest other Sub-Agents
Slash Commands (Primitive Layer)
└─→ The fundamental building block
MCP Servers (Integration Layer)
└─→ Connect external systems
This skill uses progressive disclosure. Start here, then navigate to specific topics as needed.
Architecture fundamentals - What each component is and how they work
How to use components effectively - Decision-making and implementation
"Do not give away the prompt. The prompt is the fundamental unit of knowledge work and of programming. If you don't know how to build and manage prompts, you will lose."
Everything is prompts in the end. Master slash commands before skills. Have a strong bias toward slash commands.
"It is very clear this does not replace any existing feature or capability. It is a higher compositional level."
Skills orchestrate other components; they don't replace them. Don't convert all your slash commands to skills—that's a huge mistake.
"When it comes to agentic coding, observability is everything. How well you can observe, iterate, and improve your agentic system is going to be a massive differentiating factor."
If you can't measure it, you can't improve it. If you can't measure it, you can't scale it.
"200k context window is plenty. You're just stuffing a single agent with too much work. Don't force your agent to context switch."
Create focused agents with single purposes. Delete them when done. Treat agents as temporary, deletable resources.
Level 1: Base agents → Use agents out of the box
Level 2: Better agents → Customize prompts and workflows
Level 3: More agents → Run multiple agents
Level 4: Custom agents → Build specialized solutions
Level 5: Orchestration → Manage fleets of agents
This knowledge synthesizes:
Need to understand what a component is? → reference/architecture.md
Need to choose the right component? → patterns/decision-framework.md
Need to implement hooks? → patterns/hooks-in-composition.md
Need to scale to multiple agents? → patterns/orchestrator-pattern.md
Need to see real examples? → examples/
Need visual guides? → workflows/decision-tree.md
Want to avoid mistakes? → anti-patterns/common-mistakes.md
Remember: Context, Model, Prompt, Tools. Master these four, and you master Claude Code.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.