cloud-architect
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.
npx skills add Jeffallan/claude-skills --skill cloud-architect --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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-he
- Core Workflow
- Workflow Validation Checkpoints
- Reference Guide
- Constraints
- MUST DO
- MUST NOT DO
- Common Patterns with Examples
- Least-Privilege IAM (Zero-Trust)
- VPC with Public/Private Subnets (Terraform)
- Auto-Scaling Group (Terraform)
- Cost Analysis CLI
- Output Templates
aws ec2 describe-vpc-peering-connections \ az network vnet peering list \ aws elbv2 describe-target-health \ aws iam create-role \ aws iam put-role-policy \ aws ce get-cost-and-usage \ az consumption usage list \
What does the cloud-architect skill do?
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.
How do I install it?
Run `npx skills add Jeffallan/claude-skills --skill cloud-architect --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Jeffallan/claude-skills, a repository with 10,871 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.