244 件 ・ 関連度順
概要と使いどころ
Create a professional paid-advertising strategy covering objectives, economics, platform selection, campaign architecture, audiences, budget, creative, measurement, experiments, governance, rollout, and reporting. Use for ad plan, media plan, PPC strategy, paid-social strategy, campaign architecture, advertising roadmap, or channel planning.
日本語の概要は準備中です。原文の説明を表示しています。
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Config Cat — configCat feature flag management, remote configuration, A/B testing, targeting rules, and percentage-based rollouts. Covers flag listing, targeting rule management, environment overrides, audit log review, and SDK integration status. Use when managing feature flags, reviewing targeting rules, analyzing flag usage, or auditing configuration changes in ConfigCat.
日本語の概要は準備中です。原文の説明を表示しています。
Use when working with Gcp Cloud Deploy — google Cloud Deploy delivery pipeline management, release tracking, rollout status monitoring, approval workflows, and deployment diagnostics via gcloud CLI.
日本語の概要は準備中です。原文の説明を表示しています。
BDB Shipping Godmode, the final gatekeeper for production releases. Use when running pre-launch checks, feature-flag rollouts, or rollback planning under Spec-Driven Development before a release ships.
日本語の概要は準備中です。原文の説明を表示しています。
Plans Convex schema and data migrations with widen-migrate-narrow and @convex-dev/migrations. Use for breaking schema changes, backfills, table reshaping, or zero-downtime rollouts.
日本語の概要は準備中です。原文の説明を表示しています。
Guide for using completers — TokenCompleter and MessageCompleter for text generation during RL rollouts and evaluation. Use when the user asks about generating text, completing messages, or using completers in RL environments.
日本語の概要は準備中です。原文の説明を表示しています。
Add PostHog feature flags to gate new functionality. Use after implementing features or reviewing PRs to ensure safe rollouts with feature flag controls. Also handles initial PostHog SDK setup if not yet installed.
日本語の概要は準備中です。原文の説明を表示しています。
Add feature flags to an application for gradual rollouts, A/B testing, and kill switches using PostHog, LaunchDarkly, or a simple local implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Query aggregate Langfuse cost, volume, latency, and model telemetry efficiently with Metrics API v2. Use for dashboards, rollout checks, usage summaries, and cost or latency comparisons; use Observations API v2 instead when individual rows are actually required.
日本語の概要は準備中です。原文の説明を表示しています。
Design AI model deployment strategies with rollout. TRIGGERS - Use when user needs help with ai-deployment-strategy related tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Ensure cross-service integration defines contracts, ownership, failure handling, versioning, and rollout/rollback expectations.
日本語の概要は準備中です。原文の説明を表示しています。
Plans Convex schema and data migrations with widen-migrate-narrow and @convex-dev/migrations. Use for breaking schema changes, backfills, table reshaping, or zero-downtime rollouts.
日本語の概要は準備中です。原文の説明を表示しています。
Check the health of published EAS Updates: crash rates, install/launch counts, unique users, payload size, and the split between embedded and OTA users per channel. Use when the user asks how an update is performing, whether a rollout is healthy, how many users are on the embedded build vs OTA, or wants to gate CI on update health.
日本語の概要は準備中です。原文の説明を表示しています。
Create a detailed, step-by-step implementation plan for a feature or project. Load when the user asks to plan a feature, create a technical roadmap, break down a PRD into tasks, design an implementation strategy, or sequence engineering work. Also triggers on "how should we build this", "implementation plan for", "technical breakdown", "task list for", or any request to turn a high-level requirement into a concrete execution plan. Supports phased rollouts, architecture-first, and MVP-focused planning.
日本語の概要は準備中です。原文の説明を表示しています。
Fleet worker contract for wiring assigned files to the v3 right-click menu. Use when handed files from pnpm check:context-menu, or told to 'wire the menu on X', 'do your assigned rows', or 'clear your shard'. NOT for an unassigned one-off menu wiring (use context-menu-v3).
日本語の概要は準備中です。原文の説明を表示しています。
Compact two-icon Copy / Copy-for-AI controls (components/agent-copy). Use when adding copy buttons to a row, card, list, or record; merging duplicate Copy/JSON/AI controls; continuing the copy rollout; or writing a Copy-for-AI payload. NOT for markdown content actions (use rich-document-actions).
日本語の概要は準備中です。原文の説明を表示しています。
Plans Convex schema and data migrations with widen-migrate-narrow and @convex-dev/migrations. Use for breaking schema changes, backfills, table reshaping, or zero-downtime rollouts.
日本語の概要は準備中です。原文の説明を表示しています。
OrgX operations execution contract for OpenClaw. Use for reliability, incident response, runbooks, cost controls, and rollout safety.
日本語の概要は準備中です。原文の説明を表示しています。
Find and own a defensible market position. Use when messaging sounds like competitors, conversion is weak despite awareness, repositioning a product, or testing positioning claims. Includes Crawl-Walk-Run rollout methodology and the word change that improved enterprise deal progression.
日本語の概要は準備中です。原文の説明を表示しています。
Implement feature flags for gradual rollouts and A/B testing.
日本語の概要は準備中です。原文の説明を表示しています。
Implements security headers and Content Security Policy with safe rollout strategy (report-only → enforce), testing, and compatibility checks. Use for "security headers", "CSP", "HTTP headers", or "XSS protection".
日本語の概要は準備中です。原文の説明を表示しています。
Generates Request for Comments documents for technical proposals including problem statement, solution design, alternatives, risks, and rollout plans. Use for "RFC", "technical proposals", "design docs", or "architecture proposals".
日本語の概要は準備中です。原文の説明を表示しています。
Guides the practical path from 'we have no design system' or 'we have a mess' to a real, functional design system. Component inventory, design token extraction, headless UI adoption (Radix, React Aria, Headless UI), migration order of operations, and the assessment-to-rollout pipeline. Activate on 'design system from scratch', 'bootstrap design system', 'no design system', 'design system migration', 'headless UI adoption', 'component audit', 'design token extraction', 'design system strategy'. NOT for building specific components once a system exists (use design-system-creator), not for generating token files/configs (use design-system-generator).
日本語の概要は準備中です。原文の説明を表示しています。