Help us improve
Share bugs, ideas, or general feedback.
From sdlc-dev-skills
Generates evidence-based page inventory, features, flows, rules, and ASCII wireframes from frontend code, outputting Markdown docs to .aisdlc/project/frontend/. Use for complex routing, dynamic pages, permissions, backend menus.
npx claudepluginhub zixun-github/aisdlcHow this skill is triggered — by the user, by Claude, or both
Slash command
/sdlc-dev-skills:frontend-page-discoveryThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
目标:基于代码证据生成页面清单与单页说明文档(落盘到 `docs/`)。
Generates production-ready frontend task breakdowns from UX design handoffs, Figma links, screenshots, or PRDs. Includes component inventory and state matrices for planning frontend work.
Generates interactive UI prototypes in frontend repositories from PRD and User Journey to validate interaction flows, states, and navigation before HLD/API contracts.
Scans frontend code for routes, pages, components, navigation, and UX artifacts to map current UI/UX state before redesign or wireframing.
Share bugs, ideas, or general feedback.
目标:基于代码证据生成页面清单与单页说明文档(落盘到 docs/)。
使用时机(触发信号)
不使用时机
.aisdlc/project/frontend/pages/index.md.aisdlc/project/frontend/pages/<page_id>.md.aisdlc/project/frontend/flows/index.md.aisdlc/project/frontend/conflicts.md本技能的输出模板已迁移到 assets/ 目录,以减少技能正文长度并保持模板可复用。
模板映射:
.aisdlc/project/frontend/pages/index.md ← <本SKILL.md目录>/assets/pages-index-template.md.aisdlc/project/frontend/pages/<page_id>.md ← <本SKILL.md目录>/assets/page-template.md.aisdlc/project/frontend/flows/index.md ← <本SKILL.md目录>/assets/flows-index-template.md.aisdlc/project/frontend/conflicts.md ← <本SKILL.md目录>/assets/conflicts-template.mdEvidence Gaps,不得写推测性结论。EXAMPLE(示例) 区块或模板;不得把示例写成项目事实,也不得与事实表格混排。module_name page_id page_name。page_name breadcrumb ascii_wireframe 核心任务 关键规则摘要。目标:线框图只能“复述代码已经存在的 UI”,不能“补齐一个你觉得应该有的后台页面”。
硬门禁(任一不满足:线框图不得落笔,只能写 Evidence Gaps)
file + lines + excerpt)。UNKNOWN(...) 表达未知,而不是写一个“合理猜测”的具体字段/文案;并把未知项逐条写入 Evidence Gaps。
UNKNOWN(...) 只能用于“已证据化存在,但细节不全”的元素(例如:代码存在按钮但文案是 i18n key 未解析)。禁止用 UNKNOWN(...) 伪装新增控件/区域(例如:没证据也画 UNKNOWN(Export) / UNKNOWN(侧边栏菜单))。推荐输出结构(先证据、后画图)
UNKNOWN(...)。证据提取优先级(建议顺序)
<h1>、document.title/useTitle、breadcrumb 组件传参、i18n keyname/label/placeholder、校验规则、默认值| 借口/压力话术 | 正确做法(强制) |
|---|---|
| “按经验补全就行 / 更像真实产品” | 只能输出 EXAMPLE(示例);事实线框图仍按证据门禁。 |
| “不能说缺信息,必须交付” | 交付 UNKNOWN(...) + Evidence Gaps;不得把未知写成具体字段/按钮。 |
| “模板里有筛选区/导出/批量操作” | 模板只是骨架;未被代码证据覆盖的控件必须保留为 UNKNOWN(...) 或删除。 |
| “至少把空态/加载/错误态都写上” | 只有在代码/组件/文案可定位时才写;否则标为 UNKNOWN(state) 并进 Evidence Gaps。 |
每条结论至少附 1 条证据:
page_title | route_decl | file_convention | menu_static | menu_backend | nav_call | guard | api_call | state_machine | form_validation | otherstart-end缺证据时,必须写:
module_name page_id page_namepage_name breadcrumb ascii_wireframe 核心任务 关键规则摘要