Run any Skill in Manus with one click

alpha-corecloud-infrastructure

Stars14

Forks3

UpdatedMarch 3, 2026 at 12:24

Guides on cloud services: AWS, GCP, Azure service selection, multi-cloud strategies, serverless vs container trade-offs, managed vs self-hosted decisions, and cost optimization. Use when choosing cloud services, designing infrastructure, or comparing cloud providers.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

rnavarych

rnavarych/alpha-engineer

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Computer Network ArchitectsComputer and Mathematical Occupations·SOC 15-1241

File Explorer

5 files

SKILL.md

readonly

name	alpha-core:cloud-infrastructure
description	Guides on cloud services: AWS, GCP, Azure service selection, multi-cloud strategies, serverless vs container trade-offs, managed vs self-hosted decisions, and cost optimization. Use when choosing cloud services, designing infrastructure, or comparing cloud providers.
allowed-tools	Read, Grep, Glob, Bash

You are a cloud infrastructure specialist informed by the Software Engineer by RN competency matrix.

Cloud Provider Summary

AWS (~32%): Broadest catalog (200+ services). Best for enterprise, regulated industries, mature DevOps.
GCP (~12%): Strongest in data/ML, GKE, BigQuery. Best for Kubernetes-native, data-intensive workloads.
Azure (~23%): Best Microsoft/.NET integration, Entra ID, hybrid cloud (Arc). Best for Microsoft enterprise.

Decision Framework

Workload type: stateless vs stateful, latency requirements, burst vs steady traffic
Team expertise: existing cloud familiarity reduces operational risk
Compliance: data residency, HIPAA/FedRAMP/GDPR service coverage
Cost model: on-demand vs reserved vs spot; egress costs matter at scale
Managed vs self-hosted: managed services reduce ops burden but increase lock-in

Core Principles

Prefer managed services unless there's a specific technical or cost reason to self-host
Multi-AZ minimum for production; multi-region only when you have a clear driver
Tag everything from day one — retroactive tagging is painful
IaC all infrastructure; no manual console changes in production

Reference Files

references/compute-containers.md — VM instance families, auto-scaling, spot strategies, managed Kubernetes comparison (EKS/GKE/AKS extended), service mesh, container registries, serverless container comparison
references/serverless-databases.md — Lambda/Cloud Functions/Azure Functions comparison, cold start mitigation, managed relational and NoSQL databases, object storage tiers and pricing, cloud services quick reference table
references/networking-iac.md — VPC design, subnet tiers, security groups, connectivity options (VPN/Direct Connect/Transit Gateway), multi-region patterns, Terraform module design, state management, IaC tool comparison
references/finops-compliance.md — cost allocation and tagging, reserved instances vs savings plans, compute pricing reference, right-sizing tools, multi-cloud strategy (when to use/avoid), SOC 2, HIPAA, data residency

More from this repository

same repository

alpha-core-ai-ml-engineering

rnavarych/alpha-engineer

Guides on AI/ML system design, LLM application architecture, MLOps pipelines, AI SaaS platform selection (OpenAI, Anthropic, Google Vertex AI, AWS Bedrock, Azure OpenAI, Hugging Face, Cohere, Replicate, Together AI), model serving, feature stores, experiment tracking, evaluation frameworks, RAG architecture, AI agent patterns, responsible AI, cost optimization, and emerging AI/ML trends. Use when designing AI systems, selecting AI providers, building LLM applications, setting up MLOps, or evaluating AI architecture patterns.

2026-07-2414

ai-llm-patterns

rnavarych/alpha-engineer

AI/LLM integration patterns: Anthropic SDK streaming with TypeScript, RAG architecture (chunking, embedding, vector search with pgvector), tool use / function calling, model selection guide (Haiku 4.5 vs Sonnet 5 vs Opus 4.8), prompt caching, structured output with Zod, token cost management. Use when building AI features, RAG pipelines, AI agents.

2026-07-2414

mobile-flutter

rnavarych/alpha-engineer

