Back to Details

runway-dev-recipes

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Runway Dev — Recipes

Runway Dev — Recipes

Companion: Use 
+runway-dev
for shared guidance when available. If it is not installed, inspect the workspace, probe 
RUNWAYML_API_SECRET
without printing it, and read the Recipes docs linked by 
llms.txt
. Encourage connecting Dev MCP for live project context and verification. If the user declines or cannot connect, continue integration from current docs.
配套工具： 若可用，请使用
+runway-dev
获取共享指导。如果未安装该工具，请检查工作区，探查
RUNWAYML_API_SECRET
但不要打印它，并阅读
llms.txt
中链接的Recipes文档。建议连接Dev MCP以获取实时项目上下文并进行验证。如果用户拒绝或无法连接，则根据现有文档继续集成工作。

Goal

目标

Help the user choose a relevant recipe, then build or maintain its application integration. Verify changes with one working SDK call when safe.
帮助用户选择合适的recipe，然后构建或维护其应用集成。在安全的情况下，通过一次有效的SDK调用验证更改。

MCP tools

MCP工具

  • get_credit_balance
    — check budget before billable verification.
  • get_task
    — inspect or debug an existing task, not replace SDK wait helpers in application code.
  • get_credit_balance
    — 在进行需付费的验证前检查预算。
  • get_task
    — 检查或调试现有任务，不要替换应用代码中的SDK等待助手。

Workflow

工作流程

  1. Understand the user's desired result. If no recipe is pinned or already integrated, follow 
    llms.txt
    to compare available recipes and recommend the closest fit.
  2. Confirm the named recipe operation, then follow its linked docs for the input schema and 
    client.recipes.{method}
    mapping.
  3. Pin a documented dated 
    version
    for stable behavior. Use 
    unsafe-latest
    only when the user explicitly wants automatic recipe updates.
  4. Check 
    RUNWAYML_API_SECRET
    when implementing the SDK call.
  5. Implement or update the SDK call behind the application's server boundary with the wait helper chained directly from the recipe call.
  6. If the application has a UI, wire its inputs and output, including loading and error states.
  7. When verification is appropriate, submit once and present the result.
  1. 了解用户期望的结果。如果没有固定的recipe或尚未集成，请遵循
    llms.txt
    中的内容比较可用的recipe，推荐最贴合的选项。
  2. 确认指定的recipe操作，然后遵循其链接文档中的输入模式和
    client.recipes.{method}
    映射。
  3. 固定一个带日期的已记录
    version
    以确保行为稳定。仅当用户明确需要自动更新recipe时才使用
    unsafe-latest
    。
  4. 实现SDK调用时检查
    RUNWAYML_API_SECRET
    。
  5. 在应用的服务器边界后实现或更新SDK调用，并将等待助手直接链接到recipe调用。
  6. 如果应用有UI，接入其输入和输出，包括加载状态和错误状态。
  7. 当适合进行验证时，提交一次并展示结果。

Docs

文档