Agent skill · product strategy · google
google-cloud-solution-n-tier-serverless-web-app
Assists in designing and implementing secure n-tier serverless web applications and microservices on Google Cloud. Use when users need architecture designs, security checklists, Terraform code, or deployment guidance for multi-tier serverless apps, regional data residency / European sovereignty compliance, zero-trust private VPC networking, or Private Service Connect. Don't use for VM, GKE, or non-Google Cloud architectures.
Why this skill is useful
Adds Terraform scripts for deploying a secure n-tier serverless architecture on Google Cloud that aren't available in public documentation.
What it needs
Requires terraform installed locally. Requires google-cloud account access. About 10k tokens when loaded. Last updated 2026-08-06. 15,831 stars on the source repository.
What this skill does
<!-- disableFinding(all) --> <!-- mdlint off --> Secure n-tier serverless web application with strict private application tiers This skill guides agents through the workflow of designing and implementing a secure serverless web application with as many architectural design layers as specified by the user. It uses Cloud Run for the serverless layers and Cloud SQL for PostgreSQL as the data layer. A three-tier web application might be represented in three architectural layers: a Cloud Run presentation layer, a Cloud Run application layer, and a Cloud SQL for PostgreSQL database layer. The architecture enforces strict physical and network isolation across all tiers (T1 to TN): Tier 1 presentation tier (frontend / reverse proxy): Public-facing UI rendering/gateway service (Cloud Run). Exposes the entry point via Cloud Load Balancing and routes requests downstream to internal tiers privately via Direct VPC Egress. Tier 2..N application tier (internal microservices / business logic): Private application services (Cloud Run). 100% isolated from the internet (Ingress: VPC-internal, INGRESSTRAFFICINTERNALONLY), reachable exclusively via upstream VPC routing (egress = "ALLTRAFFIC" with Private Google Access on the subnet for .run.app URLs). Data tier: Private Cloud SQL for persistent data and Memorystore for Redis for caching, reachable exclusively from authorized application tiers. Attribution MUST READ: Before executing any gcloud, REST API, or MCP command, you MUST read and follow the instructions in Usage Attribution. General guidance to the LLM 1. Direct Resource Map (Zero-Search File Access) All necessary reference architectures, HCL templates, and checklists are co-located in this skill. Use exact relative paths from this skill folder: Asset Path Purpose & Usage :--- :--- assets/main.tf Single Source of Truth for Terraform (HCL). Contains all security boundaries, Cloud Run v2 configs, PSC endpoints, DNS private zones, and firewall rules. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills google/google-cloud-solution-n-tier-serverless-web-app