Skip to content
Skills Library
DevOps & cloud · Learning & explanation

using-cloud-foundation-principles

/using-cloud-foundation-principles

This skill should be used when the user asks "which cloud foundation skill should I use", "show me all cloud principles", "help me pick an infrastructure pattern", or at the start of any cloud infrastructure, Terraform, or IaC conversation. Provides the index of all fifteen principle skills and ensures the right ones are invoked before any cloud infrastructure work begins.

Licence
MIT
Last repository change
25.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

This skill should be used when the user asks "which cloud foundation skill should I use", "show me all cloud principles", "help me pick an infrastructure pattern", or at the start of any cloud infrastructure, Terraform, or IaC conversation. Provides the index of all fifteen principle skills and ensures the right ones are invoked before any cloud infrastructure work begins.

Triggers from the description

which cloud foundation skill should I useshow me all cloud principleshelp me pick an infrastructure pattern
Original author description

This skill should be used when the user asks "which cloud foundation skill should I use", "show me all cloud principles", "help me pick an infrastructure pattern", or at the start of any cloud infrastructure, Terraform, or IaC conversation. Provides the index of all fifteen principle skills and ensures the right ones are invoked before any cloud infrastructure work begins.

How it works

  1. How to Access Skills
  2. Available Skills
  3. When to Invoke Skills
  4. The Three Meta-Principles
Original SKILL.md headings · 55 lines, 563 words
SKILL.md preview
---
name: using-cloud-foundation-principles
description: This skill should be used when the user asks "which cloud foundation skill should I use", "show me all cloud principles", "help me pick an infrastructure pattern", or at the start of any cloud infrastructure, Terraform, or IaC conversation. Provides the index of all fifteen principle skills and ensures the right ones are invoked before any cloud infrastructure work begins.
version: 1.0.0
---

<IMPORTANT>
When working on any cloud infrastructure pattern — account structure, naming conventions, Terraform organization, networking, security, credentials, secrets, deployment pipelines, or operational processes — invoke the relevant cloud-foundation-principles skill BEFORE writing or reviewing code.

These are not suggestions. They are battle-tested, opinionated principles drawn from production experience scaling cloud infrastructure across multiple migrations, hundreds of services, and teams of every size. Each principle exists because its absence caused real, expensive damage.
</IMPORTANT>

## How to Access Skills

Use the `Skill` tool to invoke any skill by name. When invoked, follow the skill's guidance directly.

## Available Skills

| Skill | Triggers On |
|-------|-------------|
| `cloud-foundation-principles:multi-account-from-day-one` | Account structure, environment isolation, governance setup, organization units, landing zones |
| `cloud-foundation-principles:naming-and-labeling-as-code` | Resource naming, tagging, cost centers, labels module, naming conventions, cost attribution |
| `cloud-foundation-principles:architecture-decision-records` | Decision documentation, ADRs, exemptions, context preservation, technical decision tracking |
| `cloud-foundation-principles:repository-and-state-strategy` | Terraform repo structure, numbered layers, state-per-layer isolation, cross-layer references, blast radius |
| `cloud-foundation-principles:terraform-module-patterns` | Module design, wrapping community modules, smart defaults, validation, version pinning, conditional creation |
| `cloud-foundation-principles:network-architecture` | VPC/VNet design, subnet tiers, API gateways, DNS, routing, NAT, VPC endpoints, private connectivity |
| `cloud-foundation-principles:zero-static-credentials` | SSO setup, OIDC federation, no API keys, no VPN, no SSH keys, identity management, CI/CD auth |
| `cloud-foundation-principles:security-monitoring-from-day-one` | Threat detection, compliance scanning, security hub, guard duty, centralized security account |
| `cloud-foundation-principles:secrets-and-configuration-management` | Secrets rotation, config vs credentials, parameter stores, secret managers, access patterns |
| `cloud-foundation-principles:managed-services-over-self-hosted` | Managed vs self-hosted, container orchestration, workflow engines, caches, databases |
| `cloud-foundation-principles:service-owned-infrastructure` | Service teams own IaC, no central bottleneck, per-service Terraform, shared modules |
| `cloud-foundation-principles:container-image-tagging` | Docker image tags, git SHA traceability, registry lifecycle policies, image metadata, OCI labels |
| `cloud-foundation-principles:tag-based-production-deploys` | Production release triggers, git tags vs branches, manual approval gates, pipeline stages, pre-commit hooks |
| `cloud-foundation-principles:unified-cicd-platform` | CI/CD platform consolidation, single pipeline platform, OIDC pipeline auth, eliminating multi-provider ops burden |
| `cloud-foundation-principles:operational-hygiene` | Resource cleanup, cost attribution, monitoring, drift detection, lifecycle policies |

## When to Invoke Skills

Invoke a skill when there is even a small chance the work touches one of these areas:

- Setting up a new cloud project, account, or environment
- Writing or modifying Terraform, OpenTofu, Pulumi, or CloudFormation code
- Designing network topology, subnets, or routing
- Configuring authentication, authorization, or credential management
- Setting up CI/CD pipelines for infrastructure deployment
- Building or tagging container images for deployment
- Making architectural decisions about managed services vs self-hosted
- Reviewing existing infrastructure code for quality, security, or cost
- Organizing repositories, state files, or module structures

## The Three Meta-Principles

All fifteen principles rest on three foundations:

1. **Governance before infrastructure** — Naming conventions, account structure, and decision records must exist before the first resource is created. Skipping governance on day one creates debt that compounds every day.

2. **Everything in code, no exceptions** — Infrastructure not in code is a liability. Every resource, every permission, every configuration must be version-controlled, reviewable, and reproducible. If it can't be in code yet, document why in an ADR.

3. **Prevent day-1 mistakes that become day-100 catastrophes** — Some decisions are cheap to make on day one and catastrophically expensive to fix later. Multi-account isolation, naming conventions, and state separation are the canonical examples. This plugin exists to ensure you make them on day one.

Versions

The database has no other skills named using-cloud-foundation-principles.

Database snapshot: 13.11.2026 · package version 2973c5960417 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90using-saas-principles
    This skill should be used when the user asks "which SaaS design skill should I use", "show me all design principles", "help me pick a design pattern", or at the start of any SaaS-related conversation. Provides the index of all twelve principle skills and ensures the right ones…
  • 90using-visual-design-principles
    This skill should be used when the user asks 'which visual design skill should I use', 'show me all design principles', 'help me evaluate a design', or at the start of any visual design conversation. Provides the index of all eleven principle skills and ensures the right ones…
  • 100google-cicd-terraform
    Architect, provision, and troubleshoot infrastructure on Google Cloud using Terraform. This skill ensures best practices like GCS backend usage and least-privilege IAM are followed. Enforces Google’s Cloud Foundation Fabric patterns and rigorous validation protocols to ensure…
  • 100terraform-iac
    Manages cloud infrastructure using Terraform (and OpenTofu). Use when the user wants to write Terraform configurations, provision cloud resources, manage state, create modules, set up multi-environment deployments, import existing infrastructure, debug plan/apply errors, migrate…
  • 90cloud-and-infrastructure
    In an aidd repository, use when code touches Terraform or other IaC, Dockerfiles, Kubernetes, serverless functions, IAM policies, or cloud cost.
  • 95cloud-infrastructure-iac
    Use this capability for cloud architecture, IaC, Terraform/OpenTofu/Pulumi, Kubernetes, networking, VPC/VNet, IAM, compute, storage, managed databases, queues, cost controls, policy-as-code, drift detection, and infrastructure review.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.