收束 · 30 天升级路线与全书验收Closing · The 30-Day Path and the Book's Acceptance.
把整本书压成一条 30 天路线:第一周首胜与底座习惯,第二周交办与沉淀,第三周接外部与权限,第四周云端与边界。三条 starter workflows 直接可抄,最后是一张全书验收单 —— 逐项勾完,你就是那个交办自如的人。The whole book compressed into a 30-day path: week one, the first win and base habits; week two, dispatching and distilling; week three, connecting and permissions; week four, cloud and boundaries. Three starter workflows to copy outright, and at the end, an acceptance sheet for the whole book — check every line, and you've become someone who delegates with ease.
把整本书压成一句:你装的不是一个终端,是一台终端形状的元工具。它把命令行、agent、Drive、MCP、Cloud Agents / Oz 放在同一个工作台上;真正的变化不是多了一个输入框,而是你开始把命令行工作流当成可以派发、审查、沉淀、复用、放到后台的东西。这一章把十二章压成一条 30 天路线,最后给你一张全书验收单。<Footnote n={1} />The whole book in one line: what you installed is not a terminal, it is a meta-tool shaped like one. It puts command line, agent, Drive, MCP, and Cloud Agents / Oz on the same workbench; the real shift is not another input box, but treating command-line workflows as work that can be dispatched, reviewed, distilled, reused, and sent to the background. This chapter compresses twelve chapters into a 30-day path, ending with an acceptance sheet for the whole book.<Footnote n={1} />
— I
30 天,跟着章序走30 Days, Following the Chapter Order.
别从「我要把 Warp 用满」开始,那会把工具变成负担。30 天路线就是这本书的章序 —— 每周两章的量,每周都有可勾的验收:Don't start with 'I need to use all of Warp' — that turns the tool into homework. The 30-day path is this book's chapter order: about two chapters a week, each week with acceptance you can check off:
时间Time
章节Chapters
动作Action
验收Validation
第 1 周Week 1
02 首胜 · 03 底座02 First Win · 03 Blocks
装好、登录、设好三设置、完成第一次只读交办并存下第一个 Workflow;⌃R 找回昨天那条命令。Install, log in, set the three settings, finish the first read-only dispatch, save the first Workflow; ⌃R-recover yesterday's command.
十分钟内拿到第一个有用答案;昨天的命令不靠翻 history 翻回来。A first useful answer inside ten minutes; yesterday's command recovered without scrolling history.
把一个真实报错修到好;跑一件带 dry-run 的批量活;把重复三次的操作固化成 Workflow。Take one real error to fixed; run one batch job with dry-run; freeze a thrice-repeated chore into a Workflow.
修 bug 不用开浏览器搜;批量活有回滚;第三次重复不用再敲。Bug fixes without browser searches; batch jobs with rollback; the third repeat needs no retyping.
第 3 周Week 3
07 接外部 · 08 管住它07 Reach Out · 08 Keep It in Check
接一个只读 GitHub MCP 答一题,写类工具进 denylist;配出 local-dev profile 并当场验收。Connect a read-only GitHub MCP to answer one question, denylist its write tools; build the local-dev profile and validate it on the spot.
多给了上下文,没多给写权限;该自动的自动、该拦的拦住。Context added without write authority; what should auto-run does, what should block asks.
派两个 cloud run 验收回来,一个改定时;写下绝不上云的那件;按缺口选定档位。Dispatch two cloud runs and review them back, one becomes a schedule; write down what never goes cloud; pick the tier by the gap.
第一次上云是可检查的 run;边界清单落在纸上;档位有理由不是跟风。The first cloud run is inspectable; the boundary list is on paper; the tier has reasons, not hype.
— II
从这三条 starter workflows 开始Start with These Three Starter Workflows.
如果你不知道第一件该交给 Warp 的活是什么,就从下面三条里选 —— 它们分别对应第四、五、六章的主线,共同点是:终端侧、可审查、可复用,出错能回滚。If you don't know what to hand Warp first, pick one of these three — they mirror the main lines of chapters 4, 5, and 6, and share one trait: terminal-side, reviewable, reusable, reversible.
提示词PromptStarter workflow · local project debugging
请在这个本地项目里做一次只读排障。
目标:
- 找出 <失败现象> 的最可能原因
- 先不要改文件
- 可以运行只读命令、测试、lint、日志查看
请按这个顺序:
1. 先列你要看的文件和命令
2. 每次命令前解释风险
3. 总结证据,不要只给猜测
4. 给出最小修复方案
5. 等我确认后再进入改动阶段Run a read-only debugging pass in this local project.
Goal:
- Find the most likely cause of <failure>
- Do not edit files yet
- You may run read-only commands, tests, lint, and log inspection
Proceed in this order:
1. List files and commands you want to inspect
2. Explain risk before each command
3. Summarize evidence, not just guesses
4. Propose the smallest fix
5. Wait for my confirmation before editing
请在这个本地项目里做一次只读排障。
目标:
- 找出 npm run dev 启动后访问首页就 500、终端报「Cannot read properties of undefined」的最可能原因
- 先不要改文件
- 可以运行只读命令、测试、lint、日志查看
请按这个顺序:
1. 先列你要看的文件和命令
2. 每次命令前解释风险
3. 总结证据,不要只给猜测
4. 给出最小修复方案
5. 等我确认后再进入改动阶段Run a read-only debugging pass in this local project.
Goal:
- Find the most likely cause of the home page returning 500 right after npm run dev starts, with the terminal logging "Cannot read properties of undefined"
- Do not edit files yet
- You may run read-only commands, tests, lint, and log inspection
Proceed in this order:
1. List files and commands you want to inspect
2. Explain risk before each command
3. Summarize evidence, not just guesses
4. Propose the smallest fix
5. Wait for my confirmation before editing
提示词PromptStarter workflow · file batch dry-run
请帮我批处理这些文件,但先只做 dry-run。
范围:
- 目录:<path>
- 文件类型:<ext>
- 目标:<rename/convert/extract/clean>
安全要求:
1. 先生成 manifest,列出会碰到的文件
2. 先处理 3 个样本
3. 任何删除、覆盖、移动都必须等我确认
4. 输出完整命令和回滚办法
5. 通过样本后,再给 full-run 命令Help me batch-process these files, but do a dry-run first.
Scope:
- Directory: <path>
- File type: <ext>
- Goal: <rename/convert/extract/clean>
Safety requirements:
1. Generate a manifest of affected files first
2. Process only 3 samples first
3. Any delete, overwrite, or move requires my confirmation
4. Output full commands and rollback steps
5. After samples pass, provide the full-run command
请帮我批处理这些文件,但先只做 dry-run。
范围:
- 目录:./assets/photos
- 文件类型:.png
- 目标:convert,全部转成质量 80 的 .webp,原文件保留
安全要求:
1. 先生成 manifest,列出会碰到的文件
2. 先处理 3 个样本
3. 任何删除、覆盖、移动都必须等我确认
4. 输出完整命令和回滚办法
5. 通过样本后,再给 full-run 命令Help me batch-process these files, but do a dry-run first.
Scope:
- Directory: ./assets/photos
- File type: .png
- Goal: convert all to .webp at quality 80, keeping the originals
Safety requirements:
1. Generate a manifest of affected files first
2. Process only 3 samples first
3. Any delete, overwrite, or move requires my confirmation
4. Output full commands and rollback steps
5. After samples pass, provide the full-run command
提示词PromptStarter workflow · server health runbook
请把一次服务器健康检查整理成 Warp Drive Notebook。
目标主机 / 环境:<host/env>
检查项:
- disk
- memory
- process
- service status
- recent logs
- open ports
要求:
1. 每个检查项给命令、正常输出特征、异常解释
2. 默认只读,不要 restart / delete / deploy
3. 最后给「什么时候升级给人」的判断线
4. 把可参数化的部分标成 <env> / <service> / <log_path>Turn a server health check into a Warp Drive Notebook.
Target host / environment: <host/env>
Checks:
- disk
- memory
- process
- service status
- recent logs
- open ports
Requirements:
1. For each check, include command, healthy-output signals, and abnormal-output interpretation
2. Default read-only; do not restart / delete / deploy
3. End with escalation criteria for a human
4. Mark parameterized parts as <env> / <service> / <log_path>
请把一次服务器健康检查整理成 Warp Drive Notebook。
目标主机 / 环境:web-prod-01 / production
检查项:
- disk
- memory
- process
- service status
- recent logs
- open ports
要求:
1. 每个检查项给命令、正常输出特征、异常解释
2. 默认只读,不要 restart / delete / deploy
3. 最后给「什么时候升级给人」的判断线
4. 把可参数化的部分标成 <env> / <service> / <log_path>Turn a server health check into a Warp Drive Notebook.
Target host / environment: web-prod-01 / production
Checks:
- disk
- memory
- process
- service status
- recent logs
- open ports
Requirements:
1. For each check, include command, healthy-output signals, and abnormal-output interpretation
2. Default read-only; do not restart / delete / deploy
3. End with escalation criteria for a human
4. Mark parameterized parts as <env> / <service> / <log_path>
这三条跑通以后,才谈沉淀。Drive 不是收藏夹,它应该收纳已经被验证过、下次会复用的工作流。2注 2Note 2Warp Docs · Warp Drive —— Drive 保存 Workflows、Notebooks、Prompts、Environment Variables,并在个人与团队空间中同步;适合把跑通过的一次性过程沉淀为可复用资产。YAML 文件式 workflows 已是 legacy(只在 Command Search / Palette,不进 Drive)。Warp Docs · Warp Drive — Drive stores Workflows, Notebooks, Prompts, and Environment Variables, synced across personal and team spaces; it is the place to turn proven one-off runs into reusable assets. YAML file-based workflows are legacy (Command Search / Palette only, not in Drive).如果一个 Workflow 或 Notebook 三个月没人用,就删掉或重写;不更新的自动化,比没有自动化更危险。Only after these work should you distill them. Drive is not a favorites folder; it should hold workflows that have been validated and will be reused.2注 2Note 2Warp Docs · Warp Drive —— Drive 保存 Workflows、Notebooks、Prompts、Environment Variables,并在个人与团队空间中同步;适合把跑通过的一次性过程沉淀为可复用资产。YAML 文件式 workflows 已是 legacy(只在 Command Search / Palette,不进 Drive)。Warp Docs · Warp Drive — Drive stores Workflows, Notebooks, Prompts, and Environment Variables, synced across personal and team spaces; it is the place to turn proven one-off runs into reusable assets. YAML file-based workflows are legacy (Command Search / Palette only, not in Drive). If a Workflow or Notebook goes unused for three months, delete or rewrite it. Stale automation is more dangerous than no automation.
第一条 MCP 不要给支付、生产数据库、客户数据导出、密钥库写权限。Do not give your first MCP write access to payments, production databases, customer exports, or secret stores.
放到 Cloud Agent / OzSend to Cloud Agent / Oz
后台任务、事件触发、团队可见性、持续检查;每个 run 留下持久记录可复查。<Footnote n={3} />Background jobs, event triggers, team visibility, continuous checks; each run leaves a persistent record for review.<Footnote n={3} />
触发、验收、额度、失败通知、人工回滚说不清,就不要上云。If trigger, validation, credits, failure notification, and human rollback are unclear, do not send it to the cloud.
带上 Warp Agent CLITake the Warp Agent CLI
SSH 进服务器、远程环境、要可移植会话与云端 handoff 的活。<Footnote n={5} />SSH into servers, remote environments, work needing portable sessions and cloud handoff.<Footnote n={5} />
装不了软件的环境别硬装 —— 普通终端仍是兜底。Don't force-install where nothing can be installed — the plain terminal remains the fallback.
切给 Cursor / 编辑器Switch to Cursor / editor
大段读代码、跨文件重构、架构迁移、靠 IDE 语义导航推进的活。Large code reading, cross-file refactors, architecture migrations, work driven by IDE semantic navigation.
不要在终端里硬做编辑器的活。Do not force editor work into a terminal.
切给浏览器自动化 / Computer UseSwitch to browser automation / Computer Use
需要看页面、点击 UI、验证前端流程;Warp 的 Computer Use 是云端沙箱,不是本机控制。<Footnote n={4} />Tasks that require seeing pages, clicking UI, or verifying frontend flows; Warp's Computer Use is a cloud sandbox, not local-machine control.<Footnote n={4} />
不要把「能跑命令」误读成「能安全控制你的电脑」。Do not mistake 'can run commands' for 'can safely control your computer.'
— IV
全书验收单The Book's Acceptance Sheet.
十二章,每章一件可勾的事。逐项勾完,你不是「读过」这本书,是把它跑通过了一遍:Twelve chapters, one checkable thing each. Check every line, and you haven't 'read' this book — you've run it through once:
01 引子:我说得出 Warp 和普通终端的差别在哪 —— 不是输入框,是工作流可派发。01 Intro: I can say how Warp differs from a plain terminal — not the input box, but dispatchable workflows.
02 首胜:装好登录好,第一次只读交办拿到有用答案,第一个 Workflow 存进 Drive。02 First Win: installed and logged in, first read-only dispatch returned a useful answer, first Workflow saved to Drive.
03 底座:⌃R 找回过一条昨天的命令,高频命令加了书签。03 Blocks: recovered one of yesterday's commands with ⌃R, bookmarked a frequent one.
04 发动机:一个真实报错从交办修到验收,没开浏览器搜。04 Engine: one real error went from dispatch to verified-fixed without a browser search.
05 派活:一件批量活带 dry-run 和回滚跑完。05 Dispatch: one batch job completed with dry-run and rollback.
06 沉淀:一件重复三次的事固化成了参数化 Workflow。06 Distill: one thrice-repeated chore is now a parameterized Workflow.
07 接外部:只读 MCP 答了一题,写类工具在 denylist。07 Reach Out: a read-only MCP answered one question; its write tools are denylisted.
08 管住它:local-dev profile 配好并当场验收过 —— 该自动的自动,该拦的拦住。08 Keep It in Check: the local-dev profile is configured and validated — auto where safe, blocked where not.
09 放出去:两个 cloud run 派出去、照 transcript 验收回来,一个成了定时。09 Send Out: two cloud runs dispatched and reviewed against transcripts; one became a schedule.
10 边界:写下三件不该交给它的活,和那条绝不上云的线。10 Boundary: three tasks it shouldn't do are written down, along with the never-goes-cloud line.
11 选型:档位是按缺口选的,加购单价算过,分工表落在自己的工具栈上。11 Choose: the tier was picked by the gap, reload pricing compared, the split table mapped onto my own stack.
12 收束:30 天路线排进了日历,三条 starter workflows 至少跑通一条。12 Closing: the 30-day path is on the calendar, and at least one of the three starter workflows has run.
勾完这十二项,你就不会把 Warp 当玩具,也不会把它当神。它只是一台很强的工作台:命令在这里发生,agent 在这里动手,知识在这里沉淀,后台在这里接力,人仍然在这里负责。With those twelve checked, you'll treat Warp as neither a toy nor a god. It is just a powerful workbench: commands happen here, the agent acts here, knowledge is distilled here, background work takes the handoff here, and the human remains responsible here.
一台终端形状的元工具真正的价值,
不是替你控制电脑,
而是让命令行工作流少丢一次。.
The real value of a terminal-shaped meta-tool
is not that it controls your computer,
but that one fewer command-line workflow gets lost..
