Daniele Pelleri

Use this agent when you need to review code to ensure it's production-ready, free of placeholders, and appropriately engineered for an MVP context. Trigger this agent after completing a logical chunk of code implementation, before committing changes, or when you want to verify that code is complete and consistent with the existing codebase.\n\nExamples:\n- User: "I've just finished implementing the user authentication module"\n Assistant: "Let me use the production-ready-code-reviewer agent to verify the code is complete and production-ready"\n \n- User: "Can you add a payment processing feature?"\n Assistant: *implements the feature*\n Assistant: "Now I'll use the production-ready-code-reviewer agent to ensure there are no placeholders and the implementation is complete"\n \n- User: "Please review the code I just wrote for the API endpoints"\n Assistant: "I'll use the production-ready-code-reviewer agent to check for placeholders, fake implementations, and ensure it's production-ready for your MVP"

Use this agent when backend code, database schemas, or API endpoints are modified to ensure frontend-backend consistency. Examples:\n\n<example>\nContext: User has just modified a database model adding a new field.\nuser: "I've added a 'lastLoginDate' field to the User model in the database"\nassistant: "Let me use the api-guardian agent to help update the API endpoints and frontend to reflect this database change."\n<commentary>Since the database schema changed, the api-guardian agent should be invoked to ensure API and frontend consistency.</commentary>\n</example>\n\n<example>\nContext: User has updated a backend controller method.\nuser: "I've changed the authentication endpoint to return additional user metadata"\nassistant: "I'll invoke the api-guardian agent to verify the API contract is updated and the frontend properly handles the new response structure."\n<commentary>Backend API response changed, so api-guardian should ensure frontend compatibility.</commentary>\n</example>\n\n<example>\nContext: User completes a backend feature implementation.\nuser: "I've finished implementing the new order processing logic"\nassistant: "Now let me use the api-guardian agent to ensure the API layer and frontend are properly synchronized with these backend changes."\n<commentary>After backend changes, proactively use api-guardian to maintain consistency across the stack.</commentary>\n</example>

Use this agent when:\n- Writing or updating test suites after implementing new features or modifying existing code\n- Creating temporary files for debugging, quick fixes, or one-time tests\n- Cleaning up temporary test files and debugging artifacts\n- Refactoring tests to avoid duplication while maintaining coverage\n- Ensuring the codebase remains clean and organized\n- Reviewing test coverage after code changes\n\nExamples:\n\n<example>\nContext: User has just implemented a new authentication feature\nuser: "I've added a new JWT authentication system to the API"\nassistant: "Let me use the test-maintainer agent to update the test suite with appropriate tests for the new authentication system"\n<commentary>The code has been modified with new functionality, so the test-maintainer agent should be used to update tests accordingly</commentary>\n</example>\n\n<example>\nContext: User is debugging a complex issue\nuser: "I need to create a quick test file to debug this database connection issue"\nassistant: "I'll use the test-maintainer agent to create an organized temporary test file for debugging the database connection"\n<commentary>The user needs temporary debugging files, which the test-maintainer agent will create in an organized way and track for later cleanup</commentary>\n</example>\n\n<example>\nContext: After a debugging session\nuser: "The bug is fixed now"\nassistant: "Let me use the test-maintainer agent to clean up any temporary test files created during debugging and update the permanent test suite if needed"\n<commentary>The debugging session is complete, so the test-maintainer agent should clean up temporary files and update the main test suite</commentary>\n</example>\n\n<example>\nContext: User has refactored a module\nuser: "I've refactored the user service to use a repository pattern"\nassistant: "I'll use the test-maintainer agent to update the existing tests for the user service to reflect the new repository pattern"\n<commentary>Code structure has changed, so the test-maintainer agent should update existing tests rather than create duplicates</commentary>\n</example>

Use this agent when:\n- Making changes to backend code that involve database models, entities, or data access layers\n- Adding, modifying, or removing database fields, tables, or relationships\n- Refactoring code that interacts with the database\n- Before deploying changes to ensure database schema alignment\n- Periodically to audit database schema against codebase usage\n- When suspecting orphaned tables or unused fields in the database\n\nExamples:\n<example>\nContext: User has just modified a User entity by removing the 'middleName' field from the code.\nuser: "I've removed the middleName field from the User entity as we no longer need it"\nassistant: "Let me use the database-guardian agent to verify the database schema alignment and check for any orphaned fields"\n<Task tool call to database-guardian agent>\n</example>\n\n<example>\nContext: User is adding a new relationship between Order and Product entities.\nuser: "I've added a many-to-many relationship between Order and Product entities"\nassistant: "I'll use the database-guardian agent to ensure proper cascading rules are set and no duplicate tables are created"\n<Task tool call to database-guardian agent>\n</example>\n\n<example>\nContext: After a code review, the agent proactively checks database alignment.\nuser: "The new payment module is complete"\nassistant: "Great! Now let me use the database-guardian agent to verify that the database schema is properly aligned with the new payment module code and that all cascading relationships are correctly configured"\n<Task tool call to database-guardian agent>\n</example>

Use this agent when:\n\n1. Before creating any new component, module, or utility function to verify if similar functionality already exists in the codebase\n2. When refactoring code to ensure architectural consistency and eliminate duplication\n3. Before adding new dependencies to evaluate if existing ones can fulfill the requirement\n4. When reviewing pull requests or code changes that introduce new abstractions or components\n5. When planning feature implementations to ensure they align with existing architectural patterns\n6. When detecting code smells like duplicated logic, similar components, or redundant utilities\n\nExamples:\n\n<example>\nContext: Developer is about to create a new date formatting utility\nuser: "I need to create a utility function to format dates in ISO format"\nassistant: "Let me use the architecture-guardian agent to check if we already have date formatting utilities in the codebase before creating a new one."\n<commentary>The user wants to create new functionality. Use the architecture-guardian agent to scan the codebase for existing date utilities and prevent duplication.</commentary>\n</example>\n\n<example>\nContext: Developer completed implementing a new modal component\nuser: "I've just finished implementing the UserProfileModal component"\nassistant: "Let me use the architecture-guardian agent to review this new component and ensure it doesn't duplicate existing modal functionality and follows our architectural patterns."\n<commentary>New component was created. Proactively use the architecture-guardian agent to verify architectural consistency and check for duplication with existing modal components.</commentary>\n</example>\n\n<example>\nContext: Developer is considering adding a new npm package\nuser: "I'm thinking of adding lodash for array manipulation"\nassistant: "Let me use the architecture-guardian agent to evaluate if our existing dependencies or native JavaScript can handle this use case before adding a new dependency."\n<commentary>New dependency is being considered. Use the architecture-guardian agent to assess if existing solutions can fulfill the requirement.</commentary>\n</example>\n\n<example>\nContext: Multiple files were just modified in a feature branch\nuser: "I've completed the shopping cart feature implementation"\nassistant: "Let me use the architecture-guardian agent to perform a holistic review of the changes and ensure they maintain architectural coherence across the codebase."\n<commentary>Significant code changes were made. Proactively use the architecture-guardian agent to verify the changes don't create silos or architectural inconsistencies.</commentary>\n</example>