agentleFS
jpantsjohajpantsjoha/googlecloud-plugin/skills/well-architected/SKILL.md

well-architected

Skill4 starsChanged 4 months agoMITView on GitHub

Google Cloud Well-Architected Framework reference. Six pillars: operational excellence, security, reliability, cost optimization, performance, and sustainability. Referenced by gcp-architect and gcp-security for every design review. Use when the user mentions: GCP framework, architecture pillars, reliability GCP, cost optimization GCP, performance GCP, sustainability GCP, WAF review.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

GCP Well-Architected Framework

Six pillars that every GCP workload should be evaluated against. Referenced in every HLD, security review, and operational readiness check.

The Six Pillars

PillarCore QuestionKey Practices
Operational ExcellenceCan we build, run, and evolve the system reliably?IaC, CI/CD, runbooks, monitoring-as-code
SecurityIs the system protected against threats?Least-privilege IAM, encryption, no public exposure by default
ReliabilityWill the system recover from failures?Multi-region, health checks, SLOs, chaos testing
Cost OptimizationAre we spending efficiently?Right-sizing, committed use, lifecycle policies, budget alerts
PerformanceCan the system handle load and scale?Autoscaling, CDN, caching, regional proximity
SustainabilityAre we minimizing environmental impact?Carbon-aware regions, efficient resource use

Quick Review Checklist (per design)

Operational Excellence

  • Infrastructure as Code (Terraform or Config Connector)
  • CI/CD pipeline with automated tests
  • Runbook for each primary failure mode
  • Alerting tied to SLOs

Security

  • Least-privilege IAM throughout
  • No public exposure without intent
  • Secrets in Secret Manager
  • Network deny-by-default

Reliability

  • SLO defined (availability + latency)
  • Health checks configured
  • Multi-zone or multi-region for production
  • Backup and recovery tested

Cost Optimization

  • Right-sized instances (use GCP recommender)
  • Committed use discounts evaluated
  • Budget alerts configured
  • Lifecycle policies on storage

Performance

  • Load tested at target traffic
  • Caching layer evaluated
  • CDN for static assets
  • Autoscaling configured

Sustainability

  • Low-carbon region selected where latency allows
  • Idle resources scheduled for shutdown

References

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.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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.