菜单
当用户正在构建、修改或 vibe-coding 一个应用、网站、原型或前端页面，并希望每次改动完成后都立刻部署到公开的生产或预览 URL，方便用手机或远程设备查看时使用。触发词包括“上线模式”“改完就上线”“自动部署”“每次改完都部署”“给我一个公开链接”“发我部署链接”“手机能打开的链接”“远程预览”，也包括 "Go Live"、"go live"、"auto deploy" 等类似请求。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Plan and run Codex-native dynamic workflows for complex tasks that benefit from explicit orchestration, goal mode, subagents or simulated work packets, approval gates, integration, verification, and reusable workflow artifacts. Use when the user invokes this skill, asks for dynamic workflows, subagents, parallel agents, swarm-like work, Goal Maker orchestration, large audits, migrations, multi-track research plus implementation, or Claude Code-style fan-out/fan-in workflows.
Direct browser control via CDP. Use when the user wants to automate, scrape, test, or interact with web pages. Connects to the user's already-running Chrome.
This skill should be used for browser automation tasks using Chrome DevTools Protocol (CDP). Triggers when users need to launch Chrome with remote debugging, navigate pages, execute JavaScript in browser context, capture screenshots, or interactively select DOM elements. No MCP server required.
Use Orca's computer-use CLI to inspect and control local desktop apps through accessibility trees, screenshots, and safe UI actions. Use when an agent needs to list desktop apps, get an app state, read visible UI, click, type, press keys, scroll, drag, set values, or perform app accessibility actions. Triggers include "computer use", "orca computer", "list apps", "get app state", "read Spotify", "read Slack", "click app", "type text", "press key", "set value", "scroll app", "drag app", and desktop app interaction tasks.
Use the `orca` CLI to drive a running Orca editor — manage Orca worktrees; create and manage scheduled automations; create, read, and run shell commands in Orca-managed terminals; and automate Orca's built-in browser (snapshot/click/fill/screenshot/tabs). Use this instead of raw `git worktree`, ad hoc shell PTYs, or Playwright whenever the task touches Orca state. Coding agents inside an Orca worktree should also use it to keep the worktree comment fresh at meaningful checkpoints. Boundary with `orchestration`: if the recipient of a terminal write is another AI agent (Claude Code, Gemini, Codex, a worker), use `orchestration` — it is the only correct way to send messages, nudges, replies, or task hand-offs to agents. orca-cli writes are for non-agent terminals (shells, build/test commands); reading or `wait`ing on any terminal — including agent terminals — stays in orca-cli.
Use Orca orchestration for structured multi-agent coordination: threaded messages, blocking ask/reply flows, task dispatch, worker_done/escalation waits, task DAGs, decision gates, coordinator loops, or decomposing work across agents. Use `orca-cli` instead for ordinary terminal control, lightweight terminal prompts, shell commands, Orca worktree management, reading or waiting on terminals, and automation of the browser embedded inside Orca. Use Computer Use for browser windows, webviews, Orca app UI, or desktop UI outside Orca's embedded browser.
| name | go-live |
| description | 当用户正在构建、修改或 vibe-coding 一个应用、网站、原型或前端页面，并希望每次改动完成后都立刻部署到公开的生产或预览 URL，方便用手机或远程设备查看时使用。触发词包括“上线模式”“改完就上线”“自动部署”“每次改完都部署”“给我一个公开链接”“发我部署链接”“手机能打开的链接”“远程预览”，也包括 "Go Live"、"go live"、"auto deploy" 等类似请求。 |
把部署视为实现工作的一部分，而不是事后补做的步骤。每次修改应用或网站后，都要交付一个用户能立即打开的公开 URL。
这个 skill 面向手机优先的 vibe coding 场景：用户不一定方便查看 localhost，所以真正可用的预览应该是已部署的公开链接。
优先使用项目已有的生产或预览发布流程：
除非部署确实被阻塞，最终回复必须包含一个公开 URL。
条件允许时，回复中包括：
如果部署失败，不要只说“失败了”。用清楚的话说明阻塞点，并给出下一步可执行的恢复方式，例如缺少登录授权、项目未绑定、构建失败或部署平台故障。
小需求在改完后部署一次。
较大的需求在每个成型的、用户可见的阶段后部署，至少要在最终回复前部署一次。除非用户明确要求只做本地工作，否则不要只留下 localhost 链接。
