agentleFS
Sign inStart free
ulises-jeremiasulises-jeremias/agent-toolkit/skills/cloud/cloud-design-patterns/SKILL.md

cloud-design-patterns

Skill19 starsChanged 2 months agoMITView on GitHub

WHAT — Vendor-neutral distributed cloud patterns (Retry, Bulkhead, Circuit Breaker, CQRS, Event Sourcing, etc.) abstracted from AWS/Azure/GCP sources — when to apply, tradeoffs, mapping to AWS/GCP/Azure primitives. Offline checklist, no live account required.

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not paste Azure pattern dump verbatim — abstract.

    line 37
  2. Very specific:

    Do not conflate generic pattern with Terraform/K8s/Helm deployment (those are official CLI terraform/kubectl/helm — see research).

    line 38

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Cloud Design Patterns (WHAT — vendor-neutral)

Sources (2026-08-12): AWS Well-Architected https://docs.aws.amazon.com/wellarchitected/latest/framework/the-pillars-of-the-framework.html (6 pillars), https://aws.amazon.com/architecture/well-architected/; abstracted from Azure Architecture Center cloud design patterns (Circuit Breaker, CQRS, Sidecar etc.) per §43 — do NOT dump Azure catalog verbatim; https://docs.microsoft.com/en-us/azure/architecture/patterns/.

Pack: Vendor-neutral architecture core (architect + ADR + TRD + threat-model + mermaid (+ C4)) stays AWS-neutral. cloud-architecture is optional pack/docs-only that composes cloud-design-patterns + aws-well-architected-review + mermaid on top of architecture. See docs/cloud/research-384-candidates.md for ADOPT/REJECT + pack semantics (ADR-0003).

When to use

  • Designing distributed system (retry, bulkhead, leader election, saga, event sourcing) without vendor lock.
  • Need mapping to AWS/GCP/Azure primitives without dumping provider-specific dump.

Instructions

  1. Select pattern from minimal catalog (abstracted): Retry/Backoff, Bulkhead, Circuit Breaker, CQRS, Event Sourcing, Saga, Sidecar, Strangler Fig, Leader Election, Throttling.
  2. Evaluate via Well-Architected lenses: operational excellence, security, reliability, performance, cost, sustainability.
  3. Map to primitives: e.g., Retry → AWS SQS+Lambda retry, GCP Cloud Tasks, Azure Service Bus; Circuit Breaker → Resilience4j/Polly/AWS App Mesh.
  4. Reference aws-well-architected-review for pillar check when on AWS; otherwise keep vendor-neutral.

Anti-patterns

  • Do not paste Azure pattern dump verbatim — abstract.
  • Do not conflate generic pattern with Terraform/K8s/Helm deployment (those are official CLI terraform/kubectl/helm — see research).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free