# Cloud Architect

Designs cloud architectures, creates migration plans, generates cost optimization...

- Repository: https://github.com/Jeffallan/claude-skills (12164 stars)
- Category: Design
- License: MIT
- Last updated: 2026-10-30
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add Jeffallan/claude-skills --skill cloud-architect -g -a claude-code -y`
Codex: `npx skills add Jeffallan/claude-skills --skill cloud-architect -g -a codex -y`
Cursor: `npx skills add Jeffallan/claude-skills --skill cloud-architect -g -a cursor -y`
Gemini CLI: `npx skills add Jeffallan/claude-skills --skill cloud-architect -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add Jeffallan/claude-skills`

## Description

Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost optimization, disaster recovery, landing zones, security architecture, serverless design.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Cloud Architect

## Core Workflow

1. **Discovery**, Assess current state, requirements, constraints, compliance needs
2. **Design**, Select services, design topology, plan data architecture
3. **Security**, Implement zero-trust, identity federation, encryption
4. **Cost Model**, Right-size resources, reserved capacity, auto-scaling
5. **Migration**, Apply 6Rs framework, define waves, validate connectivity before cutover
6. **Operate**, Set up monitoring, automation, continuous optimization

### Workflow Validation Checkpoints

**After Design:** Confirm every component has a redundancy strategy and no single points of failure exist in the topology.

**Before Migration cutover:** Validate VPC peering or connectivity is fully established:
```bash
# AWS: confirm peering connection is Active before proceeding
aws ec2 describe-vpc-peering-connections \
  --filters "Name=status-code,Values=active"

# Azure: confirm VNet peering state
az network vnet peering list \
  --resource-group myRG --vnet-name myVNet \
  --query "[].{Name:name,State:peeringState}"
```

**After Migration:** Verify application health and routing:
```bash
# AWS: check target group health in ALB
aws elbv2 describe-target-health \
  --target-group-arn arn:aws:elasticloadbalancing:...
```

**After DR test:** Confirm RTO/RPO targets were met; document actual recovery times.

## Reference Guide

Load detailed guidance based on context:

| Topic | Reference | Load When |
|-------|-----------|-----------|
| AWS Services | `references/aws.md` | EC2, S3, Lambda, RDS, Well-Architected Framework |
| Azure Services | `references/azure.md` | VMs, Storage, Functions, SQL, Cloud Adoption Framework |
| GCP Services | `references/gcp.md` | Compute Engine, Cloud Storage, Cloud Functions, BigQuery |
| Multi-Cloud | `references/multi-cloud.md` | Abstraction layers, portability, vendor lock-in mitigation |
| Cost Optimization | `references/cost.md` | Reserved instances, spot, right-sizing, FinOps practices |

The rest: https://github.com/Jeffallan/claude-skills/blob/HEAD/skills/cloud-architect/SKILL.md