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, /ml-pipeline
- Complements:
deploy-to-production skill (rollback procedures)
1---2name: cloud-platforms-23description: Cloud platform reference modules — GCP, Azure, AWS. Provides platform-specific CLI commands, managed service patterns, networking, IAM, observability, and operational procedures. Activated when working with cloud infrastructure, production environments, managed databases, container orchestration, or cloud-native services. Detect the target platform from the project's CLAUDE.md tech stack declaration.4---5
6# Cloud Platforms
7
8Pluggable cloud platform knowledge modules. Each resource file contains platform-specific patterns for one cloud provider.
9
10## How It Works
11
121. **Detect platform**: Read the project's `CLAUDE.md` tech stack declaration to identify which cloud platform(s) are in use
132. **Load the right module**: Read the corresponding resource file(s) below
143. **Apply patterns**: Use platform-specific CLI commands, service names, and operational patterns from the loaded module
15
16## Platform Detection Signals
17
18| 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` |
23
24If CLAUDE.md does not declare a cloud platform, ask the user before proceeding with platform-specific operations.
25
26If the project uses **multi-cloud**, load all relevant modules and apply patterns per service based on where it runs.
27
28## Module Structure
29
30Each reference file follows a consistent structure:
31
321. **Core Platform** — account/project structure, IAM, networking, secrets, tagging
332. **Container Orchestration** — managed Kubernetes (GKE/AKS/EKS) patterns
343. **Managed Database** — managed SQL service patterns and reliability
354. **CI/CD** — platform-native build and deploy services
365. **Observability** — monitoring, logging, alerting, dashboards
376. **CLI Reference** — essential CLI commands for diagnostics and operations
387. **Security and Compliance** — audit logging, encryption, network security
39
40## Integration
41
42- **Used by roles**: `Agent(devops-engineer)`, `Agent(sre-engineer)`, `Agent(cloud-architect)`
43- **Used by workflows**: `/analyze-prod`, `/bugfix`, `/infra-change`, `/deploy-production`, `/ml-pipeline`
44- **Complements**: `deploy-to-production` skill (rollback procedures)
majiayu000