“provider”的搜索结果

Terraform provider acceptance test patterns using terraform-plugin-testing with the Plugin Framework. Covers test structure, TestCase/TestStep fields, ConfigStateChecks with custom statecheck.StateCheck implementations, plan checks, CompareValue for cross-step assertions, config helpers, import testing with ImportStateKind, sweepers, and scenario patterns (basic, update, disappears, validation, regression), and ephemeral resource testing with the echoprovider package. Use when writing, reviewing, or debugging provider acceptance tests, including questions about statecheck, plancheck, TestCheckFunc, CheckDestroy, ExpectError, import state verification, ephemeral resources, or how to structure test files.

中文简介正在准备中。当前显示原文说明。

Migrate Terraform provider resources and data sources from Plugin SDKv2 to the Plugin Framework: muxing both plugins in one provider (terraform-plugin-mux, tf5to6server), per-resource migration workflow, SDKv2-to-Framework schema mapping (ForceNew, ValidateFunc, DiffSuppressFunc, Default, Timeouts, blocks), null-vs-zero-value behavioral traps, and state-compatibility verification. Use when converting or translating SDKv2 resources to the Framework, setting up a muxed provider server, deciding whether a resource should be migrated at all, or debugging plan diffs and state errors that appeared after a migration.

中文简介正在准备中。当前显示原文说明。

Implement Terraform provider ephemeral resources with the Plugin Framework: the Open/Renew/Close lifecycle, ephemeral schema design, registration via EphemeralResources, renewal for expiring credentials, and how ephemeral values flow into write-only attributes and provider configuration. Use when adding an ephemeral resource, exposing secrets/tokens/certificates that must never persist in state or plan, deciding between an ephemeral resource and a data source, or wiring short-lived credentials from one provider into another.

中文简介正在准备中。当前显示原文说明。

Fix Riverpod "Cannot use Ref or modify other providers inside life-cycles/selectors" crash in @riverpod provider bodies. Use when: (1) Crash during provider disposal with this exact error message, (2) Using keepAlive() with timer-based disposal, (3) Async callbacks (.then, .catchError) try to use ref.read() or ref.invalidateSelf(), (4) Error occurs after ref.onCancel/onResume/onDispose callbacks fire. Solution: wrap ref operations in try-catch or avoid using ref in async callbacks entirely.

中文简介正在准备中。当前显示原文说明。

Fix Flutter TabController crash when dynamically showing/hiding tabs. Use when: (1) TabController rebuild causes "SingleTickerProviderStateMixin but multiple tickers were created", (2) Tabs need to appear/disappear based on feature flags or async state, (3) TabController.length changes at runtime based on provider state. The fix is to use TickerProviderStateMixin instead of SingleTickerProviderStateMixin.

中文简介正在准备中。当前显示原文说明。

arkcli helper：为 Claude Code / Codex / OpenCode / OpenClaw / Hermes / ZCode 配置火山方舟 Plan 或 Platform Endpoint 的 model/provider，或给支持的 Agent（含 MCP-only Trae）配置 Harness 工具。真人 TTY 运行 `arkcli helper` 可选择模型和 Harness 能力；`helper mcp` 默认保持整组 Agent Plan MCP 行为，传 `--capability datapro|web-search|agent-memory` 只配单项，传 `--capability cua` 只给目标 Agent 安装云电脑 Skill；连 model/provider 一起配置用 `helper configure`，查状态用 `helper list`，移除用 `helper reset`。Agent Plan / Team 还支持专业数据集、豆包搜索、Agent 记忆、AI Native 应用开发底座、Agent 进化与 routing.v1 强制检索路由；上下文出现 ARKCLI ROUTING ENFORCEMENT / routing.v1，或用户要求在豆包搜索、DataPro、OpenViking、Supabase 之间强制分流时也使用本 Skill：调用这四类受管 Provider 前先提交 Route Plan，再调用唯一授权 Provider；原生 WebSearch/WebFetch/WebExtract 位于路由管理范围之外。Platform 只允许本人创建、Running、已验证为文本输出的 Endpoint，不配置 MCP、Supabase 或强制路由。豆包搜索配置成功后默认关闭目标客户端原生 WebSearch；传 `--keep-native-websearch` 可保留，并可用 `helper reset` 完整恢复 ArkCLI 配置。

中文简介正在准备中。当前显示原文说明。

Provider-neutral entry point for discovering, planning and synchronizing MCP configuration between user-selected providers and app classes. The user selects truth, targets and scope; no provider is an implicit hub.

中文简介正在准备中。当前显示原文说明。

依存パッケージ（Go modules / npm / Terraform provider / GitHub Actions / pre-commit 等）の アップグレードを、outdated 検出 → CHANGELOG・破壊的変更の確認 → 更新 → lint/test 検証 → コミットまで一連の手順で安全に適用する。「依存更新」「パッケージを上げて」「dependency update」 「go get -u」「npm update」「provider を上げる」等に言及されたときに使用する。

中文简介正在准备中。当前显示原文说明。

