Launch walkthrough checklist
Function, experience, data, security — go through them one by one before launch. The checklist exists for the version of you that is rushing, when you will only click the path you know best.
- 上线一小时内用户就发现了一个你从来没点过的按钮会白屏
- 发完才想起来空态没做，新用户进去看到的是一片空白
- 自测一直用同一个老账号，全新用户的第一步早就跑不通了
- 回滚了两次，两次的原因都在上一次说过「下次记得看」
Four categories, one list
Lock the checklist into four categories, in a fixed order: Function → Experience → Data → Security. If an earlier one fails, the later ones do not matter; the last one is a single-veto gate.
| 类别 | 逐条检查 | 怎么算过 |
|---|---|---|
| 功能 | 主流程从头到尾走通；每个异步位置的四态都在；失败之后能重试且不丢已填内容；超长内容和零条数据各跑一遍 | 不用你解释就能走完 |
| 体验 | 用全新账号完整走一次；窄屏看一遍；提示语说清了发生什么和下一步；危险操作可撤销；没有「测试」「TODO」这类占位文案漏在线上 | 陌生人不问你也知道该干什么 |
| 数据 | 关键事件都上报了；失败事件带原因；属性里有能关联的 id；看板或查询语句已经准备好 | 上线第一天就能看到曲线 |
| 安全 | 密钥和令牌不在前端代码里；换个账号试访问别人的数据；权限判断后端也做了一遍；用户输入在展示前做了转义 | 试着越权，试不成功 |
How to run the walkthrough
- Switch to a brand-new account. Old accounts carry historical data and naturally skip the empty state and onboarding — exactly the two places new users hit first.
- Narrow the window once. No real device needed — drag the browser to phone width and most layout problems surface immediately.
- Throttle the network once. Limit to 3G in the browser devtools and you can see at a glance whether loading and timeout states are handled.
- Take "the wrong path" once. Fill in wrong values on purpose, leave fields empty on purpose, double-click submit on purpose — see how it responds.
- Log as you go, don't fix as you go. Note issues first; triage them all after the pass. Start editing code mid-pass and the whole walkthrough is wasted.
What blocks the release
Not every item carries the same weight. Sort them into two tiers — it takes only seconds to decide:
Let AI self-check first
If the code was written by AI, have it self-check against the list before you walk through it yourself. It is good at structural gaps like "this branch has no error handling," and bad at judging "will a user understand this hint."
对照下面的清单检查刚才这个功能，逐条给结论，不要改代码。 ## 功能 - 主流程能否走通；每个异步位置是否都有空、加载、出错、正常四态 - 失败之后能否重试，已填内容会不会丢 - 零条数据和超长内容各会怎样 ## 体验 - 全新用户第一次进来看到什么 - 窄屏下布局是否还成立 - 出错时的提示是否说清了发生什么、下一步做什么 ## 数据 - 关键事件是否已上报，失败是否带原因 ## 安全 - 是否有密钥硬编码在前端 - 权限判断是否只做在前端 - 用户输入展示前是否转义 输出格式：每条给「过 / 不过 / 不确定」，不过的给出文件和行号。 不确定的单独列出来，我来人工看。
This checklist is a good fit for your project's rules file — have it run itself before each delivery so you do not repeat it every time (see Distilling rules).