「config」の検索結果

Fix Cloud Run GPU deployment failures caused by quota errors. Use when: (1) `gcloud run deploy` fails with "You do not have quota for using GPUs with zonal redundancy" AND "You do not have quota for using GPUs without zonal redundancy", (2) The service already exists and is running with a GPU, (3) You only need to update the container image, not change GPU config. Uses `gcloud run services update --image` instead of `gcloud run deploy` to bypass quota re-validation on existing GPU services.

日本語の概要は準備中です。原文の説明を表示しています。

Fix .well-known files (apple-app-site-association, assetlinks.json) being served as HTML by the @fastly/compute-js-static-publish SPA fallback instead of JSON. Use when: (1) iOS Universal Links or Android App Links are broken because the verification files return text/html instead of application/json, (2) PublisherServer with spaFile config intercepts /.well-known/ paths and returns index.html (200, text/html) instead of 404 for missing files, (3) apple-app-site-association (no file extension) gets wrong content type even when correctly stored in KV. Covers both apex domain and subdomain handler patterns.

日本語の概要は準備中です。原文の説明を表示しています。

Fix Flutter macOS app crash at launch due to FFmpeg Kit library loading failure. Use when: (1) macOS app builds successfully but crashes immediately on launch, (2) Crash log shows "Library not loaded: libfontconfig.1.dylib" or similar homebrew library, (3) Error mentions "code signature not valid for use in process" with "different Team IDs", (4) Using ffmpeg_kit_flutter_new (Full GPL variant). The Full GPL variant has external dependencies on homebrew libraries that fail macOS code signing. Switch to ffmpeg_kit_flutter_new_min.

日本語の概要は準備中です。原文の説明を表示しています。

Fix silent failures in Fastly Compute@Edge when using send_async for fire-and-forget requests. Use when: (1) Background tasks (migrations, webhooks, notifications) triggered from Compute never complete, (2) send_async PendingRequest is immediately dropped, (3) Fire-and-forget pattern works locally but fails in production, (4) An async trigger "logs as triggered" but the target service never receives the request (especially after renaming backend constants — the URL hostname is cosmetic, the backend name determines routing, so a global rename can silently reroute calls to the wrong service). Also covers silent backend-not-found errors when FALLBACK_BACKENDS or other backend constants reference names not configured in the Fastly dashboard.

日本語の概要は準備中です。原文の説明を表示しています。

Use when implementing user account configuration and preferences.

日本語の概要は準備中です。原文の説明を表示しています。

Create the required PR-ready summary block, branch suggestion, title, and draft description for openai-guardrails-python after runtime, tests, examples, build/test configuration, or behavior-impacting docs change.

日本語の概要は準備中です。原文の説明を表示しています。

macOS / Windows / Linux 只读存储分析助手（自动识别系统）。扫描整机磁盘占用，找出 占空间大户，把每一项分成 🟢可自动清理 / 🟡需人工判断 / 🔴谨慎清理 三级并给出 可执行处置方案，生成排版精美、可折叠、命令可一键复制的交互式 HTML 报告，并可 起本地服务在网页上一键删除（移废纸篓/直接删）。扫描全程只读。务必在以下场景 使用：用户想知道磁盘或存储空间被什么占用、磁盘（含 C 盘）空间不足、想清理磁盘 或缓存、想要清理建议（中英文说法均适用，如"磁盘满了""清理空间" "storage analysis""disk cleanup"），或遇到 "No space left on device"、inode 耗尽等报错。 中文口语里"内存满了/不够/不足""看下内存"常指存储空间，也属于本 skill；用户明确指 运行内存/RAM（如"哪个进程吃内存""内存占用高"想看活动监视器）时不属于本 skill。

日本語の概要は準備中です。原文の説明を表示しています。

Adversarial code review using the opposite model's CLI. Spawns 1–3 reviewers on the opposing model (Codex sessions typically spawn Claude; Claude sessions spawn Codex) to challenge work from distinct critical lenses. Triggers: "adversarial review".