Brokered short-lived provider credentials client in matrx-frontend (`lib/api/broker/`). Use when browser code needs a provider realtime session, a direct provider call, an ephemeral token, or a provider API key in the browser or `NEXT_PUBLIC_*`. NOT for adding a new audience server-side (use aidream's token-broker).

中文简介正在准备中。当前显示原文说明。

Configure AIsa as a first-class model provider for OpenClaw, enabling production access to major Chinese AI models (Qwen, DeepSeek, Kimi K2.5, Doubao) through official partnerships with Alibaba Cloud, BytePlus, and Moonshot. Use this skill when the user wants to set up Chinese AI models, configure AIsa API access, compare pricing between AIsa and other providers (OpenRouter, Bailian), switch between Qwen/DeepSeek/Kimi models, or troubleshoot AIsa provider configuration in OpenClaw. Also use when the user mentions AISA_API_KEY, asks about Chinese LLM pricing, Kimi K2.5 setup, or needs help with Qwen Key Account setup.

中文简介正在准备中。当前显示原文说明。

执行并监控OpenClaw发布候选版本的CI，验证实际服务提供商连接及安装、更新流程，调查失败原因并进行定向重试，整理验证结果和发布决策所需证据。

• 验证OpenClaw发布候选版本
• 调查失败的CI任务并定向重跑
• 确认服务认证及实际推理能力

用于编写和修改OpenClaw在Docker中的端到端测试，结合模拟服务器与真实服务，核查实际发送的请求、图像理解结果及用户最终看到的聊天回复。

• 添加或修改Docker端到端测试
• 核查发往依赖服务的请求内容
• 验证真实模型服务的行为

依据按编程语言分类的资料，协助开发和维护Claude应用。涵盖官方SDK调用、工具集成、模型迁移、费用检查、提示词审查和评估流程。

• 在应用中接入Claude API
• 开发使用自定义工具的智能体
• 为现有Claude集成迁移模型

为native Paperclip Runner接入新的执行工具或提供商，从需求整理、通信协议调查到实现、打包，以及在实际环境中验证完整流程。

• 为Runner新增连接
• 调查执行工具的通信协议和能力
• 验证连接的取消与恢复

在启动前审查Homecore服务器的运行计划，检查身份验证、恢复顺序、功能测试、语音服务配置及配对机密信息的处理方式，不启动服务器。

• 审查Homecore启动计划
• 检查恢复顺序和限制值
• 启用Wasmtime或HAP前检查测试

按提供商、模型、时间范围、状态和费用筛选AI调用日志，汇总用量并导出日志。还可设置预算和令牌上限，查看响应时间及提示词缓存情况。

• 筛选调用日志以排查失败请求
• 汇总所有连接的令牌用量和费用
• 设置预算和令牌上限

通过命令行管理 OmniRoute API 密钥的注册、轮换、撤销及使用限制，查看用量和有效期，并启动外部服务的 OAuth 认证、检查连接状态。

• 注册服务密钥并查看已有密钥
• 设置宽限期轮换密钥或撤销密钥
• 查看用量并限制费用和可用模型

Check OmniRoute server health, component status, and live metrics from the command line. Filter alerts or watch a refreshing dashboard to see provider status and circuit breakers, which interrupt requests when failures occur.

中文简介正在准备中。当前显示英语简介。

• Checking server health
• Reviewing component alerts
• Watching live metrics and provider status

通过命令行检查OmniRoute的连接限制、使用配额和重试等待状态，重置停滞的连接目标，并调整故障阈值及恢复等待时间。

• 排查错误后的连接限制
• 重置停滞的连接目标
• 调整故障阈值和重试等待时间

Browse and search OmniRoute's AI model catalog from the command line. Filter by provider or capability, check model aliases, validate compatible models before adding them, and maintain manually registered model details.

中文简介正在准备中。当前显示英语简介。

• Finding AI models by provider or capability
• Checking model aliases and name variants
• Validating a model before adding it

设置AI使用的支出上限、令牌配额和单位时间内的请求次数限制。按API密钥或整体查看消耗情况，协助管理多个服务提供商的费用。

• 设置AI使用的支出上限
• 为各API密钥设置令牌配额
• 查看并更新整体请求频率限制

Build AI agents with Cline SDK using guidance on choosing APIs, adding custom tools, saving sessions, and handling live events. References also cover model providers, scheduled runs, multi-agent coordination, and production deployment.

中文简介正在准备中。当前显示英语简介。

• Build an AI agent with custom tools
• Choose an API for persistent sessions
• Configure model providers and live event handling

Prepare voiceovers, background music, sound effects, transcripts, captions, and background cutouts for HyperFrames compositions. The skill guides audio provider selection, word timing, and caption styling, with local alternatives for several audio tasks.

中文简介正在准备中。当前显示英语简介。

• Creating voiceovers for HyperFrames videos
• Preparing background music and sound effects
• Adding word-timed subtitles and karaoke captions

Refactor React components with too many true-or-false options into reusable parts. Provides guidance on component composition, shared state, and flexible interfaces, with examples of good and problematic implementations and specific guidance for React 19.

中文简介正在准备中。当前显示英语简介。

• Refactoring components with too many boolean options
• Designing reusable component libraries
• Reviewing shared state and component architecture