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
- avelikiy/great_ctotheir own version, first seen Sep 5, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- avelikiy/great_cto★ 115same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- agent-architectSkill
- bigquerySkill
- cloud-runSkill
- cloud-storageSkill
- gcloud-guardrailsSkill
- gcp-architectSkill
- gcp-opsSkill
- gcp-project-contextSkill
- gcp-qaSkill
- gcp-securitySkill
- gkeSkill
- google-skills-catalogSkill
- iamSkill
- logging-monitoringSkill
- mcp-serversSkill
- networkingSkill
- solution-designerSkill
- terraform-gcpSkill
- vertex-aiSkill
The file
Files
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
| Pillar | Core Question | Key Practices |
| Operational Excellence | Can we build, run, and evolve the system reliably? | IaC, CI/CD, runbooks, monitoring-as-code |
| Security | Is the system protected against threats? | Least-privilege IAM, encryption, no public exposure by default |
| Reliability | Will the system recover from failures? | Multi-region, health checks, SLOs, chaos testing |
| Cost Optimization | Are we spending efficiently? | Right-sizing, committed use, lifecycle policies, budget alerts |
| Performance | Can the system handle load and scale? | Autoscaling, CDN, caching, regional proximity |
| Sustainability | Are 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
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
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.

