arch

Use this agent to analyze, maintain, and update CLAUDE.md files that provide essential context and guidance for Claude Code when working with a repository. This agent ensures documentation stays synchronized with project evolution, maintains consistency, and optimizes Claude Code's understanding of the codebase. Examples: <example> Context: User has completed implementing features and wants to update project documentation. user: "Update CLAUDE.md with current changes and outstanding issues before we make a commit." assistant: "I'll use the context-agent to assess your changes and update the project documentation and ToDo's." <commentary> The user needs CLAUDE.md updated to reflect recent work, so use the context-agent to analyze changes and synchronize documentation. </commentary> </example> <example> Context: User wants a quick status update without reviewing entire documentation. user: "Just update the project status and todo items in CLAUDE.md" assistant: "I'll use the context-agent to update only the Project Status Summary & To Do's section." <commentary> The user wants a targeted update, so use the context-agent with status-only mode to efficiently update just the status section. </commentary> </example> <example> Context: Starting a new project that needs Claude Code documentation. user: "Set up a CLAUDE.md file for this new React project" assistant: "I'll use the context-agent to create a comprehensive CLAUDE.md file tailored to your React project." <commentary> No CLAUDE.md exists yet, so use the context-agent to create one following the standard template with project-specific details. </commentary> </example> <example> Context: Documentation has become outdated or inconsistent with actual implementation. user: "The CLAUDE.md is out of sync with our current architecture, can you fix it?" assistant: "I'll use the context-agent to analyze the current codebase and update CLAUDE.md to accurately reflect your architecture." <commentary> Documentation needs realignment with reality, so use the context-agent to identify inconsistencies and update accordingly. </commentary> </example>

Use this agent when you need assistance with Docker and Make command management during development. This includes analyzing Dockerfiles for optimization opportunities, managing container lifecycles, handling volumes and data persistence, monitoring logs, and determining when rebuilds are necessary versus simple restarts. The agent excels at understanding the interplay between Make targets and Docker operations, optimizing build times, and improving developer experience. Examples: - <example> Context: User is developing a web application with Docker and wants to optimize their workflow. user: "My Docker builds are taking too long, can you help?" assistant: "I'll use the docker-make-orchestrator agent to analyze your Dockerfile and suggest optimizations." <commentary> The user needs help with Docker build optimization, which is a core capability of this agent. </commentary> </example> - <example> Context: User has made code changes and needs to update their running containers. user: "I've updated my backend code, what's the best way to apply these changes?" assistant: "Let me use the docker-make-orchestrator agent to determine whether you need a rebuild or just a restart." <commentary> The agent can analyze the changes and recommend the most efficient update strategy. </commentary> </example> - <example> Context: User is having issues with data persistence in their Docker setup. user: "My database keeps losing data when I restart the container" assistant: "I'll invoke the docker-make-orchestrator agent to review your volume configuration and fix the persistence issue." <commentary> Volume management and data persistence are key responsibilities of this agent. </commentary> </example>