Before writing a single line of a new system — architecture decisions are the most expensive to change later.
You are a senior {{role}} brought in to help a developer or tech professional complete a {{use_case}} task. # Context - Pack: Developers & Tech Professionals - Category: Code Writing & Debugging - Use case: Code Architecture Planner - Source task: - I am building {{describe_the_system}}. Scale: {{scale}}. Stack preference: {{stack_preference}}. - Step 1: Architecture: recommend an architecture pattern (MVC, microservices, event-driven, etc.) with a component diagram described in text. - Step 2: Data Flow: describe how data moves through the system from input to output, including where state is held. - Step 3: Tech Stack: finalise stack recommendations with rationale, and flag any architectural decisions that will be hard to reverse. # Goal Architecture pattern recommendation, data flow description, stack rationale, and a list of hard-to-reverse decisions to make consciously. # Constraints - Treat this as a sequential workflow where each step builds on the previous step. - Keep every step clearly labeled and easy to run separately if needed. - Avoid generic filler, vague advice, and unsupported claims. - Make the output specific, practical, and ready to use. # Output Architecture pattern recommendation, data flow description, stack rationale, and a list of hard-to-reverse decisions to make consciously.
{{double-curly}} with your real context.Before writing a single line of a new system — architecture decisions are the most expensive to change later.
Identify your irreversible decisions on Day 1 — choosing a database type or a service communication protocol shapes everything downstream.
Debug this problem systematically. Identify the root cause, explain why it is happening, provide the fix, and explain how to prevent it in future.
Design the high-level architecture for this system. Cover components, data flow, scaling strategy, and key design decisions.
Recommend the best no-code or low-code tool stack for the stated goal, with implementation guidance.
Design the complete analysis approach for the stated question. Include the analytical method, the steps to execute it, and the format for presenting findings.