Cloud Platforms
Pluggable cloud platform knowledge modules. Each resource file contains platform-specific patterns for one cloud provider.
How It Works
- Detect platform: Read the project's
CLAUDE.md tech stack declaration to identify which cloud platform(s) are in use
- Load the right module: Read the corresponding resource file(s) below
- Apply patterns: Use platform-specific CLI commands, service names, and operational patterns from the loaded module
Platform Detection Signals
| Signal in CLAUDE.md / Project |
Platform |
Resource File |
| GCP, Google Cloud, GKE, Cloud SQL, Cloud Build, gcloud, Artifact Registry |
Google Cloud Platform |
gcp-reference.md |
| Azure, AKS, Azure SQL, Azure DevOps, az CLI, ACR, Azure Monitor |
Microsoft Azure |
azure-reference.md |
| AWS, EKS, RDS, CodePipeline, aws CLI, ECR, CloudWatch |
Amazon Web Services |
aws-reference.md |
If CLAUDE.md does not declare a cloud platform, ask the user before proceeding with platform-specific operations.
If the project uses multi-cloud, load all relevant modules and apply patterns per service based on where it runs.
Module Structure
Each reference file follows a consistent structure:
- Core Platform — account/project structure, IAM, networking, secrets, tagging
- Container Orchestration — managed Kubernetes (GKE/AKS/EKS) patterns
- Managed Database — managed SQL service patterns and reliability
- CI/CD — platform-native build and deploy services
- Observability — monitoring, logging, alerting, dashboards
- CLI Reference — essential CLI commands for diagnostics and operations
- Security and Compliance — audit logging, encryption, network security
Integration
- Used by roles:
Agent(devops-engineer), Agent(sre-engineer), Agent(cloud-architect)
- Used by workflows:
/analyze-prod, /bugfix, /infra-change, /deploy-production
- Complements:
deployment-procedures skill (rollback procedures)
1---2name: cloud-platforms3description: Use this skill when authoring or running a workflow that needs cloud-platform-specific commands, or when reviewing such workflows for platform coverage — as a knowledge module (not a workflow itself) providing platform-specific CLI commands, managed service patterns, networking, IAM, observability, and operational procedures across GCP, Azure, and AWS. Loaded by `/analyze-prod`, `/infra-change`, `/deploy-production`, and similar workflows.4---56# Cloud Platforms78Pluggable cloud platform knowledge modules. Each resource file contains platform-specific patterns for one cloud provider.910## How It Works11121. **Detect platform**: Read the project's `CLAUDE.md` tech stack declaration to identify which cloud platform(s) are in use132. **Load the right module**: Read the corresponding resource file(s) below143. **Apply patterns**: Use platform-specific CLI commands, service names, and operational patterns from the loaded module1516## Platform Detection Signals1718| Signal in CLAUDE.md / Project | Platform | Resource File |19|---|---|---|20| GCP, Google Cloud, GKE, Cloud SQL, Cloud Build, gcloud, Artifact Registry | **Google Cloud Platform** | `gcp-reference.md` |21| Azure, AKS, Azure SQL, Azure DevOps, az CLI, ACR, Azure Monitor | **Microsoft Azure** | `azure-reference.md` |22| AWS, EKS, RDS, CodePipeline, aws CLI, ECR, CloudWatch | **Amazon Web Services** | `aws-reference.md` |2324If CLAUDE.md does not declare a cloud platform, ask the user before proceeding with platform-specific operations.2526If the project uses **multi-cloud**, load all relevant modules and apply patterns per service based on where it runs.2728## Module Structure2930Each reference file follows a consistent structure:31321. **Core Platform** — account/project structure, IAM, networking, secrets, tagging332. **Container Orchestration** — managed Kubernetes (GKE/AKS/EKS) patterns343. **Managed Database** — managed SQL service patterns and reliability354. **CI/CD** — platform-native build and deploy services365. **Observability** — monitoring, logging, alerting, dashboards376. **CLI Reference** — essential CLI commands for diagnostics and operations387. **Security and Compliance** — audit logging, encryption, network security3940## Integration4142- **Used by roles**: `Agent(devops-engineer)`, `Agent(sre-engineer)`, `Agent(cloud-architect)`43- **Used by workflows**: `/analyze-prod`, `/bugfix`, `/infra-change`, `/deploy-production`44- **Complements**: `deployment-procedures` skill (rollback procedures)
avav25