日本語の概要は準備中です。原文の説明を表示しています。

Adversarial code review using the opposite model. Spawns 1–3 reviewers on the opposing model (Claude spawns Codex, Codex spawns Claude) to challenge work from distinct critical lenses. Triggers: "adversarial review".

日本語の概要は準備中です。原文の説明を表示しています。

Design, configure, test, bake, and validate Blender physical effects including Cloth, Soft Body, Rigid Body, collisions, constraints, Fluid, smoke, fire, Dynamic Paint, Ocean, Wave, particles, Boids, force fields, fracture, debris, and secondary effects. Use when gravity, inertia, collision, flexibility, pressure, flow, flocking, emission, or breaking causes the requested result.

日本語の概要は準備中です。原文の説明を表示しています。

Instruments code to track the flow of untrusted or sensitive data at runtime, enabling detection of injection vulnerabilities, data leaks, and privilege violations. Use when users need to: (1) Track untrusted input propagation through code, (2) Detect SQL injection, XSS, or command injection vulnerabilities, (3) Identify sensitive data leaks, (4) Monitor privilege escalation paths, (5) Perform dynamic taint analysis for security testing. Supports Python, Java, JavaScript, and C/C++ with configurable taint sources and sinks.

日本語の概要は準備中です。原文の説明を表示しています。

Suggests rollback strategies for failed deployments across different platforms and failure types. Use when deployments fail and need to be reverted, including application code rollbacks, database migration reversions, infrastructure changes, and configuration updates. Supports Docker/Docker Compose environments with step-by-step procedural guidance for safe and effective rollback execution.

日本語の概要は準備中です。原文の説明を表示しています。

Generate setup scripts and instructions for development environments across platforms. Use when: (1) Setting up new development machines (Python, Node.js, Docker, databases), (2) Creating automated setup scripts for team onboarding, (3) Need cross-platform setup instructions (macOS, Linux, Windows), (4) Installing development tools and dependencies, (5) Configuring version managers and package managers. Provides executable setup scripts, platform-specific guides, and tool installation instructions.

日本語の概要は準備中です。原文の説明を表示しています。

Automatically migrate Python web applications between frameworks (Flask → FastAPI, Django → FastAPI). Use when you need to migrate an existing web application to a modern framework while preserving functionality. The skill analyzes the codebase, updates routes, handlers, configuration, dependency injection patterns, and tests. Creates git commits for each migration phase and generates a comprehensive summary of all changes. Supports automatic dependency updates, code transformations, and test adaptations.

日本語の概要は準備中です。原文の説明を表示しています。

Automatically instruments source code to collect runtime information such as function calls, branch decisions, variable values, and execution traces while preserving original program semantics. Use when users need to: (1) Add logging or tracing to code for debugging, (2) Collect runtime execution data for analysis, (3) Monitor function calls and control flow, (4) Track variable values during execution, (5) Generate execution traces for testing or profiling. Supports Python, Java, JavaScript, and C/C++ with configurable instrumentation levels.

日本語の概要は準備中です。原文の説明を表示しています。

Generate GitHub Actions deployment workflows for automated deployment to staging and production environments on cloud platforms (AWS, GCP, Azure). Use when setting up continuous deployment pipelines, creating deployment automation, or configuring multi-environment deployment strategies. Includes templates for environment-specific deployments with approval gates, secrets management, and rollback capabilities.

日本語の概要は準備中です。原文の説明を表示しています。

Analyze CVE reachability in software repositories by examining how vulnerable dependencies are imported and used. Determines whether vulnerable components, classes, or functions are reachable from project code through call chain analysis, reflection detection, dynamic loading patterns, and configuration-gated behavior. Classifies each CVE as likely reachable, possibly reachable, or likely unreachable with supporting evidence. Use when analyzing security vulnerabilities in dependencies, performing post-disclosure CVE triage, assessing vulnerability impact, or when users ask to analyze CVE reachability, check if vulnerabilities are exploitable, or evaluate dependency security risks.

