Przejdź do treści
Biblioteka skilli
DevOps i chmura · Przegląd i audyt

cloud-and-infrastructure

/cloud-and-infrastructure

Pilnuje kodu Terraform i innych IaC, Dockerfile, Kubernetes, funkcji serverless, polityk IAM oraz kosztów chmury w repozytorium aidd.

Repozytorium
aidd ↗
Licencja
Apache-2.0
Ostatnia zmiana repozytorium
12.11.2026

Ocena i bezpieczeństwo

90/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść25 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
3
Skrypty
0
Komentarze HTML
1
Adresy URL w SKILL.md
8
Przestarzałość

Brak sygnałów. Repozytorium zmienione 12.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

Co sprawdzić przed instalacją
  • SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.

Co robi i kiedy

Pilnuje kodu Terraform i innych IaC, Dockerfile, Kubernetes, funkcji serverless, polityk IAM oraz kosztów chmury w repozytorium aidd.

Oryginalny opis (EN)

In an aidd repository, use when code touches Terraform or other IaC, Dockerfiles, Kubernetes, serverless functions, IAM policies, or cloud cost.

Jak działa

  1. Scope
  2. Standards
  3. Checklist by loop step
  4. Test commands
  5. Owned elsewhere
  6. References
  7. Keep it current
Sekcje z nagłówków SKILL.md, w oryginale · 65 linii, 1 026 słów
Podgląd SKILL.md
---
name: cloud-and-infrastructure
description: "In an aidd repository, use when code touches Terraform or other IaC, Dockerfiles, Kubernetes, serverless functions, IAM policies, or cloud cost."
---

<!-- generated by `aidd gen-docs` from schemas/packs.json; edit the registry, not this file -->

# Cloud and infrastructure

## Scope

Applies when the change touches IaC, containers, Kubernetes, functions, IAM, or cloud cost. Not when the change only reads configuration the platform already provides. Neighbours: `aidd-team:ci-pipeline`, `aidd-team:release-rollout`, `aidd-packs:enterprise-controls`.

## Standards

| # | Standard | Edition | Checked | Source |
| --- | --- | --- | --- | --- |
| S1 | The host's Well-Architected framework or reference architectures | AWS 2024-11-06; Google Cloud 2026-01-28; Cloudflare 2026-06-05; Azure, living | 2026-10-16 | <https://docs.aws.amazon.com/wellarchitected/latest/framework/welcome.html> |
| S2 | FinOps Framework: budgets, allocation by tags, and unit cost | FinOps Framework 2026 | 2026-10-16 | <https://www.finops.org/framework/> |
| S3 | CIS Benchmarks | — | 2026-10-16 | <https://www.cisecurity.org/cis-benchmarks> |
| S4 | Kubernetes Pod Security Standards: workloads at the `restricted` Pod Security profile | — | 2026-10-16 | <https://kubernetes.io/docs/concepts/security/pod-security-standards/> |
| S5 | CIS Kubernetes Benchmark | 2.0.1 | 2026-10-16 | <https://www.cisecurity.org/benchmark/kubernetes> |
| S6 | Policy as code (Open Policy Agent, Kyverno) | — | 2026-10-16 | <https://www.openpolicyagent.org/docs> |
| S7 | AWS Well-Architected Sustainability Pillar | 2024-11-06 | 2026-10-17 | <https://docs.aws.amazon.com/wellarchitected/latest/sustainability-pillar/sustainability-pillar.html> |
| S8 | Software Carbon Intensity (SCI) | SCI 1.1.0; ISO/IEC 21031:2024 | 2026-10-22 | <https://sci.greensoftware.foundation/> |

## Checklist by loop step

| Step | Item | Standard |
| --- | --- | --- |
| Before the first edit (`aidd risk --paths`) | CI/CD files are in the `ci` area, and IaC, containers, and manifests in `infra`: normal, each edit reported, unless the author declares higher. `infra.apply` and `deploy.run` ask. | S1 |
| Before the first edit (`aidd risk --paths`) | An IAM change or new network exposure (a public bucket, an open port) is major: the author declares it. | S3, S6 |
| Specify | The plan or dry-run output is in the Acceptance; blast radius and rollback (previous version, previous state) are named. | S1 |
| Specify | A stateful service (database, bucket, queue holding data) states its RTO and RPO, and has a restore runbook (`restores_data: true`, `rto`, `rpo`). A person runs it as a restore drill from real backups into a scratch environment. `aidd doctor` warns when `tested_on` passes `docs.max_runbook_age_days`. | S1 |
| Specify | Placement (functions, containers, VMs, edge) chosen with references/cost-and-performance.md. A monthly estimate at today's load and at 10x, in the Context or the tech spec's Scale and cost row, within `project.budget`. `aidd validate` warns on none, or one over `max_infra_per_month`. | S1, S2 |
| Specify | Sustainability: idle environments scale to zero, region and instance type weigh carbon beside cost where the provider publishes it, and a Spec with a carbon target reports SCI per functional unit. | S7, S8 |
| Implement | Least privilege on every identity; no long-lived secret (OIDC); images pinned by digest, and their signatures checked at admission where the platform can. | S3, S4, S6 |
| Implement | Allocation tags (environment, service, owner) on every resource. Where the IaC defines cloud resources: a budget with an alert per environment, and non-production that scales to zero. A concurrency or instance cap on every function and autoscaler, and pooled database connections. | S2, S1 |
| Review | The plan matches the Spec: no resource deleted or replaced, and no cost increase, that the Spec did not name. | S6, S2 |
| Roll out | Progressive rollout (canary or blue-green) with automatic rollback on the SLO where the host supports it, otherwise the rollback runbook. A drift check after apply; actual cost by tag against the estimate in the observe window, an unexplained gap a Learn action. | S1, S2 |

