Content Inventory
List out every piece of information to display, then decide which page each one goes on. Reverse the order and the page count keeps shifting.
- 页面画到一半发现少了个字段，整个布局要重排
- 同一个信息在三个页面都出现，但显示的详略程度不一致
- 让 AI 做详情页，它凭空补了一堆你并不需要的字段
Start from the page and you'll unconsciously fill in content by copying interfaces you've seen, plugging gaps as you go. Start from the information and the page count and layout become a result driven by content volume — not a guess.
This inventory has a side effect: it's basically a draft of your data model. Once you've spelled out which fields the user fills in and which the system computes, the table structure is mostly set.
Which Columns the Inventory Needs
| 列 | 填什么 | 它决定了什么 |
|---|---|---|
| 信息 | 一条具体的信息，不是一组 | 页面上到底要显示什么 |
| 来源 | 用户填、系统算、还是外部来的 | 要不要做输入界面，要不要处理为空 |
| 谁要看 | 本人、客户、还是管理员 | 权限设计，以及要不要做多个视图 |
| 频率 | 高频看、偶尔看、几乎不看 | 放列表页还是详情页，还是干脆折叠 |
| 长度范围 | 最短和最长可能是多少 | 布局能不能扛住极值，是不是要截断 |
Once listed, the pagination rule is also clear: high-frequency and short content goes in a list; low-frequency or long content goes in a detail view; rarely-viewed content simply isn't shown and is fetched only when needed.
Note for the AI
Having the AI produce the inventory first is far more stable than having it draw pages directly — and much easier to revise.
我要做：[功能一句话描述] 使用场景：[谁、在什么时候、要完成什么] 先不要画页面，也不要写代码。请先列一份内容清单， 表格形式，包含这几列： 信息 | 来源（用户填/系统算/外部） | 谁要看 | 查看频率 | 长度范围 要求： 1. 只列这个场景真正需要的信息。你觉得「一般都会有」 但这个场景用不上的，单独列在一个「建议不做」的区块里， 说明理由，不要直接放进主表。 2. 每一条都标出如果它为空，界面上该显示什么。 3. 列完之后，给出你建议的分页方案，并说明每一页 放这些信息的理由。 我确认清单之后，你再画页面。
The first line is the key. Without it, the AI fills in fields based on similar products it has seen, and you get a generic template instead of your product.