agentleFS
pathiec92pathiec92/claude-skills/skills/gcp-architecture/SKILL.md

gcp-architecture

Skill0 starsChanged 5 months agoMITView on GitHub

Design or evaluate solutions on Google Cloud Platform — selecting GCP services, estimating cost and operational burden, and explaining IAM implications. Use when the work targets GCP or mentions Cloud Run, GKE, Pub/Sub, BigQuery, AlloyDB, or "how should I deploy/run this on GCP". Applies a managed-services-first bias. NOT for cloud-agnostic or AWS/Azure designs.

The file

Files
SKILL.md

GCP Architecture Principles

Service selection (preferred order)

  1. Managed / serverless services
  2. Cloud Run
  3. GKE — only when genuinely required

Favor

  • Pub/Sub for async decoupling
  • Cloud Run for stateless services
  • AlloyDB / Cloud SQL for relational
  • BigQuery for analytics

Avoid

  • Premature Kubernetes complexity
  • Running stateful systems you could buy as managed

For every design, state

  • Cost estimate (and primary cost drivers)
  • Operational burden
  • IAM implications (least-privilege service accounts, workload identity)

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.