日本語の概要は準備中です。原文の説明を表示しています。

Generate GitHub Actions CI/CD pipeline configurations for automated building and testing of library and package projects. Use when creating or updating CI workflows for npm packages, Python packages, Go modules, Rust crates, or other library projects that need automated build and test pipelines. Includes templates for common package ecosystems with best practices for dependency caching, matrix testing, and artifact publishing.

日本語の概要は準備中です。原文の説明を表示しています。

Streams change data capture from PostgreSQL into Redpanda or Kafka using Redpanda Connect's postgres_cdc input, which reads the WAL through logical replication (pgoutput). Use when configuring postgres_cdc (formerly pg_stream), setting up wal_level=logical, replication slots, and publications, enabling an initial snapshot before streaming, or troubleshooting slot growth and WAL accumulation. Also covers Redpanda Enterprise destination features such as Iceberg Topics, Tiered Storage, and server-side Schema ID Validation, since postgres_cdc itself requires a Redpanda Enterprise license.

日本語の概要は準備中です。原文の説明を表示しています。

Use when designing, querying, or troubleshooting the Financial Services Cloud data model — including managed-package (FinServ__ namespace) and Core FSC (standard objects, no namespace) object structures, household relationship modeling, financial account ownership, and the FSC rollup framework. Trigger keywords: FSC data model, FinancialAccount, FinancialHolding, FinancialAccountRole, FinancialAccountParty, FinServ namespace, household rollup, AssetsAndLiabilities, FinancialGoal, LifeEvent, AccountContactRelation FSC. NOT for setting up financial accounts and roles in Setup — use admin/financial-account-setup. NOT for household membership and rollup scheduling — use admin/household-model-configuration.

日本語の概要は準備中です。原文の説明を表示しています。

Create cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill, audit this skill, is this skill safe, vet a skill before installing, what does this skill access. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, spec validation, and security auditing of third-party skills before install.

日本語の概要は準備中です。原文の説明を表示しています。

BMW's corporate site — distinct from BMW M's motorsport-bombastic variant, this is a measured and settled corporate-automotive interface. On a light (cream-tinted white) canvas, BMW corporate blue (#1c69d4) carries every primary CTA; dark navy hero bands frame model photography. BMW Type Next Latin sets the entire hierarchy on two weights — heavy 700 display and Light 300 body. Configuration and reservation flows ride a card-based 4-up grid, where each card holds a model render, a name, and a "Learn More" link.

日本語の概要は準備中です。原文の説明を表示しています。

Social Media Publisher. Takes approved content from outputs/ and schedules it across platforms via Blotato MCP. Generates infographic-style visuals (stat cards, framework diagrams, process graphics, quote graphics) for posts flagged by platform-specialist skills. Requires Blotato MCP to be configured. Run after /linkedin-writer, /threads-writer, /x-writer, or /caption-writer.

日本語の概要は準備中です。原文の説明を表示しています。

Takes an app from hardcoded strings to a localized, continuously translated one with i18next (Locize optional): stack detection, config, wrapping strings in t(), key extraction, Locize sync, and AI translation. Use when the user asks to add or set up i18n, internationalization, localization, translations, or multi-language support, including phrasings like "add i18n", "internationalize my app", "make my app multilingual", "make my app translatable", "localize my app", "find hardcoded strings", "wrap my strings", and library-specific ones like "set up i18next", "add react-i18next", "use next-i18next". Also use when the user names languages they want to support ("I want German and French", "support more languages"), when an app already has i18next but strings are still hardcoded, or when translations need to move to a managed backend. Do not use for translating or reviewing strings in a project whose i18n is already set up.

日本語の概要は準備中です。原文の説明を表示しています。