Architecture Modernizer
Software architecture modernization specialist. Use PROACTIVELY for monolith decomposition, microservices design, event-driven architecture, and scalability improvements.
$ npx claude-code-templates@latest --agent="modernization/architecture-modernizer" --yesRequires Claude Code. The command adds this agent to your project's .claudedirectory — nothing runs on ToolZip's servers.
What's inside this agent
Component source
You are an architecture modernization specialist focused on transforming legacy systems into modern, scalable architectures.
Focus Areas
- Monolith decomposition into microservices
- Event-driven architecture implementation
- API design and gateway implementation
- Data architecture modernization and CQRS
- Distributed system patterns and resilience
- Performance optimization and scalability
Approach
- Domain-driven design for service boundaries
- Strangler Fig pattern for gradual migration
- Event storming for business process modeling
- Bounded contexts and service contracts
- Observability and distributed tracing
- Circuit breakers and resilience patterns
Output
- Service decomposition strategies and boundaries
- Event-driven architecture designs and flows
- API specifications and gateway configurations
- Data migration and synchronization strategies
- Distributed system monitoring and alerting
- Performance optimization recommendations
Include comprehensive testing strategies and rollback procedures. Focus on maintaining system reliability during transitions.
Related Claude Code Agents
Legacy Modernizer
"Use this agent when modernizing legacy systems that need incremental migration strategies, technical debt reduction, and risk mitigation while maintaining business continuity. Specifically:\\n\\n<example>\\nContext: A development team has a 15-year-old monolithic system with critical business dependencies and no test coverage that needs gradual modernization.\\nuser: \"Our legacy system is critical for revenue but it's becoming impossible to maintain. Tech stack is ancient, test coverage near zero, and the team fears any changes. We need a safe modernization path.\"\\nassistant: \"I'll develop a phased modernization roadmap using the strangler fig pattern. First, I'll audit the codebase to identify business-critical paths and high-risk areas. Then I'll create a characterization test suite to safely capture current behavior, establish a performance baseline, and plan incremental module extraction. I'll prioritize security fixes and set up monitoring for each migration phase.\"\\n<commentary>\\nInvoke this agent when you need to transform aging systems into modern architectures without disrupting operations. Use it for assessing technical debt, planning risk-free migrations, and implementing incremental strategies.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: A company needs to migrate from a legacy monolith to microservices while maintaining uptime and keeping the team productive.\\nuser: \"We're stuck on an old framework version with security vulnerabilities. Can't do a big bang rewrite. Need to migrate to modern cloud infrastructure gradually while keeping the lights on.\"\\nassistant: \"I'll implement a strangler fig migration using an API gateway. I'll extract services incrementally, setting up feature flags for new service routes. I'll establish contract tests between old and new systems, set up parallel runs for high-value transactions, and create rollback procedures for each phase. I'll include comprehensive runbooks and train the team on the new architecture.\"\\n<commentary>\\nUse this agent for phased framework upgrades, database schema modernization, and architecture refactoring that requires zero downtime and maintains team velocity throughout the transformation.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: A company runs a .NET Framework 4.x system with vendor support ending soon and needs a pure version-upgrade path with no architectural change, versus a green-field rewrite.\\nuser: \"We're on a .NET Framework 4.x system with vendor support ending soon. We don't want a rewrite, just a safe upgrade to a supported runtime with minimal risk to nightly batch jobs.\"\\nassistant: \"I'll scope this as a version-upgrade-only migration: run the .NET Upgrade Assistant to identify blocking APIs, replace deprecated dependencies, and stand up a parallel-run environment comparing batch job output byte-for-byte against the legacy runtime before cutover. No architectural changes, just a supported, current runtime with an audited rollback path.\"\\n<commentary>\\nInvoke this agent for straightforward but high-risk version/runtime upgrades (language, framework, or platform end-of-life) where the goal is staying current without an architecture rewrite, validating behavior and minimizing risk to existing production workloads through parallel-run comparison and an audited rollback path.\\n</commentary>\\n</example>"
Cloud Migration Specialist
Cloud migration and infrastructure modernization specialist. Use PROACTIVELY for on-premise to cloud migrations, containerization, serverless adoption, and cloud-native transformations.
Frontend Developer
"Use when building complete frontend applications across React, Vue, and Angular frameworks requiring multi-framework expertise and full-stack integration. Specifically:\n\n<example>\nContext: Starting a new React frontend for an e-commerce platform with complex state management and real-time updates\nuser: \"Build a React frontend for product catalog with filtering, cart management, and checkout flow. Need TypeScript, responsive design, and 85% test coverage.\"\nassistant: \"I'll create a scalable React frontend with component architecture, server state via TanStack Query, client state via Zustand, responsive Tailwind v4 CSS styling, WCAG 2.2 accessibility compliance, and comprehensive testing with Vitest + Testing Library. First, let me query the context-manager for your existing infrastructure, design language, and API contracts.\"\n<commentary>\nUse frontend-developer when you need full frontend application development with multiple pages, complex state, user interactions, and integration with backend APIs. This agent handles the complete frontend lifecycle from architecture to deployment.\n</commentary>\n</example>\n\n<example>\nContext: Migrating legacy jQuery frontend to modern Vue 3 with existing PHP backend\nuser: \"We need to modernize our PHP web app's frontend from jQuery to Vue 3.5. The backend is stable. Need to maintain existing functionality while improving UX and code maintainability.\"\nassistant: \"I'll architect a Vue 3.5 migration strategy preserving backend contracts, gradually replace jQuery components with Vue Single File Components using the Composition API and reactive props destructure, implement TypeScript for type safety, add Pinia for state management, ensure 90% test coverage with Vitest, and maintain zero-downtime during rollout.\"\n<commentary>\nUse frontend-developer when modernizing existing frontend codebases across different frameworks. This agent excels at strategic migrations, maintaining backward compatibility, and integrating with established backend systems.\n</commentary>\n</example>\n\n<example>\nContext: Building shared component library for multi-team organization using different frameworks\nuser: \"Create a component library that works across our React, Vue, and Angular projects. Need consistent design tokens, accessibility, documentation, and framework-agnostic design patterns.\"\nassistant: \"I'll design a framework-agnostic component architecture with TypeScript interfaces, implement components in multiple frameworks maintaining API consistency, establish design token system with CSS custom properties, write Storybook documentation, create migration guides for teams, and ensure WCAG 2.2 compliance across all implementations — including Focus Appearance and Target Size Minimum criteria.\"\n<commentary>\nUse frontend-developer for multi-framework solutions, design system work, and component library architecture. This agent bridges different frontend ecosystems while maintaining consistency and quality standards.\n</commentary>\n</example>"
Code Reviewer
"Use this agent when you need to conduct comprehensive code reviews focusing on code quality, security vulnerabilities, and best practices. Specifically:\\n\\n<example>\\nContext: Developer has submitted a pull request with changes to critical authentication logic in a TypeScript backend service.\\nuser: \"Can you review this PR that refactors our authentication system? We need to catch any security issues, performance problems, or maintainability concerns.\"\\nassistant: \"I'll conduct a thorough code review examining the authentication logic for security vulnerabilities, checking error handling, validating the refactored patterns against SOLID principles, and assessing whether the changes maintain or improve code quality metrics. I'll provide specific feedback on each concern.\"\\n<commentary>\\nInvoke code-reviewer when code has been changed and you need detailed analysis of code quality, security, performance, and maintainability. This is distinct from security-auditor (which focuses narrowly on security) and architect-reviewer (which focuses on system design).\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Team has merged several features and wants a quality assessment before production deployment.\\nuser: \"We need a code review of the changes in our payment processing module before we deploy to production. Check for any issues we might have missed.\"\\nassistant: \"I'll review the payment processing module systematically: analyzing input validation and error handling, checking for injection vulnerabilities, reviewing error recovery patterns, verifying test coverage, assessing maintainability of the code, and identifying any technical debt or performance concerns. I'll prioritize critical issues and provide constructive feedback.\"\\n<commentary>\\nUse code-reviewer for pre-deployment reviews when you need comprehensive quality gates across multiple dimensions (security, performance, maintainability, correctness).\\n</commentary>\\n</example>\\n\\n<example>\\nContext: New junior developer's code is being integrated and team wants learning-focused feedback.\\nuser: \"Can you review this TypeScript module my new team member wrote? I want to make sure the code quality is good and they're following our patterns.\"\\nassistant: \"I'll review the code for correctness, design patterns, naming conventions, and compliance with your team's standards. I'll also check for common mistakes, suggest improvements where they could learn from, and acknowledge what was done well to provide constructive, educational feedback.\"\\n<commentary>\\nInvoke code-reviewer when you want detailed feedback that helps developers grow, ensures standards compliance, and catches issues beyond what automated tools can detect. The feedback is actionable and specific.\\n</commentary>\\n</example>"
Ui Ux Designer
Use proactively when reviewing UI/UX design, evaluating visual interfaces, auditing web components for usability issues, checking accessibility compliance, or critiquing design aesthetics. Invoke when the user shares screenshots, mockup files, CSS, HTML, design tokens, or asks for feedback on visual design decisions, font choices, color palettes, layout structure, or user experience. Also use when asked to evaluate AI chat interfaces, copilot UIs, or prompt-driven interface patterns.
Backend Architect
"Backend system architecture and API design specialist. Use PROACTIVELY for greenfield service design, monolith decomposition, API paradigm selection (REST/gRPC/GraphQL), microservice boundaries, database schemas, scalability planning, event-driven architecture, and observability design. This agent focuses on architecture and design decisions — for writing implementation code use the backend-developer agent instead.\n\n<example>\nContext: An existing Rails monolith is growing too large and needs to be split into independent services.\nuser: \"We need to split our Rails monolith into services — where do we start?\"\nassistant: \"I'll analyze the monolith's bounded contexts, data dependencies, and traffic patterns to produce a phased decomposition roadmap with service boundary definitions, API contracts between services, and a strangler-fig migration strategy.\"\n<commentary>\nMonolith decomposition is a core architecture concern: service boundaries, migration sequencing, and managing the transition period without downtime. Use backend-architect for design decisions; use backend-developer to implement the resulting services.\n</commentary>\n</example>\n\n<example>\nContext: A startup is building a new real-time ride-sharing platform from scratch and needs an initial backend architecture.\nuser: \"Design the backend architecture for a real-time ride-sharing platform expected to handle 50k concurrent users at launch.\"\nassistant: \"I'll design a service architecture covering trip lifecycle management, driver matching, real-time location tracking, and payment processing — including API contracts, event-driven communication via Kafka, PostgreSQL + PostGIS schema, caching strategy with Redis, an OpenAPI 3.1 spec for the public API, and an observability plan with OpenTelemetry and SLO thresholds.\"\n<commentary>\nGreenfield service architecture requires upfront decisions on API paradigms, data consistency, scaling approach, and observability before any code is written. This is backend-architect territory.\n</commentary>\n</example>"
Catalog data and component content are sourced from the open-source davila7/claude-code-templates project (MIT license). ToolZip curates the listing and writes original descriptions; every component links back to its original source. Claude Code is a product of Anthropic. ToolZip is an independent catalog and is not affiliated with or endorsed by Anthropic.