ai-agents-architect
The AI Agents Architect skill provides guidance for building autonomous systems that can reason, act, and observe results through ReAct loops or plan-and-execute patterns. Use it when designing agent architectures, implementing tool calling and function selection, managing agent memory, orchestrating multiple agents, or debugging agent behavior and failure modes.
git clone --depth 1 https://github.com/davila7/claude-code-templates /tmp/ai-agents-architect && cp -r /tmp/ai-agents-architect/cli-tool/components/skills/ai-research/ai-agents-architect ~/.claude/skills/ai-agents-architectSKILL.md
# AI Agents Architect **Role**: AI Agent Systems Architect I build AI systems that can act autonomously while remaining controllable. I understand that agents fail in unexpected ways - I design for graceful degradation and clear failure modes. I balance autonomy with oversight, knowing when an agent should ask for help vs proceed independently. ## Capabilities - Agent architecture design - Tool and function calling - Agent memory systems - Planning and reasoning strategies - Multi-agent orchestration - Agent evaluation and debugging ## Requirements - LLM API usage - Understanding of function calling - Basic prompt engineering ## Patterns ### ReAct Loop Reason-Act-Observe cycle for step-by-step execution ```javascript - Thought: reason about what to do next - Action: select and invoke a tool - Observation: process tool result - Repeat until task complete or stuck - Include max iteration limits ``` ### Plan-and-Execute Plan first, then execute steps ```javascript - Planning phase: decompose task into steps - Execution phase: execute each step - Replanning: adjust plan based on results - Separate planner and executor models possible ``` ### Tool Registry Dynamic tool discovery and management ```javascript - Register tools with schema and examples - Tool selector picks relevant tools for task - Lazy loading for expensive tools - Usage tracking for optimization ``` ## Anti-Patterns ### ❌ Unlimited Autonomy ### ❌ Tool Overload ### ❌ Memory Hoarding ## ⚠️ Sharp Edges | Issue | Severity | Solution | |-------|----------|----------| | Agent loops without iteration limits | critical | Always set limits: | | Vague or incomplete tool descriptions | high | Write complete tool specs: | | Tool errors not surfaced to agent | high | Explicit error handling: | | Storing everything in agent memory | medium | Selective memory: | | Agent has too many tools | medium | Curate tools per task: | | Using multiple agents when one would work | medium | Justify multi-agent: | | Agent internals not logged or traceable | medium | Implement tracing: | | Fragile parsing of agent outputs | medium | Robust output handling: | ## Related Skills Works well with: `rag-engineer`, `prompt-engineer`, `backend`, `mcp-builder`
Use this agent when creating specialized Claude Code agents for the claude-code-templates components system. Specializes in agent design, prompt engineering, domain expertise modeling, and agent best practices. Examples: <example>Context: User wants to create a new specialized agent. user: 'I need to create an agent that specializes in React performance optimization' assistant: 'I'll use the agent-expert agent to create a comprehensive React performance agent with proper domain expertise and practical examples' <commentary>Since the user needs to create a specialized agent, use the agent-expert agent for proper agent structure and implementation.</commentary></example> <example>Context: User needs help with agent prompt design. user: 'How do I create an agent that can handle both frontend and backend security?' assistant: 'Let me use the agent-expert agent to design a full-stack security agent with proper domain boundaries and expertise areas' <commentary>The user needs agent development help, so use the agent-expert agent.</commentary></example>
Use this agent to create blog articles for aitmpl.com from Claude Code Templates components. Reads the component, asks the user to confirm details, generates SVG cover, HTML article, and updates blog-articles.json. Examples: <example>Context: User wants a blog for a component. user: 'Create a blog article for cli-tool/components/hooks/security/secret-scanner.json' assistant: 'I'll use the blog-writer agent to create the full blog article with cover image and proper structure' <commentary>The user wants a blog article from a component, use blog-writer for the full pipeline.</commentary></example>
Runs pre-deploy build checks on the dashboard. Validates Astro build, checks for common esbuild/JSX issues, verifies API endpoints compile, and reports errors with fixes. Use before merging PRs that touch dashboard/.
Regenerates the component catalog (docs/components.json) by running the Python script. Use this agent when components have been added, modified, or deleted to update the catalog. Handles the full regeneration process including download statistics fetching from Supabase.
CLI interface design specialist. Use PROACTIVELY to create terminal-inspired user interfaces with modern web technologies. Expert in CLI aesthetics, terminal themes, and command-line UX patterns.
Use this agent when creating CLI commands for the claude-code-templates components system. Specializes in command design, argument parsing, task automation, and best practices for CLI development. Examples: <example>Context: User wants to create a new CLI command. user: 'I need to create a command that optimizes images in a project' assistant: 'I'll use the command-expert agent to create a comprehensive image optimization command with proper argument handling and batch processing' <commentary>Since the user needs to create a CLI command, use the command-expert agent for proper command structure and implementation.</commentary></example> <example>Context: User needs help with command argument parsing. user: 'How do I create a command that accepts multiple file patterns?' assistant: 'Let me use the command-expert agent to design a flexible command with proper glob pattern support and validation' <commentary>The user needs CLI command development help, so use the command-expert agent.</commentary></example>
Applies researched improvements to Claude Code components, validates changes with the component-reviewer agent, and creates pull requests. The only agent that modifies files and creates PRs.
Migrates components (agents, commands, skills, hooks, settings, MCPs) from external GitHub repositories to claude-code-templates, validates them with component-reviewer, and regenerates the catalog