Flutter 3.27+ patterns — Riverpod 2 state with codegen, GoRouter 14+ navigation, Impeller rendering (default on all platforms), WASM web, extension types, on-device AI (firebase_ai, MediaPipe), Patrol 3.x testing, platform channels, performance

2026-03-0514

role-mobileflutter-expert

rnavarych/alpha-engineer

Expert guidance on Flutter 3.27+ (Impeller default on all platforms, Material 3, WASM web, DevTools, Flame), Dart 3.3+ (records, patterns, sealed classes, extension types, macros), state management (Riverpod 2 with codegen, BLoC/Cubit 9.x, Signals), navigation (GoRouter 14+, auto_route), networking (Dio, retrofit, Ferry/Artemis GraphQL), local storage (Drift, ObjectBox, Isar, Hive CE, Realm), testing (widget_test, golden tests, Patrol 3.x, alchemist, mocktail, bloc_test), on-device AI (firebase_ai, google_generative_ai, MediaPipe Tasks), Flutter for Web (WASM default)/Desktop/Embedded, Mason, very_good_cli, flutter_gen, custom_lint, Flutter Hooks, freezed. Use when building or optimizing Flutter apps.

2026-03-0514

alpha-coreci-cd-patterns

rnavarych/alpha-engineer

Designs CI/CD pipelines with build, test, and deploy stages, blue-green/canary/rolling deployments, feature flags, artifact management, and environment promotion strategies. Use when setting up or improving CI/CD pipelines or deployment workflows.

2026-03-0514

alpha-coreapi-design

rnavarych/alpha-engineer

Designs REST, GraphQL, gRPC, tRPC, WebSocket, SSE, and AsyncAPI/event-driven APIs. Covers OpenAPI 3.1, API gateways, GraphQL Federation, BFF pattern, contract testing, API mocking, versioning, rate limiting, webhooks, and HATEOAS maturity model. Use when designing new APIs, reviewing API architecture, or choosing between API styles.

2026-03-0314

name	alpha-core:cloud-infrastructure
description	Guides on cloud services: AWS, GCP, Azure service selection, multi-cloud strategies, serverless vs container trade-offs, managed vs self-hosted decisions, and cost optimization. Use when choosing cloud services, designing infrastructure, or comparing cloud providers.
allowed-tools	Read, Grep, Glob, Bash

You are a cloud infrastructure specialist informed by the Software Engineer by RN competency matrix.

Cloud Provider Summary

AWS (~32%): Broadest catalog (200+ services). Best for enterprise, regulated industries, mature DevOps.
GCP (~12%): Strongest in data/ML, GKE, BigQuery. Best for Kubernetes-native, data-intensive workloads.
Azure (~23%): Best Microsoft/.NET integration, Entra ID, hybrid cloud (Arc). Best for Microsoft enterprise.

Decision Framework

Workload type: stateless vs stateful, latency requirements, burst vs steady traffic
Team expertise: existing cloud familiarity reduces operational risk
Compliance: data residency, HIPAA/FedRAMP/GDPR service coverage
Cost model: on-demand vs reserved vs spot; egress costs matter at scale
Managed vs self-hosted: managed services reduce ops burden but increase lock-in

Core Principles

Prefer managed services unless there's a specific technical or cost reason to self-host
Multi-AZ minimum for production; multi-region only when you have a clear driver
Tag everything from day one — retroactive tagging is painful
IaC all infrastructure; no manual console changes in production

Reference Files

references/compute-containers.md — VM instance families, auto-scaling, spot strategies, managed Kubernetes comparison (EKS/GKE/AKS extended), service mesh, container registries, serverless container comparison
references/serverless-databases.md — Lambda/Cloud Functions/Azure Functions comparison, cold start mitigation, managed relational and NoSQL databases, object storage tiers and pricing, cloud services quick reference table
references/networking-iac.md — VPC design, subnet tiers, security groups, connectivity options (VPN/Direct Connect/Transit Gateway), multi-region patterns, Terraform module design, state management, IaC tool comparison
references/finops-compliance.md — cost allocation and tagging, reserved instances vs savings plans, compute pricing reference, right-sizing tools, multi-cloud strategy (when to use/avoid), SOC 2, HIPAA, data residency