Automate your entire cloud infrastructure — CI/CD, Docker, Kubernetes, Terraform, and monitoring
DevOps & Cloud Infrastructure is the definitive AI framework for engineers who need to build, automate, and monitor production cloud systems. It covers the full DevOps stack: CI/CD pipelines, containerization, Kubernetes orchestration, infrastructure-as-code with Terraform, observability with Prometheus and Grafana, security scanning, and incident response. Every prompt produces production-ready configuration files with security best practices built in.
Full Access Unlocked
All 50 prompts · All 6 modules
"The GitHub Actions pipeline prompt produced a complete, production-grade CI/CD workflow in one shot...."
Senior DevOps Engineer · Series B Startup
Need expert implementation?
Hire an OrchestratorConnect with a certified Prompt.Doctor Orchestrator to deploy this framework for you.
No coding required. You will use ChatGPT or Claude as your AI tool. Follow these steps in order — do not skip ahead.
Purchase & download the framework
Click the buy button on this page. After checkout, go to the and hit Download .zip. Unzip it — you'll get a .md file (the full framework) and a .pdf (easy to read reference). Keep both open.
Open your project — new or existing
This dashboard is designed to integrate into any existing project or be built as a standalone app. If you already have a site in Airo (or Cursor, Bolt, etc.), open that project. If you're starting fresh, create a new project. The Orchestrator Prompt handles both cases — it scans what's already there and adds only what's missing.
Paste the Orchestrator Prompt into your builder's chat
Open the on this page. Copy the Orchestrator Prompt and paste it into your AI builder's chat. It will scaffold the full admin system — secure login, email marketing module, booking engine, and CMS — on top of your existing codebase. This takes 2–5 minutes.
Add your API keys as secrets
Critical — Novice UsersIn your builder, go to Settings → Secrets and add the keys your app needs. For this framework: STRIPE_SECRET_KEY (for booking payments — get it from your Stripe dashboard), ANTHROPIC_API_KEY (for AI-assisted content — get it from console.anthropic.com), and DATABASE_URL (your MySQL connection string). No key is needed for the admin login, CMS, or email modules — those run on your existing infrastructure.
Don't have a MySQL server?
You can purchase a shared hosting plan with cPanel and MySQL at host.esgwon.dev. Once your account is set up, follow the step-by-step guide to create your database and connect it to your AI website builder.
How to set up cPanel MySQL & connect to your AI website →Need help with Stripe?
Get your STRIPE_SECRET_KEY and STRIPE_PUBLISHABLE_KEY from your Stripe dashboard. The guide covers test keys, webhook setup, and going live.
Need help with Anthropic?
Get your ANTHROPIC_API_KEY from console.anthropic.com. The guide covers model selection, cost management, and troubleshooting.
Prompting Airo after setup — always name the file
When asking Airo to add tables, columns, or features to the admin dashboard, always include src/server/lib/admin-db.ts in your prompt. Without it, Airo may target the wrong database. Example: "Add a bookings table in the admin database (src/server/lib/admin-db.ts) — do not touch any other database connection in this project."
Run the framework prompts inside your live app
Your app is now running in the builder's preview panel. Open the on this page, copy each prompt one at a time, and paste it into your builder's chat. Replace every [BRACKET] with your real data before sending. Work through the stages in order — each stage output feeds the next.
Test end-to-end, then publish or hand off to your client
Walk through the admin as a real user: log in, create a booking, send a test email campaign, update a CMS image, and run the Safe-to-Publish gate. Once everything passes, click Publish in your builder. Because this is a white-label dashboard, your client accesses it at /admin on their own domain — no Prompt.Doctor branding, no third-party login required.
6 modules · 50 prompts · 6 workflow stages
CI/CD Pipeline System
GitHub Actions workflows: test → build → scan → deploy pipeline for Node.js, Python, and Docker apps. Includes branch protection rules, environment approvals, and rollback workflow.
10 promptsContainerization System
Production Dockerfile (multi-stage build, non-root user, minimal base image), docker-compose for local development, and .dockerignore. Includes Node.js, Python, and Go variants.
8 promptsKubernetes Manifests
Deployment (with resource limits, liveness/readiness probes), Service, Ingress (with TLS), HorizontalPodAutoscaler, ConfigMap, Secret, and Namespace manifests. Includes Helm chart structure.
10 promptsTerraform Infrastructure
AWS modules: VPC with public/private subnets, ECS Fargate service, RDS PostgreSQL, S3 + CloudFront, and ALB. Includes remote state configuration and variable structure.
10 promptsObservability Stack
Prometheus scrape configuration, Grafana dashboard JSON (application metrics, infrastructure metrics), AlertManager rules, and PagerDuty integration.
8 promptsSecurity & Incident Response
Trivy image scanning in CI/CD, SAST with Semgrep, HashiCorp Vault secrets management, and incident response runbook template (detection, triage, resolution, post-mortem).
4 promptsWrite a GitHub Actions workflow for a Node.js TypeScript application. Requirements: 1) Triggers: push to main, pull requests to main, 2) Jobs (in order): test (npm test), lint (npm run lint), build (npm run build), docker-build (build + push to ECR), security-scan (Trivy on Docker image), deploy-staging (on push to main), deploy-production (manual approval required), 3) Environment variables from GitHub Secrets: AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, ECR_REGISTRY, 4) Caching: npm cache between jobs, 5) Notifications: Slack on failure, 6) Rollback job: triggered manually, deploys previous image tag. Full YAML.
Write a production-ready Dockerfile for a Node.js TypeScript application. Requirements: 1) Multi-stage build: builder stage (compile TypeScript), production stage (runtime only), 2) Base image: node:20-alpine (not full node), 3) Non-root user: create and use "node" user, 4) Only copy compiled output and node_modules (production only) to final stage, 5) Health check: HTTP GET /health every 30s, 6) Expose port 3000, 7) .dockerignore: exclude node_modules, src, .git, .env, 8) Final image size target: under 200MB. Include docker build and run commands.
Write Kubernetes manifests for a Node.js API service. Include: 1) Namespace: production, 2) Deployment: 3 replicas, rolling update strategy (maxSurge: 1, maxUnavailable: 0), resource limits (CPU: 500m, memory: 512Mi), liveness probe (GET /health, 30s initial delay), readiness probe (GET /ready, 10s initial delay), 3) Service: ClusterIP, port 80 → 3000, 4) Ingress: nginx ingress controller, TLS with cert-manager, host: api.example.com, 5) HorizontalPodAutoscaler: min 3, max 10, CPU target 70%, 6) ConfigMap: non-sensitive environment variables. Full YAML with --- separators.
system
20 prompts
templates
8 prompts
architecture
10 prompts
workflow
12 prompts
"The GitHub Actions pipeline prompt produced a complete, production-grade CI/CD workflow in one shot. The Trivy scanning integration is exactly what our security team required."
Senior DevOps Engineer
Series B Startup
"I'm a developer, not a DevOps engineer. The Kubernetes manifests prompt gave me production-ready configs I could actually understand and maintain."
Backend Developer
Owning My Own Infra
All 50 prompts across 6 modules are unlocked for your account.
Lifetime access