PROFESSION 24 · FREE PROFESSIONAL RESOURCE
Cloud Engineer, DevOps & AI Infrastructure Specialist: 120 AI Prompts
A practical, self-contained guide covering cloud architecture, AWS/Azure/GCP, Linux, containers, Kubernetes, CI/CD, Terraform, security, observability, reliability, FinOps and remote-career delivery.
12 modules · 120 searchable shortcodes · Copy-ready templatesHow to use: Choose a module, search a task or shortcode (for example, CLOUD-043), open its template, replace all [PLACEHOLDERS], and click Copy Prompt. Never paste live credentials, private customer data or unredacted security logs. Review and test every AI recommendation in a safe environment. These CLOUD IDs are library references, not executable WordPress shortcodes.
Quick-start tutorial
- Define the service, provider, business goal, deployment environment and constraints.
- Search for the most specific task, read the usage note, and replace placeholders with sanitized facts.
- Request a plan first. Check IAM, failure modes, cost estimates, auditability, testing and rollback.
- Validate commands and configurations in a development environment and obtain approval before production changes.
- Capture evidence in a portfolio case study: brief → architecture → code → tests → result → lessons learned.
No matching prompts. Try fewer words or reset filters.
Discovery & Architecture
Infrastructure discovery questionnaire
Use this when planning or reviewing infrastructure discovery questionnaire. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Infrastructure discovery questionnaire** for [PROJECT / CLIENT], which is a small SaaS product. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a prioritized decision table, tailored specifically to infrastructure discovery questionnaire. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Cloud migration readiness assessment
Use this when planning or reviewing cloud migration readiness assessment. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Cloud migration readiness assessment** for [PROJECT / CLIENT], which is an e-commerce storefront. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a step-by-step implementation plan, tailored specifically to cloud migration readiness assessment. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Workload inventory template
Use this when planning or reviewing workload inventory template. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Workload inventory template** for [PROJECT / CLIENT], which is an internal enterprise application. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a checklist with acceptance criteria, tailored specifically to workload inventory template. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Functional and nonfunctional requirements
Use this when planning or reviewing functional and nonfunctional requirements. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Functional and nonfunctional requirements** for [PROJECT / CLIENT], which is a data processing service. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a risk register and mitigations, tailored specifically to functional and nonfunctional requirements. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Shared responsibility mapping
Use this when planning or reviewing shared responsibility mapping. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Shared responsibility mapping** for [PROJECT / CLIENT], which is a multi-tenant API. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a reproducible runbook, tailored specifically to shared responsibility mapping. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Reference architecture comparison
Use this when planning or reviewing reference architecture comparison. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Reference architecture comparison** for [PROJECT / CLIENT], which is a remote-first startup. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a comparison matrix with trade-offs, tailored specifically to reference architecture comparison. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Service dependency map
Use this when planning or reviewing service dependency map. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Service dependency map** for [PROJECT / CLIENT], which is a regulated business workload. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a configuration outline with explanations, tailored specifically to service dependency map. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Environment separation blueprint
Use this when planning or reviewing environment separation blueprint. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Environment separation blueprint** for [PROJECT / CLIENT], which is an event-driven backend. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a validation and rollback procedure, tailored specifically to environment separation blueprint. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Architecture decision record
Use this when planning or reviewing architecture decision record. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Architecture decision record** for [PROJECT / CLIENT], which is a customer-facing web platform. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a structured report with clear owners, tailored specifically to architecture decision record. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Cloud implementation roadmap
Use this when planning or reviewing cloud implementation roadmap. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Cloud implementation roadmap** for [PROJECT / CLIENT], which is a distributed engineering team. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a concise client-ready deliverable, tailored specifically to cloud implementation roadmap. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
AWS, Azure & Google Cloud
AWS landing zone plan
Use this when planning or reviewing aws landing zone plan. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **AWS landing zone plan** for [PROJECT / CLIENT], which is a small SaaS product. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a step-by-step implementation plan, tailored specifically to aws landing zone plan. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Azure subscription governance plan
Use this when planning or reviewing azure subscription governance plan. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Azure subscription governance plan** for [PROJECT / CLIENT], which is an e-commerce storefront. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a checklist with acceptance criteria, tailored specifically to azure subscription governance plan. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Google Cloud organization setup
Use this when planning or reviewing google cloud organization setup. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Google Cloud organization setup** for [PROJECT / CLIENT], which is an internal enterprise application. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a risk register and mitigations, tailored specifically to google cloud organization setup. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Cross-cloud service comparison
Use this when planning or reviewing cross-cloud service comparison. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Cross-cloud service comparison** for [PROJECT / CLIENT], which is a data processing service. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a reproducible runbook, tailored specifically to cross-cloud service comparison. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Managed compute selection matrix
Use this when planning or reviewing managed compute selection matrix. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Managed compute selection matrix** for [PROJECT / CLIENT], which is a multi-tenant API. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a comparison matrix with trade-offs, tailored specifically to managed compute selection matrix. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Object storage design review
Use this when planning or reviewing object storage design review. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Object storage design review** for [PROJECT / CLIENT], which is a remote-first startup. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a configuration outline with explanations, tailored specifically to object storage design review. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Virtual network segmentation plan
Use this when planning or reviewing virtual network segmentation plan. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Virtual network segmentation plan** for [PROJECT / CLIENT], which is a regulated business workload. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a validation and rollback procedure, tailored specifically to virtual network segmentation plan. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Cloud identity role inventory
Use this when planning or reviewing cloud identity role inventory. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Cloud identity role inventory** for [PROJECT / CLIENT], which is an event-driven backend. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a structured report with clear owners, tailored specifically to cloud identity role inventory. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Cloud database selection
Use this when planning or reviewing cloud database selection. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Cloud database selection** for [PROJECT / CLIENT], which is a customer-facing web platform. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a concise client-ready deliverable, tailored specifically to cloud database selection. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Disaster recovery region selection
Use this when planning or reviewing disaster recovery region selection. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Disaster recovery region selection** for [PROJECT / CLIENT], which is a distributed engineering team. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a prioritized decision table, tailored specifically to disaster recovery region selection. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Linux & Scripting
Linux server baseline checklist
Use this when planning or reviewing linux server baseline checklist. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Linux server baseline checklist** for [PROJECT / CLIENT], which is a small SaaS product. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a checklist with acceptance criteria, tailored specifically to linux server baseline checklist. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Shell script review
Use this when planning or reviewing shell script review. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Shell script review** for [PROJECT / CLIENT], which is an e-commerce storefront. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a risk register and mitigations, tailored specifically to shell script review. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Systemd service troubleshooting
Use this when planning or reviewing systemd service troubleshooting. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Systemd service troubleshooting** for [PROJECT / CLIENT], which is an internal enterprise application. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a reproducible runbook, tailored specifically to systemd service troubleshooting. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Disk utilization investigation
Use this when planning or reviewing disk utilization investigation. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Disk utilization investigation** for [PROJECT / CLIENT], which is a data processing service. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a comparison matrix with trade-offs, tailored specifically to disk utilization investigation. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Linux permissions audit
Use this when planning or reviewing linux permissions audit. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Linux permissions audit** for [PROJECT / CLIENT], which is a multi-tenant API. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a configuration outline with explanations, tailored specifically to linux permissions audit. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Secure SSH configuration review
Use this when planning or reviewing secure ssh configuration review. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Secure SSH configuration review** for [PROJECT / CLIENT], which is a remote-first startup. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a validation and rollback procedure, tailored specifically to secure ssh configuration review. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Cron job reliability checklist
Use this when planning or reviewing cron job reliability checklist. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Cron job reliability checklist** for [PROJECT / CLIENT], which is a regulated business workload. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a structured report with clear owners, tailored specifically to cron job reliability checklist. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Log rotation plan
Use this when planning or reviewing log rotation plan. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Log rotation plan** for [PROJECT / CLIENT], which is an event-driven backend. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a concise client-ready deliverable, tailored specifically to log rotation plan. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Python automation script design
Use this when planning or reviewing python automation script design. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Python automation script design** for [PROJECT / CLIENT], which is a customer-facing web platform. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a prioritized decision table, tailored specifically to python automation script design. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Linux patching runbook
Use this when planning or reviewing linux patching runbook. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Linux patching runbook** for [PROJECT / CLIENT], which is a distributed engineering team. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a step-by-step implementation plan, tailored specifically to linux patching runbook. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Containers & Docker
Dockerfile optimization review
Use this when planning or reviewing dockerfile optimization review. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Dockerfile optimization review** for [PROJECT / CLIENT], which is a small SaaS product. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a risk register and mitigations, tailored specifically to dockerfile optimization review. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Multi-stage container build
Use this when planning or reviewing multi-stage container build. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Multi-stage container build** for [PROJECT / CLIENT], which is an e-commerce storefront. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a reproducible runbook, tailored specifically to multi-stage container build. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Container image vulnerability review
Use this when planning or reviewing container image vulnerability review. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Container image vulnerability review** for [PROJECT / CLIENT], which is an internal enterprise application. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a comparison matrix with trade-offs, tailored specifically to container image vulnerability review. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Docker Compose development stack
Use this when planning or reviewing docker compose development stack. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Docker Compose development stack** for [PROJECT / CLIENT], which is a data processing service. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a configuration outline with explanations, tailored specifically to docker compose development stack. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Container secret handling plan
Use this when planning or reviewing container secret handling plan. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Container secret handling plan** for [PROJECT / CLIENT], which is a multi-tenant API. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a validation and rollback procedure, tailored specifically to container secret handling plan. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Container startup debugging
Use this when planning or reviewing container startup debugging. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Container startup debugging** for [PROJECT / CLIENT], which is a remote-first startup. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a structured report with clear owners, tailored specifically to container startup debugging. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Image tagging strategy
Use this when planning or reviewing image tagging strategy. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Image tagging strategy** for [PROJECT / CLIENT], which is a regulated business workload. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a concise client-ready deliverable, tailored specifically to image tagging strategy. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Container resource limits
Use this when planning or reviewing container resource limits. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Container resource limits** for [PROJECT / CLIENT], which is an event-driven backend. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a prioritized decision table, tailored specifically to container resource limits. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Registry publishing checklist
Use this when planning or reviewing registry publishing checklist. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Registry publishing checklist** for [PROJECT / CLIENT], which is a customer-facing web platform. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a step-by-step implementation plan, tailored specifically to registry publishing checklist. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Container migration assessment
Use this when planning or reviewing container migration assessment. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Container migration assessment** for [PROJECT / CLIENT], which is a distributed engineering team. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a checklist with acceptance criteria, tailored specifically to container migration assessment. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Kubernetes & Orchestration
Kubernetes cluster architecture
Use this when planning or reviewing kubernetes cluster architecture. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Kubernetes cluster architecture** for [PROJECT / CLIENT], which is a small SaaS product. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a reproducible runbook, tailored specifically to kubernetes cluster architecture. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Deployment manifest review
Use this when planning or reviewing deployment manifest review. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Deployment manifest review** for [PROJECT / CLIENT], which is an e-commerce storefront. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a comparison matrix with trade-offs, tailored specifically to deployment manifest review. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Pod CrashLoopBackOff triage
Use this when planning or reviewing pod crashloopbackoff triage. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Pod CrashLoopBackOff triage** for [PROJECT / CLIENT], which is an internal enterprise application. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a configuration outline with explanations, tailored specifically to pod crashloopbackoff triage. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Readiness and liveness probes
Use this when planning or reviewing readiness and liveness probes. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Readiness and liveness probes** for [PROJECT / CLIENT], which is a data processing service. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a validation and rollback procedure, tailored specifically to readiness and liveness probes. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Kubernetes resource requests and limits
Use this when planning or reviewing kubernetes resource requests and limits. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Kubernetes resource requests and limits** for [PROJECT / CLIENT], which is a multi-tenant API. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a structured report with clear owners, tailored specifically to kubernetes resource requests and limits. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Horizontal pod autoscaling plan
Use this when planning or reviewing horizontal pod autoscaling plan. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Horizontal pod autoscaling plan** for [PROJECT / CLIENT], which is a remote-first startup. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a concise client-ready deliverable, tailored specifically to horizontal pod autoscaling plan. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Ingress and network policy design
Use this when planning or reviewing ingress and network policy design. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Ingress and network policy design** for [PROJECT / CLIENT], which is a regulated business workload. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a prioritized decision table, tailored specifically to ingress and network policy design. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Helm chart review
Use this when planning or reviewing helm chart review. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Helm chart review** for [PROJECT / CLIENT], which is an event-driven backend. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a step-by-step implementation plan, tailored specifically to helm chart review. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Kubernetes secret management
Use this when planning or reviewing kubernetes secret management. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Kubernetes secret management** for [PROJECT / CLIENT], which is a customer-facing web platform. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a checklist with acceptance criteria, tailored specifically to kubernetes secret management. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Cluster upgrade runbook
Use this when planning or reviewing cluster upgrade runbook. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Cluster upgrade runbook** for [PROJECT / CLIENT], which is a distributed engineering team. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a risk register and mitigations, tailored specifically to cluster upgrade runbook. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
CI/CD & Release Engineering
CI pipeline design
Use this when planning or reviewing ci pipeline design. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **CI pipeline design** for [PROJECT / CLIENT], which is a small SaaS product. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a comparison matrix with trade-offs, tailored specifically to ci pipeline design. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
GitHub Actions workflow review
Use this when planning or reviewing github actions workflow review. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **GitHub Actions workflow review** for [PROJECT / CLIENT], which is an e-commerce storefront. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a configuration outline with explanations, tailored specifically to github actions workflow review. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
GitLab CI pipeline template
Use this when planning or reviewing gitlab ci pipeline template. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **GitLab CI pipeline template** for [PROJECT / CLIENT], which is an internal enterprise application. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a validation and rollback procedure, tailored specifically to gitlab ci pipeline template. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Build artifact provenance checklist
Use this when planning or reviewing build artifact provenance checklist. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Build artifact provenance checklist** for [PROJECT / CLIENT], which is a data processing service. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a structured report with clear owners, tailored specifically to build artifact provenance checklist. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Automated testing gates
Use this when planning or reviewing automated testing gates. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Automated testing gates** for [PROJECT / CLIENT], which is a multi-tenant API. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a concise client-ready deliverable, tailored specifically to automated testing gates. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Blue-green release plan
Use this when planning or reviewing blue-green release plan. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Blue-green release plan** for [PROJECT / CLIENT], which is a remote-first startup. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a prioritized decision table, tailored specifically to blue-green release plan. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Canary deployment plan
Use this when planning or reviewing canary deployment plan. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Canary deployment plan** for [PROJECT / CLIENT], which is a regulated business workload. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a step-by-step implementation plan, tailored specifically to canary deployment plan. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Rollback decision tree
Use this when planning or reviewing rollback decision tree. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Rollback decision tree** for [PROJECT / CLIENT], which is an event-driven backend. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a checklist with acceptance criteria, tailored specifically to rollback decision tree. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Release notes generator
Use this when planning or reviewing release notes generator. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Release notes generator** for [PROJECT / CLIENT], which is a customer-facing web platform. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a risk register and mitigations, tailored specifically to release notes generator. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Deployment failure postmortem
Use this when planning or reviewing deployment failure postmortem. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Deployment failure postmortem** for [PROJECT / CLIENT], which is a distributed engineering team. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a reproducible runbook, tailored specifically to deployment failure postmortem. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Terraform & Infrastructure as Code
Terraform module requirements
Use this when planning or reviewing terraform module requirements. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Terraform module requirements** for [PROJECT / CLIENT], which is a small SaaS product. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a configuration outline with explanations, tailored specifically to terraform module requirements. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Terraform code review
Use this when planning or reviewing terraform code review. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Terraform code review** for [PROJECT / CLIENT], which is an e-commerce storefront. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a validation and rollback procedure, tailored specifically to terraform code review. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Remote state backend plan
Use this when planning or reviewing remote state backend plan. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Remote state backend plan** for [PROJECT / CLIENT], which is an internal enterprise application. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a structured report with clear owners, tailored specifically to remote state backend plan. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Infrastructure drift investigation
Use this when planning or reviewing infrastructure drift investigation. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Infrastructure drift investigation** for [PROJECT / CLIENT], which is a data processing service. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a concise client-ready deliverable, tailored specifically to infrastructure drift investigation. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Terraform provider upgrade plan
Use this when planning or reviewing terraform provider upgrade plan. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Terraform provider upgrade plan** for [PROJECT / CLIENT], which is a multi-tenant API. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a prioritized decision table, tailored specifically to terraform provider upgrade plan. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Environment variable architecture
Use this when planning or reviewing environment variable architecture. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Environment variable architecture** for [PROJECT / CLIENT], which is a remote-first startup. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a step-by-step implementation plan, tailored specifically to environment variable architecture. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
IaC policy-as-code controls
Use this when planning or reviewing iac policy-as-code controls. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **IaC policy-as-code controls** for [PROJECT / CLIENT], which is a regulated business workload. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a checklist with acceptance criteria, tailored specifically to iac policy-as-code controls. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
State migration checklist
Use this when planning or reviewing state migration checklist. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **State migration checklist** for [PROJECT / CLIENT], which is an event-driven backend. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a risk register and mitigations, tailored specifically to state migration checklist. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
CloudFormation versus Terraform decision
Use this when planning or reviewing cloudformation versus terraform decision. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **CloudFormation versus Terraform decision** for [PROJECT / CLIENT], which is a customer-facing web platform. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a reproducible runbook, tailored specifically to cloudformation versus terraform decision. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Pull request IaC review rubric
Use this when planning or reviewing pull request iac review rubric. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Pull request IaC review rubric** for [PROJECT / CLIENT], which is a distributed engineering team. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a comparison matrix with trade-offs, tailored specifically to pull request iac review rubric. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Networking, Identity & Security
Zero trust access blueprint
Use this when planning or reviewing zero trust access blueprint. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Zero trust access blueprint** for [PROJECT / CLIENT], which is a small SaaS product. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a validation and rollback procedure, tailored specifically to zero trust access blueprint. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
VPC/VNet routing investigation
Use this when planning or reviewing vpc/vnet routing investigation. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **VPC/VNet routing investigation** for [PROJECT / CLIENT], which is an e-commerce storefront. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a structured report with clear owners, tailored specifically to vpc/vnet routing investigation. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
DNS troubleshooting runbook
Use this when planning or reviewing dns troubleshooting runbook. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **DNS troubleshooting runbook** for [PROJECT / CLIENT], which is an internal enterprise application. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a concise client-ready deliverable, tailored specifically to dns troubleshooting runbook. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
TLS certificate lifecycle plan
Use this when planning or reviewing tls certificate lifecycle plan. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **TLS certificate lifecycle plan** for [PROJECT / CLIENT], which is a data processing service. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a prioritized decision table, tailored specifically to tls certificate lifecycle plan. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Least privilege IAM policy review
Use this when planning or reviewing least privilege iam policy review. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Least privilege IAM policy review** for [PROJECT / CLIENT], which is a multi-tenant API. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a step-by-step implementation plan, tailored specifically to least privilege iam policy review. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Network firewall rule audit
Use this when planning or reviewing network firewall rule audit. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Network firewall rule audit** for [PROJECT / CLIENT], which is a remote-first startup. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a checklist with acceptance criteria, tailored specifically to network firewall rule audit. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Cloud secrets rotation plan
Use this when planning or reviewing cloud secrets rotation plan. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Cloud secrets rotation plan** for [PROJECT / CLIENT], which is a regulated business workload. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a risk register and mitigations, tailored specifically to cloud secrets rotation plan. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Cloud logging retention controls
Use this when planning or reviewing cloud logging retention controls. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Cloud logging retention controls** for [PROJECT / CLIENT], which is an event-driven backend. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a reproducible runbook, tailored specifically to cloud logging retention controls. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Supply chain security checklist
Use this when planning or reviewing supply chain security checklist. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Supply chain security checklist** for [PROJECT / CLIENT], which is a customer-facing web platform. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a comparison matrix with trade-offs, tailored specifically to supply chain security checklist. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Access review procedure
Use this when planning or reviewing access review procedure. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Access review procedure** for [PROJECT / CLIENT], which is a distributed engineering team. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a configuration outline with explanations, tailored specifically to access review procedure. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Observability & Incident Response
Service level indicator design
Use this when planning or reviewing service level indicator design. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Service level indicator design** for [PROJECT / CLIENT], which is a small SaaS product. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a structured report with clear owners, tailored specifically to service level indicator design. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
SLO and error budget policy
Use this when planning or reviewing slo and error budget policy. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **SLO and error budget policy** for [PROJECT / CLIENT], which is an e-commerce storefront. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a concise client-ready deliverable, tailored specifically to slo and error budget policy. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Monitoring dashboard specification
Use this when planning or reviewing monitoring dashboard specification. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Monitoring dashboard specification** for [PROJECT / CLIENT], which is an internal enterprise application. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a prioritized decision table, tailored specifically to monitoring dashboard specification. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Alert fatigue reduction plan
Use this when planning or reviewing alert fatigue reduction plan. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Alert fatigue reduction plan** for [PROJECT / CLIENT], which is a data processing service. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a step-by-step implementation plan, tailored specifically to alert fatigue reduction plan. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Distributed tracing implementation
Use this when planning or reviewing distributed tracing implementation. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Distributed tracing implementation** for [PROJECT / CLIENT], which is a multi-tenant API. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a checklist with acceptance criteria, tailored specifically to distributed tracing implementation. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Incident severity matrix
Use this when planning or reviewing incident severity matrix. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Incident severity matrix** for [PROJECT / CLIENT], which is a remote-first startup. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a risk register and mitigations, tailored specifically to incident severity matrix. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Incident commander runbook
Use this when planning or reviewing incident commander runbook. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Incident commander runbook** for [PROJECT / CLIENT], which is a regulated business workload. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a reproducible runbook, tailored specifically to incident commander runbook. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
On-call handover template
Use this when planning or reviewing on-call handover template. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **On-call handover template** for [PROJECT / CLIENT], which is an event-driven backend. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a comparison matrix with trade-offs, tailored specifically to on-call handover template. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Root cause analysis template
Use this when planning or reviewing root cause analysis template. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Root cause analysis template** for [PROJECT / CLIENT], which is a customer-facing web platform. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a configuration outline with explanations, tailored specifically to root cause analysis template. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Observability coverage gap audit
Use this when planning or reviewing observability coverage gap audit. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Observability coverage gap audit** for [PROJECT / CLIENT], which is a distributed engineering team. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a validation and rollback procedure, tailored specifically to observability coverage gap audit. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Reliability, Backup & Disaster Recovery
Availability risk assessment
Use this when planning or reviewing availability risk assessment. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Availability risk assessment** for [PROJECT / CLIENT], which is a small SaaS product. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a concise client-ready deliverable, tailored specifically to availability risk assessment. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
High availability architecture
Use this when planning or reviewing high availability architecture. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **High availability architecture** for [PROJECT / CLIENT], which is an e-commerce storefront. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a prioritized decision table, tailored specifically to high availability architecture. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Backup policy by data class
Use this when planning or reviewing backup policy by data class. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Backup policy by data class** for [PROJECT / CLIENT], which is an internal enterprise application. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a step-by-step implementation plan, tailored specifically to backup policy by data class. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Restore drill plan
Use this when planning or reviewing restore drill plan. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Restore drill plan** for [PROJECT / CLIENT], which is a data processing service. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a checklist with acceptance criteria, tailored specifically to restore drill plan. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
RPO and RTO workshop
Use this when planning or reviewing rpo and rto workshop. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **RPO and RTO workshop** for [PROJECT / CLIENT], which is a multi-tenant API. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a risk register and mitigations, tailored specifically to rpo and rto workshop. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Chaos experiment proposal
Use this when planning or reviewing chaos experiment proposal. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Chaos experiment proposal** for [PROJECT / CLIENT], which is a remote-first startup. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a reproducible runbook, tailored specifically to chaos experiment proposal. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Capacity forecasting
Use this when planning or reviewing capacity forecasting. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Capacity forecasting** for [PROJECT / CLIENT], which is a regulated business workload. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a comparison matrix with trade-offs, tailored specifically to capacity forecasting. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Load testing test plan
Use this when planning or reviewing load testing test plan. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Load testing test plan** for [PROJECT / CLIENT], which is an event-driven backend. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a configuration outline with explanations, tailored specifically to load testing test plan. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Business continuity checklist
Use this when planning or reviewing business continuity checklist. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Business continuity checklist** for [PROJECT / CLIENT], which is a customer-facing web platform. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a validation and rollback procedure, tailored specifically to business continuity checklist. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Reliability improvement backlog
Use this when planning or reviewing reliability improvement backlog. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Reliability improvement backlog** for [PROJECT / CLIENT], which is a distributed engineering team. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a structured report with clear owners, tailored specifically to reliability improvement backlog. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
FinOps & Performance Optimization
Cloud cost allocation taxonomy
Use this when planning or reviewing cloud cost allocation taxonomy. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Cloud cost allocation taxonomy** for [PROJECT / CLIENT], which is a small SaaS product. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a prioritized decision table, tailored specifically to cloud cost allocation taxonomy. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Cloud billing anomaly investigation
Use this when planning or reviewing cloud billing anomaly investigation. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Cloud billing anomaly investigation** for [PROJECT / CLIENT], which is an e-commerce storefront. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a step-by-step implementation plan, tailored specifically to cloud billing anomaly investigation. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Reserved capacity comparison
Use this when planning or reviewing reserved capacity comparison. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Reserved capacity comparison** for [PROJECT / CLIENT], which is an internal enterprise application. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a checklist with acceptance criteria, tailored specifically to reserved capacity comparison. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Idle resource identification
Use this when planning or reviewing idle resource identification. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Idle resource identification** for [PROJECT / CLIENT], which is a data processing service. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a risk register and mitigations, tailored specifically to idle resource identification. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Storage lifecycle optimization
Use this when planning or reviewing storage lifecycle optimization. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Storage lifecycle optimization** for [PROJECT / CLIENT], which is a multi-tenant API. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a reproducible runbook, tailored specifically to storage lifecycle optimization. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Compute right-sizing plan
Use this when planning or reviewing compute right-sizing plan. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Compute right-sizing plan** for [PROJECT / CLIENT], which is a remote-first startup. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a comparison matrix with trade-offs, tailored specifically to compute right-sizing plan. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Kubernetes spend allocation
Use this when planning or reviewing kubernetes spend allocation. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Kubernetes spend allocation** for [PROJECT / CLIENT], which is a regulated business workload. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a configuration outline with explanations, tailored specifically to kubernetes spend allocation. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Cloud budget alert design
Use this when planning or reviewing cloud budget alert design. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Cloud budget alert design** for [PROJECT / CLIENT], which is an event-driven backend. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a validation and rollback procedure, tailored specifically to cloud budget alert design. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Application latency optimization
Use this when planning or reviewing application latency optimization. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Application latency optimization** for [PROJECT / CLIENT], which is a customer-facing web platform. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a structured report with clear owners, tailored specifically to application latency optimization. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Monthly FinOps report
Use this when planning or reviewing monthly finops report. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Monthly FinOps report** for [PROJECT / CLIENT], which is a distributed engineering team. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a concise client-ready deliverable, tailored specifically to monthly finops report. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Client Delivery & Remote Career
Cloud engineer portfolio case study
Use this when planning or reviewing cloud engineer portfolio case study. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Cloud engineer portfolio case study** for [PROJECT / CLIENT], which is a small SaaS product. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a step-by-step implementation plan, tailored specifically to cloud engineer portfolio case study. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
DevOps freelance scope of work
Use this when planning or reviewing devops freelance scope of work. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **DevOps freelance scope of work** for [PROJECT / CLIENT], which is an e-commerce storefront. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a checklist with acceptance criteria, tailored specifically to devops freelance scope of work. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Infrastructure handover documentation
Use this when planning or reviewing infrastructure handover documentation. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Infrastructure handover documentation** for [PROJECT / CLIENT], which is an internal enterprise application. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a risk register and mitigations, tailored specifically to infrastructure handover documentation. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Client onboarding checklist
Use this when planning or reviewing client onboarding checklist. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Client onboarding checklist** for [PROJECT / CLIENT], which is a data processing service. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a reproducible runbook, tailored specifically to client onboarding checklist. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Technical discovery call script
Use this when planning or reviewing technical discovery call script. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Technical discovery call script** for [PROJECT / CLIENT], which is a multi-tenant API. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a comparison matrix with trade-offs, tailored specifically to technical discovery call script. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Cloud proposal and estimate
Use this when planning or reviewing cloud proposal and estimate. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Cloud proposal and estimate** for [PROJECT / CLIENT], which is a remote-first startup. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a configuration outline with explanations, tailored specifically to cloud proposal and estimate. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Stakeholder status update
Use this when planning or reviewing stakeholder status update. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Stakeholder status update** for [PROJECT / CLIENT], which is a regulated business workload. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a validation and rollback procedure, tailored specifically to stakeholder status update. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Remote DevOps interview simulation
Use this when planning or reviewing remote devops interview simulation. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Remote DevOps interview simulation** for [PROJECT / CLIENT], which is an event-driven backend. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a structured report with clear owners, tailored specifically to remote devops interview simulation. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Ethical demo project plan
Use this when planning or reviewing ethical demo project plan. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **Ethical demo project plan** for [PROJECT / CLIENT], which is a customer-facing web platform. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a concise client-ready deliverable, tailored specifically to ethical demo project plan. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
30-60-90 day DevOps learning plan
Use this when planning or reviewing 30-60-90 day devops learning plan. Supply real architecture details and sanitize secrets before pasting.
Act as a senior Cloud Engineer and DevOps reviewer. Help me perform **30-60-90 day DevOps learning plan** for [PROJECT / CLIENT], which is a distributed engineering team. Context: cloud/provider=[AWS / Azure / GCP / hybrid]; environment=[dev / staging / production]; architecture=[CURRENT_ARCHITECTURE]; constraints=[BUDGET, COMPLIANCE, TEAM_SKILLS, DEADLINE]; existing evidence=[CONFIGS, METRICS, LOGS OR NOTES]. Ask for any critical missing information first; distinguish confirmed facts from assumptions. Produce a prioritized decision table, tailored specifically to 30-60-90 day devops learning plan. Include prerequisites, dependencies, least-privilege/security checks, implementation or investigation sequence, validation tests, failure scenarios, rollback/recovery steps, cost and reliability implications, and what needs human approval. Do not claim to have accessed live systems or executed commands. If suggesting commands or configuration, give safe, annotated examples and explain where placeholders must be replaced. End with a clear definition of done and the three most important follow-up actions.
Portfolio exercise: production-ready demo
Use fictional or permitted sample data to design a cloud-hosted three-tier app. Document a secure landing zone, Terraform deployment, containerized build, CI/CD with tests, SLO and alerting, backup/restore exercise, cost estimate and rollback. Publish sanitized diagrams, sample configs, test evidence and lessons learned—not secrets or client data.
Quality assurance checklist
Confirm least-privilege IAM, encryption, backups, log hygiene, resource tagging, budgets, monitoring, change approval, rollback, test coverage, accessibility of runbooks and accurate client-facing claims.
Frequently asked questions
Are these actual WordPress shortcodes?
No. CLOUD-001 through CLOUD-120 are search and reference IDs for AI prompt templates.
Can I use these with different AI assistants?
Yes. Copy the plain-English template, supply safe context and verify outputs against current provider documentation.
Should I execute AI-generated commands directly?
No. Have a qualified human review them, test in non-production first and secure explicit approval for destructive or production changes.
How can I demonstrate remote-job readiness?
Share a permission-safe end-to-end infrastructure case study with documented decisions, versioned code, tests, monitoring, cost controls and operational handover.
Educational content; provider features and prices change. Check official docs before implementation. No hiring, search ranking or AI citation outcome is guaranteed.