Claude Prompt for Creating a Software Architecture
Designing a software architecture is a fundamental step that determines the maintainability, scalability, and robustness of a project. Claude excels in this area thanks to its ability to analyze complex technical constraints, propose suitable architectural patterns, and anticipate design issues before they arise in production. Whether you are starting a new project from scratch, refactoring a monolith into microservices, or evaluating different technology options, Claude can support you at every stage of the decision-making process. By providing precise context about your constraints (team, budget, expected traffic, existing stack), you get argued architectural recommendations, component diagrams, structured ADRs (Architecture Decision Records), and concrete migration plans. The iterative approach with Claude allows you to explore multiple alternatives, compare their trade-offs, and converge towards a solution that balances pragmatism and technical excellence. It's like having a senior software architect available at all times to challenge your ideas and enrich your thinking.
Paste in your AI
Paste this prompt in ChatGPT, Claude or Gemini and customize the variables in brackets.
You are a senior software architect with 15 years of experience in large-scale distributed systems. I need to design the architecture for a new system.
Project Context
- Project Name: [PROJECT_NAME]
- Description: [functional description in 2-3 sentences]
- Target Users: [type and estimated number]
- Expected Load: [requests/second, concurrent users]
- Constraints: [budget, team, deadlines, regulatory compliance]
- Existing Stack: [technologies already in place, if applicable]
What I Expect from You
-
Overview: Propose an architecture with an ASCII art diagram showing the main components and their interactions.
-
Technology Choices: For each layer (frontend, backend, database, infrastructure, messaging), recommend a technology with justification and alternatives considered.
-
Architectural Patterns: Identify relevant design patterns (CQRS, Event Sourcing, Saga, Circuit Breaker, etc.) and explain why they apply here.
-
ADRs (Architecture Decision Records): Write 3 ADRs for the most impactful decisions, in the format: Context → Decision → Consequences.
-
Risks and Mitigations: List the top 5 architectural risks with concrete mitigation strategies.
-
Evolution Plan: Describe how this architecture can evolve over 6, 12, and 24 months.
Be pragmatic: favor simplicity when sufficient, and complexity only when justified by constraints.
Personalize this prompt with Léa
Answer 3 questions and Léa tailors the prompt to your situation.
Why this prompt works
This prompt works because it assigns Claude a precise expert role and structures the request into concrete, actionable deliverables. The detailed context (load, constraints, stack) allows Claude to calibrate its recommendations instead of giving generic answers. The final directive on pragmatism steers Claude towards realistic solutions rather than theoretically perfect but unfeasible architectures.
Use Cases
Variants
Expected Output
You will get a complete architecture document including a component diagram, argued technology recommendations for each layer, formalized ADRs, and a progressive evolution plan. The result is directly usable as a basis for discussion with your technical team or as a reference document for development.
Frequently Asked Questions
How do I provide enough context to Claude to get a relevant architecture?
The quality of the proposed architecture directly depends on the context you provide. At a minimum, specify: expected user numbers and peak loads, technical constraints (imposed stack, hosting, budget), non-functional requirements (latency, availability, GDPR compliance), team size and skills, and existing systems the architecture must integrate with. The more specific you are about your real-world constraints, the more actionable and realistic the recommendations will be.
Can Claude help me choose between a monolith and microservices?
Yes, and this is one of its strengths. Describe your context (team size, domain complexity, deployment constraints) and explicitly ask for a comparative analysis. Claude will evaluate the trade-offs in terms of operational complexity, development velocity, independent scalability, and infrastructure cost. It can also suggest intermediate approaches like modular monoliths or macro-services, which are often more suitable than the extremes.
How do I iterate with Claude to refine an architecture?
Proceed in several exchanges. Start with an initial global proposal, then dive deeper component by component. You can challenge each decision by asking, "What are the alternatives to this choice and their trade-offs?". Submit load or failure scenarios to test the design's robustness. Also, ask Claude to play the role of a critical reviewer looking for flaws in the proposed architecture. This dialectical approach produces far more robust results than a single prompt.
Learn more
Check the full skill on Prompt Guide to master this technique from A to Z.
View on Prompt Guide📬 Get new prompts every week
Join our newsletter and never miss a prompt.
Similar Prompts
Generate Mocks and Fixtures for Your Automated Tests
A prompt to automatically generate realistic mocks, stubs and data fixtures adapted to your test framework and use cases.
Automatically Generate Unit Tests with AI
Automatically generate an exhaustive unit test suite covering nominal cases, edge cases, and error cases for any source code.
Create a Python Automation Script
Create a professional Python automation script with CLI configuration, structured logging, error handling, and tests.
Analyze and Optimize Algorithmic Complexity
Analyze the Big O complexity of your algorithms and optimize them with appropriate data structures and more efficient algorithms.