メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | cloud-architect |
| description | 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. |
| license | MIT |
| metadata | {"author":"https://github.com/Jeffallan","version":"1.0.0","domain":"infrastructure","triggers":"AWS, Azure, GCP, Google Cloud, cloud migration, cloud architecture, multi-cloud, cloud cost, Well-Architected, landing zone, cloud security, disaster recovery, cloud native, serverless architecture","role":"architect","scope":"infrastructure","output-format":"architecture","related-skills":"devops-engineer, kubernetes-specialist, terraform-engineer, security-reviewer, microservices-architect, monitoring-expert"} |
Senior cloud architect specializing in multi-cloud strategies, migration patterns, cost optimization, and cloud-native architectures across AWS, Azure, and GCP.
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.
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 |
When designing cloud architecture, provide:
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)
Active token optimization and context efficiency specialist. ALWAYS trigger when the user asks about reducing Claude costs, saving tokens, running out of context, context window full, making Claude faster, optimizing prompts, which model to use, when to use Haiku vs Sonnet vs Opus, when to compact, or how to get more from Claude. Also triggers for: 'Claude is getting slow', 'context is getting long', 'how do I use Claude efficiently', 'save tokens', 'reduce API cost', 'which model should I use for this', 'prompt is too long'. Works alongside token-tracker for cost monitoring.
Token usage tracking and cost monitoring specialist. ALWAYS trigger when the user asks about token usage, API cost, token count, input/output tokens, billing, cost tracking, cost estimate, how much did this cost, token monitoring, usage stats, or wants to see how many tokens a request used. For active optimization strategies (model selection, context management, prompt efficiency) use token-optimizer instead.
CTO-level engineering leadership advisor. Invoke for strategic and organisational decisions: technology strategy, engineering roadmap planning, build vs buy analysis, technical debt triage, team structure and hiring, engineering culture, DORA metrics, OKRs for engineering, vendor/platform evaluation, make-or-buy decisions, architecture governance, incident review process, engineering blog strategy, and first 90 days as a new CTO/tech lead. NOT for writing code — for implementation use the relevant stack skill.
Platform engineering and SRE specialist. Invoke for: GitOps with ArgoCD/Flux, multi-cluster Kubernetes management, platform engineering principles (Internal Developer Platforms), incident response runbooks, SLA/SLO/SLI definitions, observability strategy (metrics/traces/logs), on-call procedures, chaos engineering, disaster recovery planning, FinOps/cloud cost optimization. For standard Docker/CI/CD pipeline setup use devops-cicd instead.
Advanced Flutter architecture specialist. Use for Flutter architecture decisions, NOT standard Flutter implementation (use flutter-dev for that). Invoke for: Flutter clean architecture, feature-first project structure, advanced Riverpod patterns (Notifier/AsyncNotifier/family), advanced Bloc (Cubit vs Bloc tradeoffs, BlocObserver), Flutter performance profiling (DevTools, shader compilation, jank), custom RenderObject, platform channels/MethodChannel, multi-module monorepo, Flutter plugin authoring, isolates/compute(), build_runner code generation, get_it/injectable DI, Flutter 3.x upgrade migrations.
Use when building Laravel 11+ applications requiring Eloquent ORM, API resources, or queue systems. Invoke for Laravel models, Livewire components, Sanctum authentication, Horizon queues.