## Test commands

| Command | Proves | How | Standard |
| --- | --- | --- | --- |
| IaC scanning | no high finding in the infrastructure code | `uvx checkov==3.3.20 -d .`, a Trivy config scan, or KICS | S3 |
| Policy as code | the plan or manifests pass the policies | the `policy-tool`'s tests entry, such as `conftest test` over OPA policies, or Kyverno | S6 |
| Manifest lint | Pod Security Standards and best practices hold | `kube-linter lint .` (kube-linter v0.8.3) or Polaris | S4, S5 |
| Plan or dry-run check | no resource is destroyed or replaced that the Spec did not name | a script over `terraform show -json`, `pulumi preview --json` (Pulumi v3.265.0), `npx aws-cdk@2.1143.0 diff --fail`, or `npx wrangler@4.148.0 deploy --dry-run` failing on an unnamed destroy or replace; the plan attached for the reviewer | S1 |
| Cost diff threshold | the cost change is what the Spec states; the total is within `max_infra_per_month` | Optional: the `cost-estimate-tool`'s tests entry, such as Infracost's `scan <dir> --json` on base and head failing when `summary.total_monthly_cost` passes the Spec's change or limit, or the provider's calculator. Infracost sends resource parameters to its pricing API or a self-hosted `INFRACOST_CLI_PRICING_ENDPOINT` | S2 |
| Tag and budget policy | every resource has the allocation tags; each environment, a budget with an alert | For Terraform or OpenTofu: the `policy-tool`'s tests entry over `terraform show -json`, denying an untagged resource and an environment without a budget | S2, S6 |
| IAM and exposure check | no wildcard action on a wildcard resource, no public principal, no admin port open to the internet | the `policy-tool`'s rules over the `iac-tool`'s plan | S6, S3 |

- From `aidd-packs:enterprise-controls`: Container scan and SBOM.

## Owned elsewhere

- Build provenance (SLSA) and the pipeline that produces it: `aidd-team:ci-pipeline`.
- A published project's OpenSSF Scorecard and OSPS Baseline: `aidd-packs:package-publishing`.

## References

- [references/cost-and-performance.md](references/cost-and-performance.md): the placement guide, the provider map, limits and price links, and the break-even worksheet.
- [references/open-choices.md](references/open-choices.md): its open choices, with aidd's defaults.

## Keep it current

Each entry is due after its `review_every_days` (else emerging 90 days, established 365) or by its `review_due`. An emerging one applies only when the change needs it, said in the Spec. One `aidd eval standards` lists as due is looked up in Specify, and a missing one is proposed to aidd's `schemas/industry-standards.json`.
Pliki w paczce (3)
  • SKILL.md 7 KB
  • references/cost-and-performance.md 4 KB
  • references/open-choices.md 4 KB

Wersje

W bazie nie ma innych skilli o nazwie cloud-and-infrastructure.

Migawka bazy z 13.11.2026 · wersja paczki 885067b03eb7 (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

  • 95cloud-infrastructure-iac
    Pomaga w architekturze chmury i IaC: Terraform, OpenTofu, Pulumi, Kubernetes, sieci, IAM, magazyny i kontrolę kosztów.
  • 90cloud-infrastructure
    Projektuje infrastrukturę chmurową i pisze IaC: moduły Terraform, konstrukty AWS CDK, architektury VPC, load balancerów, serverless, wielu regionów i DR, analiza kosztów oraz przegląd kodu IaC.
  • 100cloud-infrastructure
    Pomaga przy zakładaniu zasobów chmurowych, wyborze usług AWS (Lambda, ECS, EKS), pisaniu CDK i IaC, projektowaniu architektur serverless i kontenerowych, konfiguracji IAM oraz optymalizacji kosztów.
  • 100infrastructure-coder
    Generuje, przegląda, porównuje pod względem kosztów i skanuje pod kątem bezpieczeństwa kod infrastruktury w Terraform, Kubernetes i Docker; nie obejmuje CI/CD ani kodu aplikacji.
  • 100infrastructure-engineer
    Projektuje i wdraża infrastrukturę chmurową: architekturę, IaC (Terraform, Pulumi), potoki CI/CD, Kubernetes, sieci, obserwowalność i utwardzanie bezpieczeństwa.
  • 90iac-security-auditor
    Audytuje infrastrukturę jako kod i konfigurację uruchomieniową (Dockerfile, manifesty Kubernetes, Terraform, pipeline'y CI/CD, ustawienia chmury) pod kątem błędnych konfiguracji i luk w utwardzaniu.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.