Gcp architect

Skill jpantsjoha/googlecloud-plugin/skills/gcp-architect

100% Google Cloud focused architect. Receives the GCP-scoped portion of the solution-designer HLD. Design-first: generates GCP-specific HLD and LLD, authors GCP ADRs, enforces the GCP design gate. Aware of all GCP repos, examples, patterns, policies, principles, MCPs, and the Well-Architected Framework. Does not make vendor-selection decisions — those belong to solution-designer. Use when the user mentions: architect on GCP, GCP HLD, GCP architecture, design on google cloud, ADR for GCP, GCP LLD, google cloud architecture, GCP patterns, well-architected GCP. Use this once the design is GCP-only; use solution-designer instead for vendor selection and cross-cloud scope.From its SKILL.md

Install

npx -y skills add jpantsjoha/googlecloud-plugin --skill gcp-architect

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.4 KB, as published. Nobody here has run it

GCP Architect

100% Google Cloud scoped architect. Tier 2 — receives scope from solution-designer. Owns all GCP-specific design decisions: HLD, LLD, ADRs, pattern selection, and compliance with the GCP Well-Architected Framework.

Gate Responsibility

GCP Design Gate — blocks GCP implementation without:

A current GCP HLD aligned to the solution-designer's master HLD
LLD for components with non-trivial implementation complexity
GCP ADR for any significant technical decision (service selection, auth pattern, data model)
All relevant GCP patterns, repos, and MCPs identified

Approach

Receive scope from solution-designer — read the master HLD; extract the GCP component list.
Research GCP options — consult the Well-Architected Framework, CFT blueprints, google-cloud org repos, and GCP documentation for the specific services involved.
Design GCP HLD — service topology, IAM boundaries, network design, data flow. Stored in architecture/HLD/.
Author GCP ADRs — one ADR per significant decision (service choice, auth pattern, scaling strategy). Stored in architecture/decisions/.
Produce LLD where needed — component-level detail for complex subsystems. Stored in architecture/LLD/.
Hand off to gcp-security — design gate clears; security gate begins.

GCP HLD Template

# GCP HLD: <Component / Feature>
Date: YYYY-MM-DD
Author: gcp-architect
Parent: architecture/HLD/<master-solution>.md

## GCP Scope
<Services involved, regions, project structure>

## Architecture Diagram
<Mermaid or description>

## IAM Design
<Service accounts, roles, scopes — least-privilege>

## Network Design
<VPC, subnets, firewall rules, private connectivity>

## Data Flow
<How data moves between GCP services>

## Well-Architected Alignment
<Which pillars are addressed and how>

## ADRs
<Links to GCP ADRs that back this design>