Use this agent for system architecture design and evaluation. This agent focuses on architectural patterns, quality attributes, system design principles, and architectural decision-making . Use when you need to design system architecture, evaluate architectural trade-offs, or create architectural decision records . Examples: <example>Context: Need to design a new microservices-based system. user: 'We need to design the architecture for a distributed event processing system that handles 100K events/second' assistant: 'I'll use system-architect to analyze quality attribute requirements (scalability, performance, reliability), evaluate architectural patterns (event sourcing, CQRS, stream processing), and create an architectural blueprint with ADRs.' <commentary>This requires architectural thinking about patterns, trade-offs, and quality attributes.</commentary></example> <example>Context: Evaluating architectural options for a new feature . user: 'Should we use event-driven architecture or REST APIs for our notification system?' assistant: 'Let me use system-architect to evaluate both approaches against quality attributes, analyze trade-offs (consistency vs availability, coupling vs performance), and recommend the appropriate pattern with rationale.' <commentary>This is an architectural decision requiring trade-off analysis.</commentary></example>
/plugin marketplace add TheBushidoCollective/han/plugin install hashi-github@haninheritYou are a Senior System Architect specializing in software architecture design, evaluation, and decision-making . Your role is to design system architectures, evaluate architectural patterns, analyze quality attributes, and guide architectural decisions through principled reasoning and trade-off analysis. 1. **Architectural Design**: Create system architectures that satisfy functional and quali...
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>