using-cloud-foundation-principles
/using-cloud-foundation-principles
Wskazuje, który z piętnastu skilli zasad chmury stosować, i zapewnia ich wywołanie przed pracą nad infrastrukturą lub Terraformem.
- Autor
- oborchers ↗
- Repozytorium
- fractional-cto ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 25.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 25.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Wskazuje, który z piętnastu skilli zasad chmury stosować, i zapewnia ich wywołanie przed pracą nad infrastrukturą lub Terraformem.
Wyzwalacze z opisu
Oryginalny opis (EN)
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.
Jak działa
- How to Access Skills
- Available Skills
- When to Invoke Skills
- The Three Meta-Principles
Podgląd SKILL.md
--- 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.
Wersje
W bazie nie ma innych skilli o nazwie using-cloud-foundation-principles.
Migawka bazy z 13.11.2026 · wersja paczki 2973c5960417 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 90using-saas-principles
Wskazuje dwanaście zasad projektowania SaaS i dobiera właściwe przed pracą nad interfejsem aplikacji abonamentowej. - 90using-visual-design-principles
Wskazuje jedenaście zasad projektowania wizualnego i dobiera je do oceny projektu przed pracą nad grafiką. - 100google-cicd-terraform
Projektuje, wdraża i diagnozuje infrastrukturę Google Cloud w Terraform, z backendem GCS, IAM o najmniejszych uprawnieniach i wzorcami Cloud Foundation Fabric. - 100terraform-iac
Zarządza infrastrukturą chmurową w Terraform i OpenTofu: pisze konfiguracje i moduły, obsługuje stan, import istniejących zasobów, wiele środowisk oraz błędy plan i apply. - 90cloud-and-infrastructure
Pilnuje kodu Terraform i innych IaC, Dockerfile, Kubernetes, funkcji serverless, polityk IAM oraz kosztów chmury w repozytorium aidd. - 95cloud-infrastructure-iac
Pomaga w architekturze chmury i IaC: Terraform, OpenTofu, Pulumi, Kubernetes, sieci, IAM, magazyny i kontrolę kosztów.