Code Architecture Review
Opus can process multiple files simultaneously and cross-reference patterns across them. The severity rating forces prioritization instead of a flat list. Asking for concrete code fixes rather than just descriptions produces actionable output that developers can implement immediately.
Review the following codebase architecture for a {{projectType}} application. **Tech stack:** {{techStack}} **Scale:** {{scaleRequirements}} **Team size:** {{teamSize}} engineers I'll provide the key files. For each architectural concern, reference the specific file and line where the issue exists. Review for: 1. **Separation of concerns** — Are responsibilities cleanly divided? Any God objects or modules doing too much? 2. **Scalability bottlenecks** — What breaks first at 10x current load? 3. **Error handling gaps** — Where can failures cascade or go unhandled? 4. **Testing friction** — What's hard to test due to tight coupling or hidden dependencies? 5. **Security surface** — Auth bypasses, injection points, data exposure risks For each issue found, provide: - Severity: critical / high / medium / low - The specific anti-pattern or violation - A concrete fix with code example <codebase> {{codebaseFiles}} </codebase>
Variables to customize
Why this prompt works
Opus can process multiple files simultaneously and cross-reference patterns across them. The severity rating forces prioritization instead of a flat list. Asking for concrete code fixes rather than just descriptions produces actionable output that developers can implement immediately.
Save this prompt to your library
Organize, version, and access your best prompts across ChatGPT, Claude, and Cursor.
Related prompts
Forcing the agent to plan before acting prevents premature execution and wasted steps. Explicit dependency mapping enables parallel execution and catches logical gaps early.
Tool Selection AgentThe ReAct pattern (Reason + Act) creates an explicit reasoning trace that improves tool selection accuracy. The error-handling rule prevents infinite retry loops.
Prompt CompressorExplicitly requiring all functional requirements to be preserved prevents the model from over-compressing and losing critical instructions.
Memory Management AgentExplicit memory read/write instructions create agents that improve over time. Categorization keeps memories organized, and the deduplication rule prevents context bloat.