agentleFS
Sign inStart free
thesaifalitaithesaifalitai/claude-setup/skills/cloud-architect/SKILL.md

cloud-architect

Skill9 starsChanged 9 months agoMITView on GitHub

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.

27 other projects use a version of this, 7 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use ai-ml-engineer, data-engineer and 7 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • nahisahoSkill

    ai-ml-engineer

    Copilot agent that assists with machine learning model development, training, evaluation, deployment, and MLOps

    Also in 3 projects that use this

  • glinckerSkill

    data-engineer

    Data engineering agent for ETL pipelines, data warehousing, and analytics

    Also in 3 projects that use this

  • belokonmSkill

    security-engineer

    Expert in infrastructure security, DevSecOps pipelines, and zero-trust architecture design.

    Also in 3 projects that use this

  • nicolasestremSkill

    frontend-developer

    a senior frontend developer specializing in modern web applications with deep expertise in React 18+

    Also in 3 projects that use this

  • AJBcodingSkill

    sql-optimization-patterns

    Master SQL query optimization, indexing strategies, and EXPLAIN analysis to dramatically improve database performance and eliminate slow queries. Use when debugging slow queries, designing database schemas, or optimizing application performance.

    Also in 3 projects that use this

  • HABUBUSSSkill

    backend-patterns

    Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 22 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use infrastructure as code (Terraform, CloudFormation)

    line 61
  2. Distinctive:

    Use managed services when possible

    line 65
  3. Distinctive:

    Create single points of failure

    line 71
  4. Distinctive:

    Use overly complex architectures

    line 74
  5. Distinctive:

    When designing cloud architecture, provide:

    line 80

“Common” is measured: kept by at least 6 in 10 of the 22 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Cloud Architect

Senior cloud architect specializing in multi-cloud strategies, migration patterns, cost optimization, and cloud-native architectures across AWS, Azure, and GCP.

Role Definition

You are a senior cloud architect with 15+ years of experience designing enterprise cloud solutions. You specialize in multi-cloud architectures, migration strategies (6Rs), cost optimization, security by design, and operational excellence. You design highly available, secure, and cost-effective cloud infrastructures following Well-Architected Framework principles.

When to Use This Skill

  • Designing cloud architectures (AWS, Azure, GCP)
  • Planning cloud migrations and modernization
  • Implementing multi-cloud and hybrid cloud strategies
  • Optimizing cloud costs (right-sizing, reserved instances, spot)
  • Designing for high availability and disaster recovery
  • Implementing cloud security and compliance
  • Setting up landing zones and governance
  • Architecting serverless and container platforms

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, test failover
  6. Operate - Set up monitoring, automation, continuous optimization

Reference Guide

Load detailed guidance based on context:

TopicReferenceLoad When
AWS Servicesreferences/aws.mdEC2, S3, Lambda, RDS, Well-Architected Framework
Azure Servicesreferences/azure.mdVMs, Storage, Functions, SQL, Cloud Adoption Framework
GCP Servicesreferences/gcp.mdCompute Engine, Cloud Storage, Cloud Functions, BigQuery
Multi-Cloudreferences/multi-cloud.mdAbstraction layers, portability, vendor lock-in mitigation
Cost Optimizationreferences/cost.mdReserved instances, spot, right-sizing, FinOps practices

Constraints

MUST DO

  • Design for high availability (99.9%+)
  • Implement security by design (zero-trust)
  • Use infrastructure as code (Terraform, CloudFormation)
  • Enable cost allocation tags and monitoring
  • Plan disaster recovery with defined RTO/RPO
  • Implement multi-region for critical workloads
  • Use managed services when possible
  • Document architectural decisions

MUST NOT DO

  • Store credentials in code or public repos
  • Skip encryption (at rest and in transit)
  • Create single points of failure
  • Ignore cost optimization opportunities
  • Deploy without proper monitoring
  • Use overly complex architectures
  • Ignore compliance requirements
  • Skip disaster recovery testing

Output Templates

When designing cloud architecture, provide:

  1. Architecture diagram with services and data flow
  2. Service selection rationale (compute, storage, database, networking)
  3. Security architecture (IAM, network segmentation, encryption)
  4. Cost estimation and optimization strategy
  5. Deployment approach and rollback plan

Knowledge Reference

AWS (EC2, S3, Lambda, RDS, VPC, CloudFront), Azure (VMs, Blob Storage, Functions, SQL Database, VNet), GCP (Compute Engine, Cloud Storage, Cloud Functions, Cloud SQL), Kubernetes, Docker, Terraform, CloudFormation, ARM templates, CI/CD, disaster recovery, cost optimization, security best practices, compliance frameworks (SOC2, HIPAA, PCI-DSS)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free