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

references/azure.md

View on GitHub
# Azure

<!-- Last reviewed: 2026-10-28 -->

## Baseline
- **MUST** Terraform state in the `azurerm` backend, with Entra ID auth (`use_azuread_auth = true`). The state storage account has versioning + soft delete, and no public blob access.
- **MUST** Workloads on Azure use Managed Identity / Workload Identity. Do not use service principal secrets when there is another option.
- **MUST** Key Vault uses RBAC authorization, with soft-delete and purge protection turned on.
- **SHOULD** PaaS that holds data (Azure SQL / PostgreSQL Flexible Server, Storage Account, Key Vault): Private Endpoint + Private DNS Zone, public network access turned off.
- **SHOULD** NSGs are attached at subnet level. Do not open SSH/RDP to the Internet (use Bastion / VPN / JIT).
- **SHOULD** Budget + alerts at subscription or resource group level.

## Production
- **SHOULD** Use Availability Zones for important parts (AKS node pools, databases, LB).
- **SHOULD** Diagnostic settings send logs to Log Analytics, but **choose carefully**: Log Analytics ingestion is often the biggest surprise cost (see `finops`).
- **SHOULD** Azure Backup / app-level backup with tested restores (see `disaster-recovery`).
- **CONTEXT** Microsoft Defender for Cloud, depending on security needs and budget.
- **AKS:** see skill `playbook-aks` (CNI Overlay, Workload Identity, Entra ID + Azure RBAC, separate system node pool).

## Enterprise landing zone (only with many teams / subscriptions)
- Management Group hierarchy: `Root` → `Platform` (Identity, Management, Connectivity) → `Landing Zones` (Corp, Online) → subscriptions per workload.
- Hub-spoke network (Azure Firewall, VPN / ExpressRoute Gateway in the hub; spokes peered to the hub), or Virtual WAN with many regions / many branches.
- Azure Policy assigned at Management Group level: required tags, allowed regions / SKUs, no public IPs in the Corp landing zone.
- Subscription vending (create standard subscriptions with IaC) when there are many subscriptions.
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: 197kUpdated 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