Loading...
Loading...
Found 6,804 Skills
Processes GCP infrastructure design and deployment workflows within Application Design Center (ADC). Use when: - Designing GCP infrastructure with Terraform. - Validating local HCL. - Performing best-practice plan scans. - Importing templates to Application Design Center (ADC). - Deploying templates. - Troubleshooting deployment failures. Boundaries: - Only use for GCP-specific cloud infrastructure. - Only use for Terraform coding within the ADC context.
Monitors, troubleshoots, and manages GKE TPU Dynamic Slices custom resources. Use when checking TPU slice lifecycle states, troubleshooting slice provisioning failures, validating single-slice or multi-slice (JobSet) workload manifests, or safely patching stuck finalizers and disabling the slice controller. Don't use for generic GKE cluster node pool creation or standard non-TPU workload management (use gke-basics or gke-cluster-creation instead).
Monitors and troubleshoots GKE TPU workloads, nodes, and node pools using GKE system metrics and PromQL. Use when monitoring TensorCore duty cycle, TPU memory, node readiness, multi-host TPU node pool availability, host maintenance or preemption interruptions, and calculating MTTR or MTBI metrics for GKE TPUs. Don't use for general non-TPU GKE workload monitoring or non-metric TPU debugging.
Render independent questions in an Agent workflow into a local interactive form, mark recommended answers, collect optional supplementary notes for each question, save responses as portable JSON, and return the submitted results directly to the waiting Agent command. Suitable for grill-me, grill-with-docs, brainstorming, requirement clarification, configuration, planning, and any workflow requiring user confirmation or question collection; explicitly call Ask UI when a round contains more than two questions. When a user says "submitted", "done submitting", or "finished answering" during an Ask UI round, follow this skill's manual recovery path.
Use taste as a competitive moat and business advantage. In the AI and vibe-coding era, execution is commoditized. Taste is the defensible edge. Use when advising founders on product differentiation, building product culture, evaluating why some products win despite fewer features, or understanding taste as a strategic asset.
Notice what's deliberately missing from a design. Restraint is a taste signal. Use when studying minimalist products, evaluating design maturity, or understanding the power of removal.
Build a reference system that returns the right reference in under 60 seconds. Use when setting up a design reference library, reorganizing existing collections, or helping teams build shared reference systems.
Write a structured design review that someone can act on without follow-up questions. Use when giving async design feedback, writing portfolio case studies, or documenting design decisions.
Reverse-engineer why a design decision was made. Move from observation to inference. Use when studying products you admire, learning from competitors, or building analytical design thinking.
Design or verify automated build, test, quality-gate, release, deployment, and post-deployment checks, including failure evidence and stop or rollback conditions. Do not use it for branch, commit, or tag history, or infer product correctness from a green pipeline alone.
Review a diff or proposed implementation for behavior correctness, boundary violations, regressions, error handling, maintainability, scope, and verification evidence before merge or handoff. Do not use it as the primary Skill for live failure diagnosis or new implementation planning.
Decide whether a technical dependency boundary is meaningful and design Ports, Adapters, dependency inversion, explicit injection, and test seams. Use for DI, interfaces, package direction, infrastructure isolation, and protocol translation; not for primarily business invariants or active failure diagnosis.