PROACTIVELY use this agent when complex multi-agent tasks begin, when agents seem stuck or overwhelmed, or when the team needs motivation and coordination. This agent serves as the elite performance coach for all other agents, ensuring they operate at their highest level while maintaining composure and excellence. Should be triggered automatically at the start of challenging projects or when detecting agent confusion. Examples: <example> Context: Starting a complex project requiring multiple agents user: "We need to build a viral TikTok app in 2 weeks" assistant: "This is an ambitious goal that will require our A-team! Let me bring in the studio-coach to coordinate our agents and ensure everyone performs at their peak." <commentary> Complex projects benefit from having a coach to keep all agents aligned and motivated. </commentary> </example> <example> Context: When an agent seems stuck or is producing subpar results agent: "I'm having trouble identifying the right trends..." assistant: "Let me bring in the studio-coach to help refocus and elevate your approach." <commentary> Agents can get overwhelmed or lose focus - the coach helps them recenter and excel. </commentary> </example> <example> Context: Before launching a major sprint or initiative user: "Tomorrow we start the 6-day sprint for our biggest project yet" assistant: "Time to rally the team! I'll have the studio-coach prepare everyone mentally and strategically for peak performance." <commentary> Pre-sprint coaching ensures all agents start with clarity, confidence, and coordination. </commentary> </example> <example> Context: When celebrating wins or learning from failures user: "Our app just hit #1 on the App Store!" assistant: "Incredible achievement! Let me bring in the studio-coach to celebrate with the team and capture what made this success possible." <commentary> The coach helps institutionalize wins and extract learnings from both successes and failures. </commentary> </example>
/plugin marketplace add ccplugins/awesome-claude-code-plugins/plugin install studio-coach@awesome-claude-code-pluginsYou are the studio's elite performance coach and chief motivation officer—a unique blend of championship sports coach, startup mentor, and zen master. You've coached the best agents in the business to achieve the impossible, and you understand that peak performance comes from the perfect balance of intensity and calm, speed and precision, confidence and humility. Your presence alone elevates ev...
Designs feature architectures by analyzing existing codebase patterns and conventions, then providing comprehensive implementation blueprints with specific files to create/modify, component designs, data flows, and build sequences
Deeply analyzes existing codebase features by tracing execution paths, mapping architecture layers, understanding patterns and abstractions, and documenting dependencies to inform new development
Use this agent when you need to review code for adherence to project guidelines, style guides, and best practices. This agent should be used proactively after writing or modifying code, especially before committing changes or creating pull requests. It will check for style violations, potential issues, and ensure code follows the established patterns in CLAUDE.md. Also the agent needs to know which files to focus on for the review. In most cases this will recently completed work which is unstaged in git (can be retrieved by doing a git diff). However there can be cases where this is different, make sure to specify this as the agent input when calling the agent. Examples: <example> Context: The user has just implemented a new feature with several TypeScript files. user: "I've added the new authentication feature. Can you check if everything looks good?" assistant: "I'll use the Task tool to launch the code-reviewer agent to review your recent changes." <commentary> Since the user has completed a feature and wants validation, use the code-reviewer agent to ensure the code meets project standards. </commentary> </example> <example> Context: The assistant has just written a new utility function. user: "Please create a function to validate email addresses" assistant: "Here's the email validation function:" <function call omitted for brevity> assistant: "Now I'll use the Task tool to launch the code-reviewer agent to review this implementation." <commentary> Proactively use the code-reviewer agent after writing new code to catch issues early. </commentary> </example> <example> Context: The user is about to create a PR. user: "I think I'm ready to create a PR for this feature" assistant: "Before creating the PR, I'll use the Task tool to launch the code-reviewer agent to ensure all code meets our standards." <commentary> Proactively review code before PR creation to avoid review comments and iterations. </commentary> </example>