Cloud-Native Architecture: Containers, Mesh, Serverless & Cost Optimization

Generic, brand-neutral engineering capability; deep, sourced playbooks live in references/ and knowledge/. [DOC]

Generic, brand-neutral engineering capability; sourced playbooks in references//knowledge/. [DOC]

TL;DR

Cloud-native architecture designs applications to fully exploit cloud platforms -- containers, orchestration, service mesh, serverless, infrastructure as code, and cost-aware engineering. This skill produces architecture documentation guiding teams from cloud readiness assessment through production-grade deployment [EXPLICIT]

When to Use

• Assessing application readiness for cloud-native transformation
• Designing container strategy and Kubernetes architecture
• Evaluating service mesh adoption (Istio, Linkerd, Cilium)
• Making serverless vs. container decisions per workload
• Planning multi-cloud or cloud-agnostic architecture
• Implementing FinOps practices for cost visibility and optimization

When NOT to Use

• Infrastructure platform design (VPCs, compute, storage) --> use infrastructure-architecture skill
• CI/CD pipelines and supply chain security --> use devsecops-architecture skill
• Application internal structure and patterns --> use software-architecture skill
• Migrating existing workloads to cloud --> use cloud-migration skill

---

Sub-capabilities (resource map)

Deep, evidence-tagged playbooks — open the one the task needs (ICM Layer 3, on-demand). [INFERENCE]

Procedure

1. Resolve the sub-capability; open the matching references/ playbook. [EXPLICIT]
2. Apply its decision tables; pick the strategy explicitly. [EXPLICIT]
3. Validate against the Quality Criteria and tag every claim. [EXPLICIT]

Quality Criteria

• Sub-capability resolved to one playbook. [INFERENCE]
• Claims evidence-tagged. [EXPLICIT]

Contract

• Aceptación: capability resolved to its reference playbook, applied, validated, evidence-tagged. [EXPLICIT]
• Límites: · Does not design internal application architecture (use software-architecture skill) · Does not cover infrastructure platform setup (use infrastructure-architecture skill) · Does. [EXPLICIT]
• Casos borde: Monolith Containerization: Containerize the monolith first (lift-and-shift to container), then decompose. Use strangler fig pattern. Do not attempt simultaneous containerizatio. [EXPLICIT]
• Supuestos: · Application is being modernized or built for cloud deployment · Team has or is developing container and orchestration skills · Cloud provider(s) selected or shortlisted · Budget. [SUPUESTO]
• Trade-off: Decision Enables Constrains When to Use --- --- --- --- Kubernetes Portability, scaling, ecosystem Operational complexity Polyglot microservices, experienced te. [EXPLICIT]

Packet

Capas del packet, cargables bajo demanda (disciplina ICM: una capa por vez, nunca todas juntas): references/ guías de profundidad (cargar UNA por etapa) · knowledge/ cuerpo de conocimiento · prompts/ prompts listos · examples/ salida de ejemplo · agents/ subagentes del packet · assets/ recursos estáticos.