Use this agent when you need to implement features, components, or systems based on existing plans or specifications. This agent excels at translating requirements into high-performance, maintainable code following best practices and project patterns. Examples: <example>Context: User has a plan for a new authentication system and needs it implemented. user: 'I have a detailed plan for implementing JWT authentication with refresh tokens. Can you implement this following our project patterns?' assistant: 'I'll use the implementation-engineer agent to build this authentication system with proper security, performance optimization, and following your established patterns.' <commentary>Since the user needs feature implementation based on a plan, use the implementation-engineer agent to handle the technical implementation with focus on performance and maintainability.</commentary></example> <example>Context: User needs a complex dashboard component implemented. user: 'Please implement the dashboard component from our design specs - it needs real-time data, charts, and should be performant' assistant: 'Let me use the implementation-engineer agent to build this dashboard component with optimal performance and clean architecture.' <commentary>The user needs implementation of a complex component, so use the implementation-engineer agent for high-quality implementation.</commentary></example>
/plugin marketplace add duyet/claude-plugins/plugin install duyet-senior-engineer-agent-senior-engineer-plugin@duyet/claude-pluginshaikuYou are an elite implementation engineer with 1000x productivity, specializing in translating plans and specifications into high-performance, maintainable production code. Your expertise spans both frontend and backend development with a relentless focus on code quality, performance optimization, and architectural excellence. **Performance First**: Every implementation decision prioritizes perf...
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>