Prompt lesson · 24 prompts
Software Architecture Design prompts for CTOs (Chief Technology Officers)
24 ready-to-use prompts from our AI for CTOs (Chief Technology Officers) course. Copy one, fill in the {{placeholders}}, and paste it into ChatGPT, Claude, Gemini or any other AI.
Analyze System Performance
Use this when you need to assess and optimize the performance of a software system, including identifying bottlenecks and recommending improvements.
Role You are a performance engineering expert with deep knowledge of system optimization. Your goal is to provide a thorough performance analysis and actionable recommendations for improvement.
Context you provide
- {{system_type}}: e.g., data processing application, real-time messaging app, or online retail platform.
- {{performance_goals}}: target metrics like response time, throughput, or resource utilization (optional).
- {{current_metrics}}: any existing performance data or known issues (optional).
Instructions
- If any required context is missing, ask for it before proceeding.
- Analyze the performance requirements for the {{system_type}}, discussing key factors contributing to optimal performance.
- Evaluate the system's performance, identifying bottlenecks and recommending strategies for optimizing response times and resource utilization.
- Consider factors like network latency, scalability, and load handling, and propose architectural changes if needed.
- Provide a set of metrics to track for effective performance monitoring.
Output format Provide a structured analysis with sections: Performance Requirements, Current Performance Assessment, Bottlenecks, Recommendations, and Monitoring Metrics. Use bullet points and tables where helpful. Keep the tone technical and data-driven.
Guardrails
- Do not invent specific performance numbers; if unsure, ask for actual data.
- Flag any assumptions about the system's architecture or workload.
- Stay within the scope of performance analysis; do not redesign unrelated parts of the system.
Example {{system_type}} = "real-time messaging app", {{performance_goals}} = "p99 latency under 200ms", {{current_metrics}} = "average response time 500ms under peak load".
Open this prompt Analysis · Advanced
API-First Design Strategy Plan
Use this when you need to develop a strategic plan for adopting an API-first design philosophy to improve system integration, scalability, and reusability.
Role You are a senior technical strategist who helps organisations adopt an API-first design philosophy to ensure scalability, reusability, and seamless integration across systems.
Context you provide
- {{software_type_or_system}}: The core system you are designing for (e.g., inventory management, customer support tool).
- {{current_integration_challenges}}: Pain points with existing integrations, data silos, or scaling issues.
- {{business_goals}}: What you aim to achieve (e.g., faster partner integrations, microservices readiness).
Instructions
- Ask for any missing details (e.g., tech stack, team size, timeline).
- Evaluate the benefits of API-first design for the given context, quantifying potential improvements.
- Identify the top 3-5 challenges in implementation (e.g., versioning, security, documentation) and suggest mitigation strategies.
- Create a step-by-step implementation roadmap covering design principles, tooling (e.g., OpenAPI, GraphQL), and governance.
- Include best practices for API documentation, testing, and versioning tailored to the system.
Output format A strategic plan with sections: Benefits Analysis, Challenges & Mitigations, Implementation Roadmap (phases with milestones), and Recommended Tools. Use headings and bullet points.
Guardrails
- Do not recommend specific vendors without justification; focus on patterns and standards.
- Flag any assumptions about team capability or existing architecture.
- Stay within API-first design – do not expand into full system architecture unless relevant.
Example {{software_type_or_system: "legacy CRM with custom integrations", current_integration_challenges: "Manual data sync, brittle point-to-point connections", business_goals: "Reduce integration time by 50%, enable partner ecosystem"}}
Open this prompt Planning · Advanced
Architecture Documentation and Communication
Use this when you need to create clear documentation and summaries of software architecture for different audiences.
Open this prompt Communication · Intermediate
CI/CD Pipeline Blueprint for CTOs
Use this when you need to design or improve a continuous integration and continuous deployment pipeline for faster, more reliable software releases.
Open this prompt Planning · Advanced
Cloud-Native Architecture Design
Use this when you want to design a cloud-native architecture for an application, including migration steps and tool recommendations.
Open this prompt Planning · Advanced
Containerization Strategy Guide
Use this when you need to understand containerization benefits, implementation steps, scalability, and security for your software.
Open this prompt Research · Intermediate
Create High-Level System Architecture
Use this when you need a high-level architectural overview of a software system, including components and interactions.
Open this prompt Writing · Intermediate
Data Lake Architecture
Use this when you need to design or evaluate a scalable data lake architecture for advanced analytics, including performance, security, and machine learning integration.
Open this prompt Planning · Advanced
Data Model Design
Use this when you need to design the data structure for a software system, including entities, relationships, and attributes.
Open this prompt Creating · Intermediate
Design Fault-Tolerant Error Handling
Use this when you need to design or improve error handling and fault tolerance for a software system.
Open this prompt Writing · Advanced
Design Intuitive System Interfaces
Use this when you need to define user interfaces or component interactions for a software system, focusing on usability and efficiency.
Open this prompt Writing · Intermediate
Design Reactive System Architecture
Use this when you need to design a reactive system architecture that is responsive, resilient, elastic, and message-driven for a software application.
Open this prompt Writing · Advanced
Domain-Driven Design Guidance
Use this when you need expert guidance on applying Domain-Driven Design principles to a software project for better maintainability and business alignment.
Open this prompt Analysis · Advanced
Event-Driven Architecture Design Guide
Use this when you need expert guidance on designing a scalable, responsive event-driven system.
Open this prompt Planning · Advanced
Microservices Architecture Strategy
Use this when you are breaking down a monolith or designing a modular microservices system.
Open this prompt Planning · Advanced
Plan PWA Implementation Strategy
Use this when you need to plan and implement Progressive Web Applications to enhance user engagement and performance.
Open this prompt Planning · Intermediate
Plan System Integration Strategy
Use this when you need to plan the integration of a software system with existing services, including data formats, stakeholders, and risk assessment.
Open this prompt Planning · Advanced
Scalability and Extensibility Planning
Use this when you need to design or optimize a software system to handle future growth and evolving requirements.
Open this prompt Planning · Advanced
Security Design for Software Systems
Use this when you need to design or enhance security measures within a software system's architecture.
Open this prompt Planning · Advanced
Serverless Architecture Evaluation
Use this when you are considering serverless architecture for a new or existing application and need to evaluate benefits, costs, and trade-offs.
Open this prompt Analysis · Advanced
Service-Oriented Architecture Explained
Use this when you need to understand or explain the principles, benefits, and implementation steps of Service-Oriented Architecture (SOA) for your organization.
Open this prompt Learning · Intermediate
Software Component Identification
Use this when you need to identify the key components and modules for a software system's architecture.
Open this prompt Analysis · Intermediate
System Requirements Analysis and Prioritization
Use this when you need to analyze, categorize, and prioritize functional and non-functional requirements for a software system.
Open this prompt Analysis · Intermediate
Technology Stack Selection and Evaluation
Use this when you need to evaluate and select technologies, frameworks, or platforms for a software system.
Open this prompt Research · Intermediate