152 件 ・ 関連度順
概要と使いどころ
Expert in creating rich backstories, fictional universes, and ARGs (Alternate Reality Games). Covers world-building, mystery construction, community-driven storytelling, and transmedia narratives. Knows how to create depth that rewards exploration without overwhelming. Use when "lore, world building, backstory, ARG, mythology, fictional universe, hidden story, deep canon, " mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
Calibrated grilling session for stress-testing a plan, design, idea, or decision. First assesses the user's topic knowledge, confidence, and desired pressure level, then asks one question at a time with recommended answers. Use when user says "grill me", "stress-test this", "challenge my plan", "interview me", or wants a plan probed without being overwhelmed.
日本語の概要は準備中です。原文の説明を表示しています。
Design first-run experiences that get users to value quickly without overwhelming them.
日本語の概要は準備中です。原文の説明を表示しています。
Deploy, manage, and debug Kubernetes in production — Deployments, Services, Gateway API, Service Mesh (Istio/Linkerd/Cilium), eBPF observability (Cilium Hubble), security hardening (Pod Security Standards, OPA/Kyverno, seccomp, runtime security with Falco/Tetragon), Helm, HPA, PDB, topology spread, and debugging. Use when user asks to write K8s manifests, deploy to a cluster, debug pods, set up Gateway API, configure autoscaling, or harden cluster security. Do NOT use for Dockerfiles (use docker), CI/CD pipeline design (use ci-cd), or Terraform infrastructure (use terraform).
日本語の概要は準備中です。原文の説明を表示しています。
Use when the diff changes a GitHub Actions workflow, a reusable action, a Dockerfile or compose file, Terraform/HCL, Kubernetes manifests or Helm values, or a cloud OIDC trust policy - judged only where concretely exploitable
日本語の概要は準備中です。原文の説明を表示しています。
Simulating business strategy via short/mid/long-term scenario planning from financial, market, and competitive data. Applies SWOT/PESTLE/Porter, KPI forecasting, roadmaps. Does not write code.
日本語の概要は準備中です。原文の説明を表示しています。
Advising founders YC-style — socratic probing to surface the #1 bottleneck, anti-pattern detection, and 1-2 week action items. Not for brainstorming (Riff) or long-term scenarios (Helm).
日本語の概要は準備中です。原文の説明を表示しています。
Analyse a learning task for cognitive load problems and recommend specific design improvements. Use when tasks overwhelm students, instructions feel complex, or materials need simplifying.
日本語の概要は準備中です。原文の説明を表示しています。
Head of product — orchestrate the product team, write briefs, plan initiatives, hand off to Apex. Use when asked to "write a product brief", "plan the roadmap", "decide what to build", or hand off requirements to engineering.
日本語の概要は準備中です。原文の説明を表示しています。
Scope arbitration — resolve disagreements between product and engineering on what is in or out of scope, with a decision log and escalation path. Use when asked to "resolve this scope disagreement", "arbitrate between product and eng", "scope is creeping", "we can't agree on what's in scope", or "help us decide what to cut".
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked to write a product brief, turn a feature idea into a spec, define requirements for something to build, or clarify what a product should do and why. Examples: "write a brief for X", "turn this idea into a spec", "what should we build here", "help me define requirements".
日本語の概要は準備中です。原文の説明を表示しています。
Use when a product brief is finalized and ready to hand off to the engineering team, or when asked to send a brief to Apex, kick off engineering work, or start development on a product spec. Examples: "hand this off to engineering", "send brief to Apex", "start building this", "kick off dev on this spec".
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked to build a product roadmap, prioritize a backlog, decide what to build next, or sequence a list of feature ideas. Examples: "what should we build next", "prioritize this backlog", "make a roadmap", "RICE score these features".
日本語の概要は準備中です。原文の説明を表示しています。
Product landscape reconnaissance — survey existing briefs, research, strategy, and team output before writing new briefs or dispatching specialists. Use when asked to "understand the product state", "what briefs exist", "what has the team produced", "orient me on this product", or before starting a new product initiative.
日本語の概要は準備中です。原文の説明を表示しています。
Manage Alibaba Cloud Container Registry (ACR) Enterprise Edition using the @alicloud/cr20181201 TypeScript SDK. Use when working with container image registries on Alibaba Cloud, including instance management, namespaces, image repositories, image tags, build rules, image synchronization, security scanning, delivery chains, Helm charts, artifact lifecycle, and event notifications. Covers all 115 APIs of the CR 20181201 version.
日本語の概要は準備中です。原文の説明を表示しています。
Kubernetes 工作负载编排，覆盖 Deployment / Service / Ingress / HPA / PDB。Helm Chart 管理、ArgoCD GitOps 部署、资源调优、高可用设计。
日本語の概要は準備中です。原文の説明を表示しています。
容器编排与部署时使用。覆盖 Docker/Docker Compose/K8s/Helm 实操。
日本語の概要は準備中です。原文の説明を表示しています。
Diagnoses ArgoCD application sync failures using the ArgoCD REST API and Kubernetes resource diff analysis. Identifies Helm value conflicts, Kustomize overlay errors, and resource health check failures.
日本語の概要は準備中です。原文の説明を表示しています。
Manages ArgoCD Application sync waves and hooks through the ArgoCD REST API and Kubernetes custom resources. Uses kubectl diff and Helm template rendering to validate manifests before triggering progressive rollouts via Argo Rollouts.
日本語の概要は準備中です。原文の説明を表示しています。
Container orchestration expert including Docker, Kubernetes, Helm, and service mesh
日本語の概要は準備中です。原文の説明を表示しています。
Guide a person through structured learning of a new topic, technology, or skill. AI acts as learning coach — assessing current knowledge, designing a learning path, walking through material, testing understanding, adapting difficulty, and planning review sessions for retention. Use when a person wants to learn a new technology and does not know where to start, when someone feels overwhelmed by documentation, when a person keeps forgetting material and needs spaced repetition, or when transitioning between domains and needing a gap analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Deploy applications to Kubernetes clusters using kubectl manifests for Deployments, Services, ConfigMaps, Secrets, and Ingress resources. Implement health checks, resource limits, rolling updates, and Helm chart packaging for production deployments. Use when deploying new applications to EKS, GKE, AKS, or self-hosted clusters, migrating from Docker Compose to container orchestration, implementing zero-downtime rolling updates, or setting up multi-environment deployments across dev, staging, and production.
日本語の概要は準備中です。原文の説明を表示しています。
Implement AI-powered anomaly detection for operational metrics using time series analysis (Isolation Forest, Prophet, LSTM), alert correlation, and root cause analysis. Reduce alert fatigue by intelligently identifying true anomalies in system metrics, logs, and traces. Use when operations teams are overwhelmed by alert volume, when detecting complex multi-metric anomalies beyond static thresholds, when seasonal patterns make thresholds ineffective, or when needing to predict issues proactively before they impact users.
日本語の概要は準備中です。原文の説明を表示しています。
"Apply Cognitive Load Theory to optimize instructional design by managing intrinsic, extraneous, and germane load within working memory limits. Use this skill when the user needs to diagnose why learners are overwhelmed, redesign training or documentation for better comprehension, evaluate UI/UX information architecture for cognitive burden, or when they ask 'why is this tutorial confusing', 'how to simplify complex instructions', or 'what causes information overload'.".
日本語の概要は準備中です。原文の説明を表示しています。