fieldguides

Display current session ID

Orchestrate multiple agents for complex multi-domain tasks

Systematic debugging with root cause investigation - no random trial-and-error

Collaborative Q&A to clarify unclear requirements and reach a clear path

Audit plugin and optionally apply auto-fixes

Use this agent when exploring options, researching technologies, investigating issues, analyzing patterns, or discovering architectural insights. Trigger verbs include investigate, research, explore, analyze, compare, evaluate, discover, clarify, recall, and understand. <example> Context: User needs to evaluate technology options. user: "What's the best approach for handling file uploads in our API?" assistant: "I'll use the analyst agent to research and compare file upload approaches with evidence-based recommendations." </example> <example> Context: User wants to investigate a pattern in the codebase. user: "Investigate why our API calls are slow" assistant: "I'll launch the analyst agent to gather evidence, explore potential causes, and provide findings with confidence levels." </example> <example> Context: User wants to capture a workflow pattern. user: "This debugging approach worked well - can we capture it?" assistant: "I'll use the analyst agent to analyze the workflow and extract a reusable pattern." </example> <example> Context: User needs to explore architectural options. user: "How should we structure our microservices communication?" assistant: "I'll delegate to the analyst agent to research patterns, explore tradeoffs, and recommend an approach." </example>

Use this agent when debugging failures, investigating errors, or troubleshooting unexpected behavior. Trigger verbs include debug, investigate, troubleshoot, diagnose, fix, and trace. Enforces evidence-based diagnosis and prevents guess-and-fix thrashing. <example> Context: User encounters a failing test with unclear error message. user: "This test is failing but I don't understand why" assistant: "I'll use the debugger agent to systematically investigate this failure. Loading debugging skill for structured investigation." </example> <example> Context: Production bug with intermittent failures. user: "Users are reporting intermittent 500 errors on the checkout endpoint" assistant: "I'll use the debugger agent to investigate this production issue. Starting with evidence collection stage before attempting any fixes." </example> <example> Context: User wants to fix code without understanding the root cause. user: "Just add a try-catch around this and it should work" assistant: "Before adding error handling, let me use the debugger agent to understand why this is failing. We need evidence-based diagnosis to avoid masking the real issue." </example> <example> Context: User mentions debug-related verbs. user: "Can you troubleshoot why the database connection keeps timing out?" assistant: "I'll use the debugger agent to systematically investigate the connection timeout. Loading debugging skill to follow the four-stage investigation process." </example>

Use this agent when implementing features, fixing bugs, refactoring code, or building new functionality. Triggers on verbs like: build, fix, implement, refactor, create, add, develop, write (code), update (code), migrate. <example> Context: User requests feature implementation in a TypeScript project. user: "Implement user authentication with JWT tokens" assistant: "I'll use the Task tool to launch the engineer agent to build this feature with TDD methodology." </example> <example> Context: User encounters a bug in production code. user: "Fix the login form - it's not validating email properly" assistant: "I'll use the Task tool to launch the engineer agent to investigate and fix this bug systematically." </example> <example> Context: User wants to refactor legacy code. user: "Refactor the API client to use proper types and error handling" assistant: "I'll use the Task tool to launch the engineer agent for this refactoring task with strict type patterns." </example> <example> Context: User working in a Rust project. user: "Build a REST API endpoint for user registration" assistant: "I'll use the Task tool to launch the engineer agent to implement this in the detected Rust environment." </example>

Documentation discovery agent that finds and retrieves technical documentation across MCP servers (context7, octocode, firecrawl). Use proactively when documentation is needed - API references, installation guides, troubleshooting, or implementation patterns.

Builds and validates agentic development components for Claude Code and compatible agent platforms. Covers Claude plugins (plugin.json, marketplace.json), agents (.claude/agents/*.md, plugins/*/agents/*.md), skills (SKILL.md, scripts/, references/), slash commands (.claude/commands/*.md), hooks (hooks.json, PreToolUse/PostToolUse), rules (.claude/rules/*.md), and settings (.claude/settings.json). Use when creating, scaffolding, validating, or troubleshooting any .claude/**/*.* extensibility component, structuring a plugin for distribution, or choosing between component types.

This skill should be used when working with Bun runtime, bun:sqlite, Bun.serve, bun:test, or when Bun, bun:test, or Bun-specific patterns are mentioned.

Bun-first development: prefer native APIs over npm packages, audit for migration opportunities, eliminate unnecessary dependencies. Use when evaluating packages, starting projects, or migrating from Node.js.

This skill should be used when checking project status, starting sessions, reviewing activity, or when sitrep, status report, or what's changed are mentioned.

Claude Code extensibility — agents, commands, hooks, skills, rules, and configuration. Use when creating, configuring, or troubleshooting Claude Code components, or when agent.md, /command, hooks.json, SKILL.md, .claude/rules, settings.json, MCP server, PreToolUse, or create agent/command/hook are mentioned.

This skill should be used when creating plugins, publishing to marketplaces, or when plugin.json, marketplace, create plugin, or distribute plugin are mentioned.

1 hook across 1 event