As a software architect, you're constantly balancing technical depth with organizational breadth — designing systems that scale, making decisions that stick, and communicating trade-offs to audiences ranging from engineers to executives. These 35 ChatGPT prompts are built specifically for the challenges architects face daily, from sketching out system boundaries to writing airtight ADRs. Use them to think faster, communicate clearer, and lead with more confidence.
System Design and Architecture Patterns
I'm designing a [type of system, e.g. real-time notification service] that needs to handle [scale/constraints]. Walk me through 2-3 architectural patterns that would fit this use case, including the trade-offs of each. Recommend one and explain your reasoning.
Help me design the high-level architecture for a [domain, e.g. multi-tenant SaaS platform]. Include the major components, how they interact, and where the likely bottlenecks or failure points are. Format it as a component breakdown with notes.
I need to choose between a monolithic and microservices architecture for [project description]. Given our team size of [X], expected traffic of [Y], and deployment frequency of [Z], which approach makes more sense and why?
Explain the event-driven architecture pattern to me as if I need to justify it to a skeptical CTO. Cover when it's the right choice, what problems it solves, and what complexity it introduces.
We're building a [system type] and debating whether to use CQRS and event sourcing. Explain both patterns, describe when using them together makes sense, and outline the operational overhead we should expect.
Technology Evaluation and Decision Making
I need to evaluate [Technology A] vs [Technology B] for [specific use case]. Create a structured comparison covering performance, scalability, ecosystem maturity, operational complexity, cost, and community support. Conclude with a recommendation.
We are considering adopting [new technology/framework] into our stack. Help me build a technology radar entry for it: what quadrant it belongs in (adopt, trial, assess, hold), the key risks, and the conditions under which we should move forward.
Our team is evaluating message brokers for a high-throughput event pipeline. Compare Kafka, RabbitMQ, and AWS SQS/SNS across durability, ordering guarantees, throughput, and operational burden. Which fits best for [our specific scenario]?
I need to make a build-vs-buy decision for [component, e.g. authentication system]. Walk me through a structured framework for this decision and apply it to our context: [team size, budget range, timeline, existing stack].
Help me write a technology evaluation matrix for selecting a [database / API gateway / CI-CD tool]. Include the evaluation criteria, a scoring rubric, and how to weight each criterion based on our priorities: [list priorities].
Technical Documentation and ADRs
Write an Architecture Decision Record (ADR) for the decision to [e.g. adopt GraphQL over REST for our public API]. Use the standard ADR format: title, status, context, decision, consequences. Be specific and include the alternatives we considered.
I made the decision to [architectural decision]. Help me document the rationale in a way that will still make sense to a new engineer joining the team two years from now. Include the constraints we were under at the time and what would cause us to revisit this decision.
Create a system architecture overview document for [system name]. Include: purpose, key components, data flow, external dependencies, deployment model, and known limitations. Audience is mid-level engineers joining the team.
We need to document our integration architecture for [system]. Write a technical integration guide that covers authentication, key endpoints or events, error handling expectations, and SLA commitments. Tone should be precise and practical.
Help me create a living architecture diagram description (in text/Mermaid format) for a [system type]. Include services, databases, message queues, and external APIs. Add annotations for data flow direction and synchronous vs asynchronous communication.
Cross-Team Communication and Stakeholder Alignment
I need to present a proposed architecture change to non-technical stakeholders. Help me translate [technical decision, e.g. migrating from a monolith to microservices] into business terms, focusing on risk reduction, speed of delivery, and cost impact.
Write a one-pager for engineering leadership explaining why we need to invest in [technical initiative, e.g. service mesh adoption]. Cover the problem we're solving, the proposed solution, timeline, estimated cost, and the risk of not acting.
I need to align two engineering teams with conflicting preferences on [e.g. API design standards]. Help me draft a discussion framework that acknowledges both perspectives, surfaces the real trade-offs, and guides the team toward a consensus decision.
Help me write an RFC (Request for Comments) for [proposed change, e.g. moving to a new deployment pipeline]. Include background, motivation, proposed solution, alternatives considered, and open questions. Format it for an internal engineering audience.
I have to push back on a stakeholder request to [e.g. add a feature that creates serious architectural debt]. Help me draft a response that is diplomatic, technically grounded, and proposes an alternative path forward.
Code Quality and Engineering Standards
Help me define a set of architectural fitness functions for [system type]. These should be automatable checks that verify our architecture stays aligned with our principles over time. Include examples for coupling, test coverage, dependency rules, and performance budgets.
I want to establish API design standards for our engineering org. Draft a concise API design guideline covering naming conventions, versioning strategy, error response formats, pagination, and authentication patterns. Include a do/don't example for each.
We are seeing architectural drift in our codebase — teams are making local decisions that conflict with our intended design. Help me design a lightweight architectural governance process that doesn't slow teams down but keeps the big picture coherent.
Create a code review checklist specifically for architecture-level concerns. Include items related to separation of concerns, dependency direction, error handling strategy, observability hooks, and adherence to our defined patterns.
Help me write engineering principles for our team that will guide technical decision-making. We value [e.g. simplicity, operability, incremental delivery]. Turn these values into 6-8 actionable principles with a short explanation and example for each.
Scalability, Performance and Reliability
Our [service/system] is experiencing performance degradation under load. Walk me through a systematic approach to diagnosing the bottleneck, starting from observability signals and working down to code and infrastructure-level causes.
Help me design a caching strategy for [system type] that handles [read/write pattern]. Include cache placement (client, CDN, application, database), eviction policy, cache invalidation approach, and how to handle cache stampedes.
I need to design for 10x our current traffic without a full rewrite. Review our current architecture: [describe it briefly]. Identify the three highest-impact changes we could make to improve scalability and explain the expected gains from each.
Design a reliability strategy for a [service type] with an SLA target of [e.g. 99.9%]. Include fault tolerance patterns (retries, circuit breakers, fallbacks), deployment strategies to reduce blast radius, and how we'd measure and report on availability.
Help me conduct a chaos engineering planning exercise for [system]. Identify the top 5 failure scenarios we should test, how we would safely inject each failure in production-like conditions, and what steady-state metrics we'd monitor during each experiment.
Security and Compliance Architecture
Conduct a threat modeling exercise for [system/feature description] using the STRIDE framework. Identify threats in each category, rate their severity, and suggest a mitigation for each high-severity threat.
Help me design a zero-trust security architecture for [system type]. Cover identity verification, network segmentation, least-privilege access controls, and how each principle maps to specific implementation decisions in our stack: [describe stack].
We need to achieve [compliance standard, e.g. SOC 2 Type II / GDPR / HIPAA] compliance for our platform. Create an architecture checklist of the technical controls we need to implement, organized by control domain.
Design a secrets management strategy for a [cloud-native / hybrid] environment. Cover secret storage, rotation policies, access control, audit logging, and how secrets are injected into services at runtime without being exposed in code or config files.
I need to present our security architecture to an external auditor. Help me write a security architecture narrative for [system] that covers our defense-in-depth approach, data classification, encryption strategy, access control model, and incident response posture.
Get All 35 Prompts in One Place
If these prompts were useful, I've compiled all 35 into a ready-to-use toolkit with bonus prompts and usage notes.
Get the complete AI Prompt Toolkit for this profession →
Works with ChatGPT, Claude, and DeepSeek.
Top comments (0)