1,141 件 ・ 関連度順
概要と使いどころ
Design or audit Kubernetes RBAC — roles, bindings, service accounts, and least-privilege model. Use when asked to "audit Kubernetes RBAC", "apply least privilege in K8s", or "review service account permissions".
日本語の概要は準備中です。原文の説明を表示しています。
Audit existing service mesh configuration — find mTLS gaps, traffic policy issues, and observability holes. Use when asked to "audit our service mesh", "find mTLS gaps", or "review traffic policy issues".
日本語の概要は準備中です。原文の説明を表示しています。
Design a service mesh deployment — technology selection, mTLS policy, and traffic management config. Use when asked "should we use a service mesh", "Istio or Linkerd", or "design our mTLS policy".
日本語の概要は準備中です。原文の説明を表示しています。
Design service mesh observability — distributed tracing, service-level metrics, and dashboards. Use when asked to "add service mesh observability", "set up distributed tracing in the mesh", or "build service-level dashboards".
日本語の概要は準備中です。原文の説明を表示しています。
Assess and improve cloud portability — identify lock-in, prioritize abstraction, and design migration paths. Use when asked "how locked in are we", "reduce vendor lock-in", or "plan a cloud migration".
日本語の概要は準備中です。原文の説明を表示しています。
Design a multi-cloud or cloud portability strategy — provider selection, workload placement, and lock-in management. Use when asked "should we go multi-cloud", "design for cloud portability", or "where should this workload run".
日本語の概要は準備中です。原文の説明を表示しています。
Design a Kubernetes cluster architecture — node pools, RBAC, networking, and workload config. Use when asked to "design a Kubernetes cluster", "plan our node pools", or "design K8s architecture for this workload".
日本語の概要は準備中です。原文の説明を表示しています。
Audit an existing Kubernetes cluster — find misconfigurations, security gaps, and resource issues. Use when asked to "audit our Kubernetes cluster", "find K8s misconfigurations", or "check cluster security gaps".
日本語の概要は準備中です。原文の説明を表示しています。
Survey existing cloud architecture for lock-in depth and portability gaps. Use when asked to "survey our cloud lock-in", "find portability gaps", or "how cloud-agnostic are we".
日本語の概要は準備中です。原文の説明を表示しています。
Design a reservation and savings plan strategy — commitment level, term, and coverage targets. Use when asked "should we buy reserved instances", "design a savings plan strategy", or "what commitment coverage do we need".
日本語の概要は準備中です。原文の説明を表示しています。
Survey existing cloud cost controls — tagging coverage, alerting, and FinOps maturity. Use when asked to "audit our cost controls", "is our tagging complete", or "assess our FinOps maturity".
日本語の概要は準備中です。原文の説明を表示しています。
Audit embedding infrastructure — model drift, index freshness, query latency, coverage gaps. Use when asked to "audit our embeddings", "is our index stale", or "find embedding coverage gaps".
日本語の概要は準備中です。原文の説明を表示しています。
Audit existing experimentation infrastructure and past experiments for methodology issues. Use when asked to "audit our experiments", "is our experimentation sound", or "review past test methodology".
日本語の概要は準備中です。原文の説明を表示しています。
Design a CDN configuration — caching rules, TTLs, and origin shield setup. Use when asked to "configure the CDN", "set cache headers", or "set up an origin shield".
日本語の概要は準備中です。原文の説明を表示しています。
Audit existing CDN and edge configuration — find cache misses, missing headers, and performance gaps. Use when asked to "audit our CDN", "why is our cache hit rate low", or "find edge config gaps".
日本語の概要は準備中です。原文の説明を表示しています。
Design and configure model serving infrastructure — endpoint scaling, batching, GPU allocation. Use when asked to "serve this model", "design an inference endpoint", or "size GPU allocation for serving".
日本語の概要は準備中です。原文の説明を表示しています。
Design an edge routing and geo-distribution strategy — latency routing, failover, and edge logic. Use when asked to "geo-route our traffic", "reduce global latency", or "design edge failover".
日本語の概要は準備中です。原文の説明を表示しています。
Audit cloud spend — identify waste, rightsizing opportunities, and reservation gaps. Use when asked "our cloud bill is too high", "find cloud waste", or "where can we rightsize".
日本語の概要は準備中です。原文の説明を表示しています。
Design a caching strategy for an application — pattern selection, key design, TTL, and eviction policy. Use when asked to "add caching to this", "design a cache strategy", or "what should we cache".
日本語の概要は準備中です。原文の説明を表示しています。
Design a cache invalidation and eviction strategy — event-driven invalidation and thundering herd prevention. Use when asked to "design cache invalidation", "fix stale cache data", or "prevent a thundering herd".
日本語の概要は準備中です。原文の説明を表示しています。
Audit existing caching implementation — find cache misses, stampedes, and key design issues. Use when asked to "audit our caching", "why is our hit rate low", or "find cache stampedes".
日本語の概要は準備中です。原文の説明を表示しています。
Audit existing resilience — identify untested failure modes and chaos engineering gaps. Use when asked "how resilient are we", "what failure modes are untested", or "find our chaos engineering gaps".
日本語の概要は準備中です。原文の説明を表示しています。
Design a game day — simulated failure scenario, runbook, and post-event review. Use when asked to "run a game day", "plan a failure drill", or "simulate an outage".
日本語の概要は準備中です。原文の説明を表示しています。
Design a chaos engineering experiment — hypothesis, blast radius, steady state, and abort conditions. Use when asked to "design a chaos experiment", "inject a failure", or "test the resilience of this service".
日本語の概要は準備中です。原文の説明を表示しています。