用 Opus 5.5 检查 vibe-coded 应用的空状态设计
Before you ship a vibe-coded app, have Opus 5.5 check what every page looks like…
提供了可直接复用的具体提示词，清晰展示了如何利用 AI 解决特定开发痛点（空状态处理），结构完整且具备实操参考价值。
Before you ship a vibe-coded app, have Opus 5.5 check what every page looks like 𝘄𝗶𝘁𝗵 𝘇𝗲𝗿𝗼 𝗱𝗮𝘁𝗮. When you test it yourself, 𝘆𝗼𝘂𝗿 𝗮𝗰𝗰𝗼𝘂𝗻𝘁 𝗮𝗹𝗿𝗲𝗮𝗱𝘆 𝗵𝗮𝘀 𝗱𝗮𝘁𝗮, so nothing looks wrong. A new user starts with nothing. Pages that were never built for that sometimes go completely blank, and sometimes just show an error.
在交付由 vibe-coded（氛围编码）生成的应用之前，让 Opus 5.5 检查每个页面在零数据情况下的显示效果。 当你自己测试时，你的账户里已经有数据了，所以看起来一切正常。但新用户是从零开始的。那些从未为无数据场景设计的页面有时会完全空白，有时则只显示错误信息。
Send it this: "List every place in this app that shows data, like lists, search results, notifications and profile pages. For each one, check three no-data cases: a new user's first visit, a search or filter with no results, and everything deleted. First tell me what each one shows right now, then fix it: anywhere that's blank or shows an error gets one line explaining why, plus a button that takes the user to the next step. When you're done, create a fresh empty account and open every page to confirm."
发送以下指令给它： “列出此应用中所有显示数据的地方，例如列表、搜索结果、通知和个人资料页面。针对每一个地方，检查三种无数据的情况：新用户的初次访问、搜索或筛选结果为空、以及所有内容被删除。首先告诉我当前每个地方显示的内容，然后修复问题：任何空白或显示错误的地方都要加上一行解释原因的文字，并添加一个引导用户进入下一步的按钮。完成后，创建一个全新的空账户，并打开每个页面进行确认。”
What a page shows when there's no data is called an empty state. Done right, it looks roughly like this 👇
当页面无数据时的显示状态被称为“空状态”（empty state）。处理得当的话，它大致如下所示 👇
更进一步：量化金融体系
看懂新闻只是起点——沿量化金融路径，把它变成能交付的工程能力