Skip to content

hoangminhung/devops-ai-kit / claude/skills/cloud-platforms

cloud-platforms

Verified

Design standards for cloud and on-prem infrastructure — Azure, AWS, GCP, Hetzner, OVHcloud and bare-metal data centers — organised by tier (baseline, production, enterprise landing zone) so recommendations match the real size of the project. Use whenever designing, provisioning or reviewing cloud networking, identity, managed Kubernetes (AKS/EKS/GKE), landing zones, VPC/VNet layouts or data-center infrastructure, even if the user only names a single provider service.

FileKindSize
SKILL.mdskill md3.4 KB
references/aws.mdmarkdown1.8 KB
references/azure.mdmarkdown2.0 KB
references/gcp.mdmarkdown1.2 KB
references/hetzner.mdmarkdown1.2 KB
references/on-premise.mdmarkdown1.3 KB
references/ovh.mdmarkdown710 B
---
name: cloud-platforms
description: Design standards for cloud and on-prem infrastructure — Azure, AWS, GCP, Hetzner, OVHcloud and bare-metal data centers — organised by tier (baseline, production, enterprise landing zone) so recommendations match the real size of the project. Use whenever designing, provisioning or reviewing cloud networking, identity, managed Kubernetes (AKS/EKS/GKE), landing zones, VPC/VNet layouts or data-center infrastructure, even if the user only names a single provider service.
when_to_use: Use when designing, deploying or reviewing infrastructure on Azure, AWS, GCP, Hetzner, OVH or on-premise — networking, identity, AKS/EKS/GKE, landing zone, VPC/VNet. Vietnamese triggers — "thiết kế, triển khai hoặc review hạ tầng trên Azure, AWS, GCP, Hetzner, OVH hoặc on-premise", "mạng, định danh, AKS/EKS/GKE, landing zone, VPC/VNet".
---

# Cloud & on-premise infrastructure standards

<!-- devops-ai-kit · Last reviewed: 2026-10-28 -->

## Choose the right tier before you apply standards

Suggesting an enterprise architecture for a small project is over-engineering: it costs money, it costs operations work, and the user will then ignore even the good advice. Always decide the tier first, and write the chosen tier in the plan / ADR.

| Tier | When | Apply |
|---|---|---|
| **Baseline** | Every project, including dev / PoC used for more than a few days | The "Baseline" part of each provider |
| **Production** | Real users, real data, an uptime commitment | Baseline + "Production" |
| **Enterprise landing zone** | Many teams / many subscriptions-accounts, compliance needs, a platform team | All three tiers |

If the tier is not clear, ask the user. Do not pick Enterprise by default.

## Common rules for every provider

- **MUST** Create every resource with IaC (Terraform / OpenTofu). Manual console work is only for troubleshooting. If you must create something by hand, write it down and import it into IaC later.
- **MUST** Identity does not use long-lived static keys: CI uses OIDC federation, workloads use managed / workload identity. If a static key cannot be avoided, it has an expiry date and is rotated.
- **MUST** Standard tags / labels (`Environment`, `Owner`, `Project`, `ManagedBy`) to track cost and ownership.
- **SHOULD** Services that hold data (database, storage, key vault) are not public. Access them through a private endpoint / private link / private network.
- **SHOULD** Encryption at rest is on by default (usually built in). Customer-managed keys (CMK) are **CONTEXT**: use them when compliance requires it.
- **SHOULD** Set a budget and cost alerts from day one (see skill `finops`).
- **SHOULD** Plan CIDRs once for all environments. Avoid overlap with networks you will peer / VPN / connect on-prem. Changing a CIDR later usually means rebuilding.

## Provider references

Read the matching file in `references/` when you work with that provider:

- Azure (including AKS): `references/azure.md`. To build AKS, also read skill `playbook-aks`.
- AWS (including EKS): `references/aws.md`
- GCP (including GKE): `references/gcp.md`
- Hetzner: `references/hetzner.md`
- OVHcloud: `references/ovh.md`
- On-premise / bare metal: `references/on-premise.md`

The reference files describe the **design direction**. Terraform attribute names and specific features change between provider versions: check the provider docs for the exact version before you write code.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall