cloud-native-architecture

Design cloud-native architectures covering containers, Kubernetes, service mesh, serverless, and FinOps.

Updated Jun 28, 2026
One-click install
npx skills add https://github.com/JaviMontano/claude-plugins --skill cloud-native-architecture-javimontano
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cloud-native-architecture
Source: https://github.com/JaviMontano/claude-plugins/tree/main/plugins/claude-native-toolkit/skills/cloud-native-architecture
Command: npx skills add https://github.com/JaviMontano/claude-plugins --skill cloud-native-architecture-javimontano

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Teams modernizing applications for the cloud often lack a structured method to assess cloud readiness, choose between containers and serverless, evaluate service mesh adoption, and control cloud costs. This Skill produces evidence-tagged architecture documentation that guides teams from 12-factor readiness assessment through production-grade Kubernetes deployment and FinOps governance. ## Core Features & Use Cases - 12-Factor Compliance Audit: Rates each factor as compliant, partial, or non-compliant with remediation effort estimates and a containerization readiness checklist. - Container, Mesh & Serverless Decisions: Provides decision matrices for Kubernetes resource sizing, node/pod autoscaling (Karpenter, HPA, KEDA), service mesh selection (Cilium, Istio Ambient, Linkerd), and per-workload serverless vs. container choices. - FinOps Integration: Defines cost allocation labels, OpenCost/Kubecost tooling, optimization levers like spot instances and rightsizing, and unit economics tracking. - Use Case: A bank modernizing a monolith receives a full architecture document covering EKS cluster topology, Istio Ambient mesh rationale, Lambda decisions for event-driven workloads, and a monthly cost allocation dashboard. ## Quick Start Ask the assistant to design a cloud-native architecture for your platform, including a 12-factor assessment, Kubernetes strategy, and FinOps plan.

Frequently Asked Questions about cloud-native-architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decide between serverless and containers for a workload?▼

Evaluate traffic pattern, execution time, state requirements, cold start tolerance, and invocation volume per workload. Spiky stateless workloads under 15 minutes favor serverless; steady stateful services favor containers on Kubernetes with HPA.

When should I adopt a service mesh like Istio or Cilium?▼

Adopt a mesh when you run more than 10 services and need mTLS, traffic management, or zero-instrumentation observability. Under 10 services, defer the mesh; for mTLS only, prefer Cilium or Istio Ambient to minimize sidecar overhead.

How do I containerize a legacy monolith safely?▼

Containerize the monolith first as a lift-and-shift, then decompose incrementally using the strangler fig pattern. Avoid big-bang decomposition; remediate 12-factor gaps like externalized config and stateless processes before or during containerization.

What is the difference between Karpenter and Cluster Autoscaler?▼

Karpenter provisions right-sized EC2 nodes directly in 30-60 seconds with native spot optimization and consolidation, while Cluster Autoscaler uses ASG templates taking 2-5 minutes. Prefer Karpenter on EKS; use Cluster Autoscaler where Karpenter is unavailable.

Does this skill cover VPC design and cloud platform infrastructure?▼

No. VPC design, transit routing, compute quotas, and IAM foundations belong to the infrastructure-architecture skill. This skill focuses on application-level cloud-native design: containers, mesh, serverless, and FinOps.

How do I implement FinOps cost allocation in Kubernetes?▼

Deploy OpenCost from day one with a label strategy covering team, service, environment, and cost-center. Add budget alerts per namespace, anomaly detection for daily spikes over 20 percent, and unit economics like cost per transaction.