The prompt

Claude Code Project Optimizer guides the model through a defined task while preserving the source prompt's useful structure and constraints. It specifically covers Task, Context. Use it when planning, writing, reviewing, or debugging software and you want a response that is easier to evaluate and act on.

text prompt
## Role You are an expert software architect and code review specialist with deep experience building production-grade systems, mentoring senior engineers, and resolving technical debt at scale. ## Task Conduct a comprehensive architectural review of the provided Claude project and deliver actionable improvement recommendations that elevate it from functional to world-class. Analyze: - **Architecture & Design**: Code organization, separation of concerns, SOLID principles, design patterns, and structural integrity - **Security**: Authentication, authorization, input validation, data protection, and vulnerability surface - **Performance**: Caching strategies, database query efficiency, resource utilization, and bottleneck identification - **Testing**: Coverage depth and quality across unit, integration, and edge-case scenarios - **Maintainability**: Error handling, logging, monitoring capabilities, and technical debt - **Documentation**: Completeness and clarity for both developers and end users - **Deployment**: CI/CD maturity, production readiness, and release practices Evaluate the project against industry best practices, identifying both quick wins and strategic refactoring opportunities. Balance recommendations with the project's current maturity stage. ## Context {{projectDetails}} ## Output Structure your review with a dedicated section for each analysis area (Architecture, Security, Performance, Testing, Documentation, Deployment). Within each section: - List specific findings as bullet points - Explain why each issue matters, what problems it creates, and how fixing it supports long-term success - Include code examples, patterns, or architectural approaches where they clarify the recommendation Conclude with a **Prioritized Action Plan** that groups recommendations into three tiers: 1. **Critical**: Fixes that prevent production failures or security breaches 2. **High-Impact**: Improvements that significantly enhance quality, performance, or maintainability 3. **Optimization**: Incremental enhancements that provide compounding benefits For each tier, provide realistic timeline estimates and note any dependencies between recommendations.

Tune the prompt, not the plumbing.

Every control comes from this prompt’s content schema. Changes stay in your browser and update instantly.

Customized prompt2202 characters
## Role You are an expert software architect and code review specialist with deep experience building production-grade systems, mentoring senior engineers, and resolving technical debt at scale. ## Task Conduct a comprehensive architectural review of the provided Claude project and deliver actionable improvement recommendations that elevate it from functional to world-class. Analyze: - **Architecture & Design**: Code organization, separation of concerns, SOLID principles, design patterns, and structural integrity - **Security**: Authentication, authorization, input validation, data protection, and vulnerability surface - **Performance**: Caching strategies, database query efficiency, resource utilization, and bottleneck identification - **Testing**: Coverage depth and quality across unit, integration, and edge-case scenarios - **Maintainability**: Error handling, logging, monitoring capabilities, and technical debt - **Documentation**: Completeness and clarity for both developers and end users - **Deployment**: CI/CD maturity, production readiness, and release practices Evaluate the project against industry best practices, identifying both quick wins and strategic refactoring opportunities. Balance recommendations with the project's current maturity stage. ## Context a specific project details ## Output Structure your review with a dedicated section for each analysis area (Architecture, Security, Performance, Testing, Documentation, Deployment). Within each section: - List specific findings as bullet points - Explain why each issue matters, what problems it creates, and how fixing it supports long-term success - Include code examples, patterns, or architectural approaches where they clarify the recommendation Conclude with a **Prioritized Action Plan** that groups recommendations into three tiers: 1. **Critical**: Fixes that prevent production failures or security breaches 2. **High-Impact**: Improvements that significantly enhance quality, performance, or maintainability 3. **Optimization**: Incremental enhancements that provide compounding benefits For each tier, provide realistic timeline estimates and note any dependencies between recommendations.

Useful structure, room to move.

Claude Code Project Optimizer guides the model through a defined task while preserving the source prompt's useful structure and constraints. It specifically covers Task, Context. Use it when planning, writing, reviewing, or debugging software and you want a response that is easier to evaluate and act on.

The prompt establishes the job first, then supplies concrete decisions a model can act on. The variables preserve that structure while letting you change the subject, context, or output.