Plan, create, and configure production-ready Google Kubernetes Engine (GKE) clusters using the golden path Autopilot configuration. Covers Day-0 checklist, Autopilot vs Standard, networking (private clusters, VPC-native, Gateway API), security (Workload Identity, Secret Manager, RBAC hardening), observability, scaling, cost optimization, and AI/ML inference. WHEN: create GKE cluster, provision GKE environment, design GKE networking, secure GKE, optimize GKE cost, GKE autoscaling, GKE inference, GKE upgrade, GKE observability, GKE multi-tenancy, GKE batch, GKE HPC, GKE compute class.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
GKE is a managed Kubernetes platform on Google Cloud for deploying, scaling, and operating containerized applications. This skill defaults to the golden path Autopilot configuration — see gke-golden-path.md for defaults, rules, and guardrails.
gcloud services enable container.googleapis.com --quiet
gcloud container clusters create-auto my-cluster --region=us-central1 --quiet
gcloud container clusters get-credentials my-cluster --region=us-central1 --quiet
kubectl create deployment hello-server \
--image=us-docker.pkg.dev/google-samples/containers/gke/hello-app:1.0
Load the relevant reference based on trigger keywords. Prefer the most specific match; if ambiguous, ask the user to clarify.
| Scenario | Trigger Keywords | Reference |
|---|---|---|
| Core Concepts | Autopilot vs Standard, architecture, pricing, what is GKE | core-concepts.md |
| Golden Path & Defaults | golden path, Day-0 checklist, production defaults, cluster defaults | gke-golden-path.md |
| Cluster Creation | create cluster, new cluster, provision GKE | gke-cluster-creation.md |
| Networking | private cluster, VPC, subnet, Gateway API, DNS, ingress, egress, datapath | gke-networking.md |
| Security & IAM | Workload Identity, Secret Manager, RBAC, Binary Auth, hardening, audit, gVisor, IAM roles | gke-security.md |
| Scaling | HPA, VPA, autoscaler, autoscaling, NAP, scale pods, scale nodes | gke-scaling.md |
| Compute Classes | ComputeClass, machine family, Spot fallback, GPU node pool, node selection | gke-compute-classes.md |
| Cost | cost, savings, Spot VMs, rightsizing, CUD, optimize spend, budget | gke-cost.md |
| AI/ML Inference | inference, model serving, LLM, GPU, TPU, GIQ, vLLM | gke-inference.md |
| Upgrades | upgrade, maintenance window, release channel, patching, version | gke-upgrades.md |
| Observability | monitoring, logging, Prometheus, Grafana, metrics, alerts, dashboards | gke-observability.md |
| Multi-tenancy | multi-tenant, namespace isolation, team access, enterprise, RBAC planning | gke-multitenancy.md |
| Batch & HPC | batch, HPC, job queue, high performance, MPI, parallel | gke-batch-hpc.md |
| App Onboarding | containerize, deploy app, Dockerfile, onboard, migrate to GKE | gke-app-onboarding.md |
| Backup & DR | backup, restore, disaster recovery, CMEK | gke-backup-dr.md |
| Storage | storage, PVC, persistent volume, StorageClass, Filestore, GCS FUSE | gke-storage.md |
| Reliability | PDB, health probe, liveness, readiness, topology spread, graceful shutdown | gke-reliability.md |
| Client Libraries | client library, client-go, kubernetes python, kubernetes java, kubernetes SDK | client-library-usage.md |
| Infrastructure as Code | Terraform, IaC, HCL, infrastructure as code | iac-usage.md |
| MCP Server | MCP tools, MCP server, MCP setup | mcp-usage.md |
| CLI / Tools | gcloud, kubectl, commands, how to | cli-reference.md |
| Production Audit | production readiness, compliance, golden path check | gke-cluster-creation.md |
If you need product information not found in these references, use the Developer Knowledge MCP server search_documents tool.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Design, implement, and audit inclusive digital products using WCAG 2.2 Level AA standards. Use this skill to generate semantic ARIA for Web and accessibility traits for Web and Native platforms (iOS/Android).
日本語の概要は準備中です。原文の説明を表示しています。
Whole site or product — a full web accessibility (a11y) audit against WCAG 2.2, following the WCAG-EM methodology. Defines scope, samples representative pages and flows, runs the automated tier (`accessibility-scan`) and the hands-on manual tier (`accessibility-inspect`), and produces one conformance report. Grades each finding by severity and evidence basis, and states per-criterion conformance as pass, fail, or undetermined (needs a human). Use it for 'audit my site for accessibility', 'is this product accessible', 'a11y audit', 'WCAG or Section 508 conformance report', or any multi-page assessment. Assesses; does not fix (use `accessibility-fix`) or diff (use `accessibility-diff`). For a single page use `accessibility-scan`; for hands-on keyboard and screen-reader checks use `accessibility-inspect`.
日本語の概要は準備中です。原文の説明を表示しています。
Regression check — diff a live page's web accessibility (a11y) violations against a baseline. By default it compares your uncommitted changes (stash-based); pass `--branch [<name>]` to compare against a branch. Reports the new WCAG violations introduced, the ones fixed, and the count of pre-existing ones. Use it for 'did my change break accessibility', 'what a11y issues did this PR add', or as a CI gate. For a full scan of one page use `accessibility-scan`; for a whole site use `accessibility-audit`.
日本語の概要は準備中です。原文の説明を表示しています。
Remediation only — repair web accessibility (a11y) violations against WCAG 2.2 with a baseline, edit, and verify loop. Takes a target (URL, files, directory) or a findings worklist from `accessibility-scan`/`accessibility-inspect`/`accessibility-audit`, applies mechanical fixes as given, leaves TODOs for visual or contextual judgment, and verifies by re-running the baseline check. It only fixes. To find issues use `accessibility-scan` (one page, automated), `accessibility-inspect` (one page, manual), or `accessibility-audit` (whole site, WCAG-EM); to check for regressions use `accessibility-diff`. Use it for 'fix the a11y issues in X', 'make this accessible', 'add missing alt text and labels', 'apply these accessibility fixes', 'remediate these violations'.
日本語の概要は準備中です。原文の説明を表示しています。
One page, hands-on manual tier — drive a live page through the web accessibility (a11y) checks a rule engine can't decide: keyboard operation and focus order, screen-reader names, roles and states from the accessibility tree, reflow and zoom, reduced motion, form errors, and target size. Grades each finding by evidence basis (verified / confirm-with-a-human / human-required) and severity, and closes every criterion in a ledger: verified, flagged, not exercised, or N/A. Locates and assesses; does not fix (use `accessibility-fix`). Use it for keyboard testing, focus-order checks, screen-reader or a11y-tree review, reflow and zoom at 200%, or 'is this operable, not just lint-clean'. The automated tier is `accessibility-scan`; `accessibility-audit` runs both across a sampled site.
日本語の概要は準備中です。原文の説明を表示しています。
One page, automated tier — run the web accessibility (a11y) rule engine against a live page and locate every violation it can detect mechanically. Pass a URL, a config target name (e.g. `accesslint:accessibility-scan dev`), or nothing to use the default target from `accesslint.config.json`. Ensures a debuggable Chrome, runs the @accesslint/core engine over CDP, and returns a worklist of live-DOM WCAG 2.2 violations, each grounded to its DOM selector and source `file:line`. Locates; doesn't edit. Use it for 'is this page accessible', 'check a11y on this URL', 'find contrast and alt-text issues', or to verify a UI change. For hands-on keyboard and screen-reader checks use `accessibility-inspect`; for a whole site or product use `accessibility-audit`; to diff against uncommitted changes or a branch use `accessibility-diff`.
日本語の概要は準備中です。原文の説明を表示しています。