@brms/ai-skills 0.1.0

package/skills/brms-prototype-generator/references/04-composite-page-package.md

@@ -0,0 +1,339 @@
+# 组合页面包模式
+
+当产品输入不是单个页面，而是一组业务功能清单、字段清单和页面间导航关系时，使用组合页面包模式。
+
+## Compact planning first
+
+4 个及以上完整页面必须先运行 `scripts/plan-pages.mjs`，再生成 Vue 文件。使用脚本输出的 page packets 作为总控和子智能体的工作契约。
+
+```bash
+node .claude/skills/brms-prototype-generator/scripts/plan-pages.mjs <entry-md> --repo-root . --target-project <project/name> --page-prefix <PAGE_PREFIX> --format both
+```
+
+`<PAGE_PREFIX>` 必须是页面编码前缀，不是模块目录前缀。前缀至少 4 位，例如 `DMDA` 会生成 `DMDA01`、`DMDA02`；禁止用 `KQ` 这类 2 位前缀生成 `KQ01`。
+
+不要让每个页面生成任务都重新携带完整产品文档和全部 reference。每个页面任务只需要：全局计划摘要、自己的 page packet、`references/resource-index.md` 指定的必要规则、已创建的共享数据契约、以及该页面的校验命令。
+
+## 适用场景
+
+- 文档中包含多个一级编号功能模块，如“1. 区域公司结构管理”“2. 矿权项目维护”
+- 文档末尾包含“页面间导航关系”或明显的跨页面跳转
+- 多个页面共享同一批业务维度、字典或 mock 数据
+- 页面包中有明确 serviceName/methodName 的页面需要真实接口原型，其他页面仍保持 mock
+- 一个功能既可以独立进入，也可以从其他页面带参数进入
+
+## 生成目标
+
+组合页面包不是生成一个超大 Vue 文件，而是生成一组可独立访问、可互相跳转的页面：
+
+```text
+<target-project>/src/views/<MODULE>/<SUBMODULE>/
+  ├── <CODE01>.vue       # 页面 1：区域公司结构管理
+  ├── <CODE02>.vue       # 页面 2：矿权项目维护
+  ├── <CODE03>.vue       # 页面 3：矿权信息维护
+  └── components/        # 仅当多个页面确实复用时才创建
+```
+
+每个页面仍然遵循单页面模式：
+
+- 管理维护页：参考 `01-list-query.md`
+- 新增/编辑弹窗：优先内嵌在当前维护页中，不单独注册菜单
+- 详情/只读页：参考 `03-detail-display.md`
+- 附件、任务、通知等功能：如果文档中给了独立入口，则生成独立页面；如果只是某页面的行操作，则生成弹窗或抽屉
+
+## 组合页布局规则
+
+- 主从页不要把多个表格硬塞进一个纵向结果卡片；区域公司/公司这类页面使用左右布局。
+- 左右布局推荐：
+
+```vue
+<div class="flex h-full gap-4">
+  <BxRoundedContainer class="w-1/3 flex flex-col">
+    <BxContainer class="flex-initial" title="区域公司列表" />
+    <VxePlusTable class="flex-1" />
+  </BxRoundedContainer>
+
+  <BxRoundedContainer class="flex-1 flex flex-col">
+    <BxContainer class="flex-initial" title="下属公司" />
+    <VxePlusTable class="flex-1" />
+  </BxRoundedContainer>
+</div>
+```
+
+- `BxContainer` 是标题栏，必须使用 `flex-initial`，不要让标题栏挤压下方表格。
+- 结果/列表标题不要使用 `custom-btn-auto`；查询按钮只属于查询区。
+- 不生成操作列和复选框列；复选框使用 `VxePlusTable :show-checkbox="true"`，行操作使用工具栏、业务字段点击或行点击。
+- 普通列使用 `useTable().createColumns([...], { width: undefined })` 自动撑开。
+
+## 拆分规则
+
+1. 每个一级编号功能默认拆成一个菜单页面。
+2. “新增/编辑弹窗”“上传弹窗”“附件列表弹窗”默认作为页面内部弹窗，不创建单独路由。
+3. “综合查询”“任务管理”“合规报告计划”等有独立入口的功能创建独立路由。
+4. 附录里的导航关系必须转化为按钮、链接或带 query 的路由跳转。
+5. 多页面共享的枚举、mock 数据和工具函数，放在同目录 `components/` 或 `data.ts` 中；只有两个以上 mock 页面复用时才抽取。`data.ts` 里导出的 mock 数组/对象必须在声明前写 `// @brms-mock-data <source-or-page>: <purpose>`，方便真实接口接入后清理。
+6. 接口是逐页、逐方法 opt-in：有明确 serviceName/methodName 的页面读 `06-backend-request-patterns.md` 并生成真实请求；没有明确接口的页面继续 mock。
+
+## 菜单结构优先级
+
+如果产品文档末尾存在“页面间导航关系”“导航关系”或类似文本树，必须先分析这棵树，再规划页面和菜单。
+
+- 导航树是菜单层级和跨页面入口的主要依据，优先级高于章节顺序。
+- 树节点能匹配生成页面时，注册为可访问菜单项。
+- 树节点只是分组名称且有子节点时，注册为父菜单或分组节点。
+- 树中的父子关系必须转化为真实交互：按钮、业务字段点击、卡片入口、tab 切换或 `router.push`。
+- 不要把有层级的导航树简单拍平成同级菜单，除非用户明确确认。
+
+生成规划时先输出：
+
+1. 解析出的导航/菜单树。
+2. 树节点到页面编码、文件路径和菜单标题的映射。
+3. 每条跨页面边对应的 UI 入口和 `query` 参数。
+4. 无法匹配到页面的树节点及处理方式。
+
+## 按钮和功能完整性
+
+所有文档中的功能、按钮、操作和跳转都必须有可见入口和可执行处理函数。
+
+- 新增、编辑、保存、删除、上传、下载、状态切换、提醒开关、生成任务等功能不能只画按钮。
+- 每个按钮必须能打开弹窗/抽屉、修改本地 mock 数据、筛选表格、重置表单、切换状态、选择 mock 文件或执行页面跳转。
+- 后台相关按钮使用 TODO toast，但仍然要在本地完成可见反馈，让原型可点击。
+- 跨页面按钮必须使用 `router.push({ path: '/web/<MODULE>/<SUBMODULE>/<CODE>', query: {...} })`。
+- 目标页必须读取 `route.query`，作为默认筛选条件或预填上下文。
+- 每生成一个页面后，对照功能表逐项检查：没有 handler 的按钮视为未完成。
+
+## 生成方式选择
+
+拆分页面清单后，先输出识别出的完整页面数量，再让用户在三种方式中选择。不要在用户选择前直接写多页面代码。
+
+| 生成方式                                        | 适用场景                                        | 执行规则                                                                                |
+| ----------------------------------------------- | ----------------------------------------------- | --------------------------------------------------------------------------------------- |
+| `single-agent-package` 整包一次性生成           | 1-3 个完整页面，页面关系简单                    | 一个 agent 按全局规划生成全部页面、共享数据和菜单。速度最快，但页面多时更容易遗漏规则。 |
+| `coordinator-sequential` 总控逐页顺序生成       | 4 个以上页面，或当前环境不支持子智能体          | 当前 agent 每次只生成一个页面，生成后立即做局部规则检查，最后统一生成共享数据和菜单。   |
+| `coordinator-subagents` 总控 + 子智能体逐页生成 | 4 个以上页面，且当前环境支持子智能体/并行 agent | 总控负责规划、共享数据契约、菜单和最终验证；每个子智能体只负责一个页面文件。            |
+
+默认建议：
+
+- 完整页面数 `<= 3`：推荐 `single-agent-package`。
+- 完整页面数 `>= 4`：优先推荐 `coordinator-subagents`。
+- 如果当前工具环境没有子智能体能力：推荐 `coordinator-sequential`。
+
+### 子智能体任务边界
+
+使用 `coordinator-subagents` 时，总控先产出全局页面包规划和共享数据契约，再给每个子智能体一个页面任务包。任务包至少包含：
+
+- 页面编码、标题、路径、页面类型。
+- 需要使用的字段、mock 数据名称、枚举名称；如有明确接口，列出 serviceName、methodName 和是否使用 serviceConfig。mock 数据名称旁必须说明对应的 `@brms-mock-data` 标记文本。
+- 页面入口、跳转 query 契约和需要读取的 `route.query`。
+- 必须遵守的布局/表格规则。
+- 禁止修改的文件清单。
+
+子智能体只能编辑自己分配的 `<target-project>/src/views/<MODULE>/<SUBMODULE>/<CODE>.vue`。子智能体不能编辑路由配置、共享 `data.ts`、`localMenu.ts`、其他页面或文档。总控在所有页面完成后统一创建共享文件；只有目标项目存在 `src/routers/config/index.ts` 时才创建新的菜单配置文件，否则输出权限中心配置交接信息。
+
+## 页面编码规则
+
+如果产品文档没有给页面编码，需要先为页面包分配同一模块/子模块前缀，再按功能顺序编号：
+
+- 页面编码必须是 6 位及以上大写字母数字，例如 `DMDA01`、`MNRG01`。
+- 页面编码前 2 位是模块目录，后 2 位是子模块目录；`DMDA01` 对应 `src/views/DM/DA/DMDA01.vue`。
+- 不允许只使用 2 位模块前缀编号，例如 `KQ01`。如果只知道模块是 `KQ`，必须先询问或从产品文档/菜单树推导子模块前缀，再生成页面。
+- 页面文件名、Vue route `name`、动态路由 `path` 的页面编码必须一致。
+
+```text
+MNRG01 区域公司结构管理
+MNRG02 矿权项目维护
+MNRG03 矿权信息维护
+MNRG04 矿权信息综合查询
+MNRG05 项目资料上传
+MNRG06 矿权任务管理
+MNRG07 任务到期提醒
+MNRG08 合规报告计划
+```
+
+编码前 2 位决定模块目录，中 2 位决定子模块目录，例如：
+
+```text
+<target-project>/src/views/MN/RG/MNRG01.vue
+<target-project>/src/views/MN/RG/MNRG02.vue
+```
+
+如果用户指定编码前缀，必须使用用户指定前缀，但仍必须满足 4 位及以上前缀规则。例如用户指定 `DMDA` 时，页面必须命名为 `DMDA01`、`DMDA02`，不能退化成 `DM01` 或 `KQ01`。
+
+## 菜单注册
+
+组合页面包通常需要在同一个父菜单下注册多个子菜单。只有目标项目存在静态路由配置时才新建独立菜单文件，不要修改 `localMenu.ts`。
+
+- 目录：`<target-project>/src/routers/config/`
+- 文件名：`<小写页面包前缀>-<yyyymmddhhmmss>.ts`，例如 `mnrg-20260530143000.ts`
+- 自动加载：`config/index.ts` 已经自动引入同目录 `.ts` 文件，无需手动 import
+- 重复生成：旧的同前缀菜单文件仍会被加载；如出现重复菜单，提示用户删除或归档旧生成文件
+- 如果 `<target-project>/src/routers/config/index.ts` 不存在，跳过菜单文件生成，不创建路由目录，并输出权限中心配置交接清单。
+- 动态菜单 `path` 只写页面编码：`/MNRG01`。运行时 `auth.ts` 会自动拼成 `/web/MNRG01`。
+- 不要把物理目录写进动态菜单 `path`，例如禁止 `/MN/RG/MNRG01`、`/KQ/02/KQ02`。物理目录只属于 `component`。
+- 页面内跳转也必须使用运行时路径 `/web/<PAGE_CODE>`，例如 `router.push({ path: '/web/MNRG03' })`；不要写 `/web/MN/RG/MNRG03`。
+- `name` 必须等于页面编码，例如 `DMDA01`。
+- `component` 使用物理路径，例如 `'/DM/DA/DMDA01'`。
+- 详情页、跳转页、仅从其他页面进入的页面也必须放在同一个父菜单的 `children` 中，只是设置 `meta.isHide: true`；不要把它们作为 `export default` 数组里的第二个顶层 route。
+- 一个页面包通常只导出一个父菜单对象；除非产品文档明确要求多个并列父菜单，否则不要在顶层数组中混放父菜单和同前缀页面。
+
+`component` 推荐填写相对 `src/views` 的文件路径，不含 `.vue`：
+
+```typescript
+export default [
+  {
+    path: '/MNMenu',
+    name: 'MNMenu',
+    meta: {
+      icon: 'Folder',
+      title: '矿权管理',
+      isLink: '',
+      isHide: false,
+      isFull: false,
+      isAffix: false,
+      isKeepAlive: true,
+    },
+    children: [
+      {
+        path: '/MNRG01',
+        name: 'MNRG01',
+        component: '/MN/RG/MNRG01',
+        meta: {
+          icon: 'Menu',
+          title: '区域公司结构管理',
+          isLink: '',
+          isHide: false,
+          isFull: false,
+          isAffix: false,
+          isKeepAlive: true,
+        },
+      },
+      {
+        path: '/MNRG02',
+        name: 'MNRG02',
+        component: '/MN/RG/MNRG02',
+        meta: {
+          icon: 'Menu',
+          title: '矿权项目维护',
+          isLink: '',
+          isHide: false,
+          isFull: false,
+          isAffix: false,
+          isKeepAlive: true,
+        },
+      },
+      {
+        path: '/MNRG04',
+        name: 'MNRG04',
+        component: '/MN/RG/MNRG04',
+        meta: {
+          icon: 'Menu',
+          title: '矿权详情',
+          isLink: '',
+          isHide: true,
+          isFull: false,
+          isAffix: false,
+          isKeepAlive: true,
+        },
+      },
+    ],
+  },
+];
+```
+
+## 跨页面跳转规则
+
+使用 `router.push` 跳转，并通过 query 传递筛选条件或上下文：
+
+```typescript
+router.push({
+  path: '/web/MNRG03',
+  query: {
+    projectCode: row.projectCode,
+    projectName: row.projectName,
+  },
+});
+```
+
+目标页面在初始化时读取 query，作为默认筛选条件：
+
+```typescript
+const route = useRoute();
+
+onMounted(() => {
+  if (route.query.projectCode) formData.projectCode = String(route.query.projectCode);
+});
+```
+
+跨页面跳转是完整性规则，不是装饰规则：
+
+- 每条产品文档里的跳转关系，都必须在源页面有可见入口，例如按钮、业务字段点击、卡片入口或 tab。
+- 源页面入口必须调用 `router.push({ path: '/web/<PAGE_CODE>', query: {...} })`。
+- 目标页面必须读取 `route.query`，并将 query 用作默认筛选、预填上下文或高亮当前记录。
+- 生成计划的 page packet 必须列出该页面的 inbound/outbound navigation contract；逐页生成时不得丢弃这些跳转。
+
+## 针对 function.md 的映射示例
+
+`project/prototype/doc/function.md` 应拆成 8 个页面：
+
+| 页面             | 页面类型       | 建议实现                                             |
+| ---------------- | -------------- | ---------------------------------------------------- |
+| 区域公司结构管理 | 主从维护页     | 左侧区域公司列表 + 右侧公司列表，新增/编辑公司用弹窗 |
+| 矿权项目维护     | 列表维护页     | 项目列表 + 新增/编辑弹窗 + “查看矿权”跳转            |
+| 矿权信息维护     | 列表维护页     | 筛选区 + 矿权列表 + 合计行 + 附件/任务操作           |
+| 矿权信息综合查询 | 查询汇总页     | 筛选区 + 结果列表 + 汇总维度切换                     |
+| 项目资料上传     | 附件管理页     | 附件列表 + 上传弹窗                                  |
+| 矿权任务管理     | 任务维护页     | 任务筛选 + 状态流转按钮 + 新增/编辑弹窗              |
+| 任务到期提醒     | 通知设置页     | 提醒设置 + 通知列表                                  |
+| 合规报告计划     | 报告计划维护页 | 报告类型列表 + 新增报告任务跳转                      |
+
+## 输出顺序
+
+1. 先输出解析出的导航/菜单树；如果没有树，再按章节顺序规划。
+2. 输出页面包规划：页面编码、标题、类型、路径、菜单层级、跳转关系、按钮/功能清单。
+3. 输出完整页面数量、三种生成方式和推荐方式，等待用户选择。
+4. 根据用户选择执行整包生成、总控逐页生成或总控 + 子智能体逐页生成。
+5. 创建共享 mock 数据或工具文件；明确接口页不要为了表格数据额外创建无用 mock rows。共享 `data.ts` 的每个 mock export 都必须有 `@brms-mock-data`。
+6. 逐个生成页面文件，并逐页检查按钮 handler 和跳转 handler。
+7. 如果目标项目支持静态路由，最后新建独立菜单配置文件，不修改 `localMenu.ts`；否则输出权限中心菜单配置交接信息。
+8. 只在全部文件生成后做一次 `vue-tsc` 或 dev 启动验证。
+
+## Multi-Page Second-Pass Validation
+
+At the end of a composite page package generation, run a second validation pass before reporting completion.
+
+Required checks:
+
+1. Compare generated page count and route config against the analyzer report.
+2. If `menuStructureDetected` was true, compare route/menu hierarchy against the parsed navigation tree. Do not flatten the tree unless the user explicitly approved it.
+3. Check hidden detail/jump-only pages are inside the same parent menu `children` with `isHide: true`, not outside the parent as top-level route siblings.
+4. Check every generated `.vue` template has exactly one top-level root, and every dialog/modal is inside that root.
+5. Check every mock-backed generated `VxePlusTable` with `:columns` also has mock-backed `:data` and searchable `@brms-mock-data` / `@brms-mock-handler` markers; check every interface-backed table has a marker and documented `serviceConfig`.
+6. Check that no page has operation/action columns or checkbox columns in `createColumns`.
+7. Check every documented function, button, operation, and navigation edge has a visible UI entry and a wired handler.
+8. Check generated action buttons are not placed in `BxContainer` slots (`#left`, `#right`, `#default`, `#custom-btn`) unless the product document explicitly requested header-slot buttons.
+9. Check cross-page navigation uses `router.push({ path: '/web/<PAGE_CODE>' , query: {...} })`, and target pages read `route.query`.
+10. Check generated pages do not use `serviceConfig`, `EiCommunicator`, `EiInfo`, `http`, or real backend services unless the product document explicitly names the service and methods; explicit-interface files must include `// @brms-explicit-interface ...`.
+11. If static route config exists, check route config is a new file and `localMenu.ts` was not edited. If it does not exist, check no route directory/file was created and the permission-center handoff is present.
+12. Check generated `.vue` files do not use JSX/TSX; custom table cells must use template slots.
+13. Check dialogs follow `references/05-dialog-patterns.md`; reject unknown components such as `VxePlusDialog`.
+14. Check every dialog `VxePlusForm` uses `:form-options`, not `:form-config`.
+15. Check simple one-section dialogs do not contain `BxContainer`/`bx-container`; only multi-section dialogs may add section containers.
+16. Check attachment upload/view flows do not create custom modals. They must call `useFileUpload().openFileBFSS0001` with demo parameters and TODO markers when real parameters are unavailable.
+
+Run:
+
+```bash
+node .claude/skills/brms-prototype-generator/scripts/validate-generated.mjs <generated-vue-or-route-files> --repo-root .
+```
+
+Then run `vue-tsc` when the correct Node/pnpm environment and installed dependencies are available. Fix failures and repeat this second pass.
+
+After validation, write a compact handoff summary for follow-up turns:
+
+```text
+<target-project>/.generation-summaries/<lowercase-page-prefix>-<yyyymmddhhmmss>.md
+```
+
+Include generated files, menu tree, query contracts, per-page functions, validation output, remaining issues, and constraints. Read this summary first in later repair turns to avoid losing direction when chat context gets long.
+
+For Claude Code, a skill cannot execute `/compact` automatically. After the summary is written, tell the user they may run `/compact` manually. Do not imply that compaction has already happened.

package/skills/brms-prototype-generator/references/05-dialog-patterns.md

@@ -0,0 +1,113 @@
+# Dialog Patterns
+
+Use only dialog patterns that already exist in the confirmed target project or in the bundled references. Do not invent components such as `VxePlusDialog`, `FileUploadDialog`, `UploadDialog`, `BxUploadDialog`, `AttachmentDialog`, or other unverified dialog/upload wrappers.
+
+## Pattern A: Normal Form Or Detail Modal
+
+Use this for add, edit, detail, change, confirmation-detail, and other page-local dialogs.
+
+Reference behavior: `vxe-modal` provides the dialog title. Do not add another `BxContainer` title for a simple one-section form.
+
+Rules:
+
+- Use `<vxe-modal v-model="modal" title="..." width="..." show-footer show-cancel-button show-confirm-button cancel-button-text="取消" confirm-button-text="确定" @confirm="handleSave">`.
+- Put `VxePlusForm` directly inside the modal for a simple one-section form.
+- Use `VxePlusForm :form-options="formOption"` inside dialogs.
+- Do not use `VxePlusForm :form-config` inside dialogs; that prop is for table query binding patterns and will render an empty dialog form.
+- Do not wrap the form with `<bx-container>` or `<BxContainer>` unless the dialog has multiple sections that genuinely need section titles.
+- Do not rely on `show-footer` alone. `vxe-modal` defaults `show-cancel-button` and `show-confirm-button` to `false` for normal modals, so generated add/edit/detail modals must explicitly set both button visibility props and button text props.
+- Prefer the built-in modal footer buttons over a custom `<template #footer>` for generated form dialogs. Bind the save logic through `@confirm`; the cancel button should close the modal through the built-in behavior.
+- Keep modal visibility as `const modal = ref(false)`.
+- Open the modal from a real handler, such as `handleAdd`, `handleEdit`, or `handleView`.
+- For table edit dialogs, open the modal from `toolbarButtonClick`, an explicit selected-row handler, or a business-field `tableLink`; do not use `cell-click` / `handleCellClick` as the edit opener.
+- A table using this dialog edit pattern must not also set `VxePlusTable :is-edit="true"` or column `editRender`; those belong to the row edit pattern in `references/01-list-query.md`.
+- The save/confirm handler must mutate local mock data and show a TODO backend toast when the action represents a backend operation.
+- If the save/confirm handler only mutates local mock data, put `// @brms-mock-handler <source-or-page>: dialog save, replace with ServiceName.save` immediately before the handler.
+
+Example:
+
+```vue
+<vxe-modal
+  v-model="modal"
+  title="变更"
+  width="500px"
+  show-footer
+  show-cancel-button
+  show-confirm-button
+  cancel-button-text="取消"
+  confirm-button-text="确定"
+  @confirm="handleSave"
+>
+  <VxePlusForm ref="formRef" :form-options="formOption" />
+</vxe-modal>
+```
+
+```ts
+const modal = ref(false);
+const formData = reactive({
+  type: '',
+  name: '',
+});
+
+const formOption = reactive({
+  id: 'change_form',
+  data: formData,
+  items: [
+    { field: 'type', title: '类型', itemRender: { name: 'formSelect', props: { options: [] } } },
+    { field: 'name', title: '名称', itemRender: { name: 'vxe-input' } },
+  ],
+});
+
+function handleEdit(row: any) {
+  Object.assign(formData, row);
+  modal.value = true;
+}
+
+// @brms-mock-handler product-doc: dialog save, replace with ServiceName.save
+function handleSave() {
+  // TODO: 接入后台保存接口
+  ElMessage.info('TODO: 接入后台接口');
+  upsertLocalRow(rows.value, formData);
+  modal.value = false;
+}
+```
+
+## Pattern B: Existing File Upload Dialog
+
+Use this for attachment upload and attachment view flows when the prototype should use the project's real file dialog shell.
+
+Reference implementation: `<target-project>/src/hooks/useFileUpload.ts` when it exists; `project/prototype/src/hooks/useFileUpload.ts` can be used only as a fallback reference.
+
+Rules:
+
+- Import `useFileUpload` from `@/hooks/useFileUpload`.
+- Always use `openFileBFSS0001` for generated attachment upload/view actions.
+- Do not create a new upload/view modal with `vxe-modal`, `el-dialog`, `el-upload`, or a custom component.
+- Do not create new upload dialog component names.
+- Pass business identifiers from the selected mock row when available.
+- If the product document does not provide ids or codes, demo-construct the parameters and add `TODO: confirm attachment parameters for openFileBFSS0001`.
+- Show a TODO toast before opening or simulating the upload action so the backend boundary remains visible.
+
+Example:
+
+```ts
+import { useFileUpload } from '@/hooks/useFileUpload';
+
+const { openFileBFSS0001 } = useFileUpload();
+
+function handleUpload(row: any) {
+  // TODO: confirm attachment parameters for openFileBFSS0001.
+  ElMessage.info('TODO: 接入附件上传接口');
+  openFileBFSS0001({
+    bizTypeCode: 'MNRG_ATTACHMENT',
+    fileTypeCode: 'MNRG_ATTACHMENT',
+    bizBillId: row.id || row.attachmentId || 'DEMO_BILL_ID',
+    bizBillCode: row.code || row.mineralRightCode || row.projectCode || 'DEMO_BILL_CODE',
+    bizBillVersion: '1.00',
+    flag: 'operate',
+    cb: () => {
+      ElMessage.success('附件操作完成');
+    },
+  });
+}
+```

package/skills/brms-prototype-generator/references/06-backend-request-patterns.md

@@ -0,0 +1,118 @@
+# Backend Request Patterns
+
+Use this reference only when the product document explicitly provides backend service and method names. Otherwise generate mock-backed pages.
+
+## Interface Gate
+
+Treat an interface as explicit only when the document names at least:
+
+- `serviceName`, such as `BMBF56`;
+- one concrete method name, such as `query`, `insert`, `save`, `delete`, or `queryExport`.
+
+Do not infer method names from common CRUD words, page codes, menu names, or examples from other pages. If the interface is unclear, keep local mock data and TODO backend toasts.
+
+Every generated file that uses real interface wiring must include a marker comment near the request config/imports:
+
+```ts
+// @brms-explicit-interface product-doc: BMBF56.query/BMBF56.delete
+```
+
+## Standard List CRUD Pattern
+
+Follow the style of the standard sample `project/prototype/src/views/DM/DA/DMDA02.vue` for documented list CRUD interfaces, but add the explicit-interface marker required by this skill.
+
+```vue
+<VxePlusTable
+  ref="xGrid"
+  :columns="columns"
+  :service-config="serviceConfig"
+  :show-checkbox="true"
+  :is-edit="true"
+  :form-config="formConfig"
+  v-on="gridEvents"
+/>
+```
+
+```ts
+import { EiCommunicator, EiInfo } from '@eplat/ei';
+
+// @brms-explicit-interface product-doc: BMBF56.query/BMBF56.insert/BMBF56.save/BMBF56.delete
+const formConfig = reactive({
+  id: 'inqu_status',
+  data: formData,
+});
+
+const serviceConfig = reactive({
+  serviceName: 'BMBF56',
+  queryMethod: 'query',
+  insertMethod: 'insert',
+  updateMethod: 'save',
+  deleteMethod: 'delete',
+});
+```
+
+Query and reset buttons should reload the grid:
+
+```ts
+function btnClick({ code }: { code: string }) {
+  if (code === 'BTN_QUERY' || code === 'QUERY') {
+    xGrid.value?.reload();
+  } else if (code === 'BTN_RESET' || code === 'RESET') {
+    formRef.value?.reset?.();
+    xGrid.value?.reload();
+  }
+}
+```
+
+## Custom EiInfo Actions
+
+For documented actions that are not covered by `serviceConfig`, call `EiCommunicator.send(serviceName, methodName, ei)` directly.
+
+```ts
+async function deleteSelectedRows($grid: any) {
+  const selectedRows = $grid.getCheckboxRecords();
+  if (!selectedRows.length) {
+    ElMessage.warning('请选择一行数据！');
+    return;
+  }
+
+  const ei = new EiInfo();
+  selectedRows.forEach((row: RowVO, index: number) => {
+    ei.set('result', index, 'id', row.id);
+  });
+
+  const res = await EiCommunicator.send('BMBF56', 'delete', ei);
+  if (res.status < 0) {
+    ElMessage.error(res.msg || '删除失败');
+    return;
+  }
+
+  ElMessage.success(res.msg || '删除成功');
+  $grid.commitProxy('query');
+}
+```
+
+For export/query actions, map non-empty query fields using the form block naming convention expected by the backend:
+
+```ts
+async function exportRows() {
+  const ei = new EiInfo();
+  Object.keys(formData).forEach((key) => {
+    const value = formData[key as keyof typeof formData];
+    if (value) {
+      ei.set(`inqu_status-0-${key}`, value);
+    }
+  });
+
+  const res = await EiCommunicator.send('BMBF56', 'queryExport', ei);
+  if (res.status < 0) {
+    ElMessage.error(res.msg || '导出失败');
+  }
+}
+```
+
+## Mixed Page Rule
+
+A page may mix real documented interfaces and mock-only interactions. Use real requests only for the documented methods. Keep undocumented buttons clickable with local mock behavior and TODO toasts.
+
+Do not create fake `serviceConfig` values, fake `EiCommunicator.send` methods, or empty request shells just because the page has a backend service section.

package/skills/brms-prototype-generator/references/resource-index.md

@@ -0,0 +1,46 @@
+# Resource Index
+
+Use this index after `analyze-doc.mjs` or `plan-pages.mjs`. Load only the files required by the current page packet.
+
+## Workflow Resources
+
+- `04-composite-page-package.md`: read for 4+ page packages, page code naming, route/menu hierarchy, cross-page navigation contracts, coordinator/worker split, shared data contracts, and final handoff.
+- `templates/user-input-template.md`: read only when helping the user prepare or improve the product Markdown.
+- `system-prompt.md`: legacy full prompt for external/manual use. Do not load during normal skill execution unless the user explicitly asks for the old full prompt.
+
+## Page Pattern Resources
+
+- `01-list-query.md`: list pages, query/result layouts, row-edit vs dialog-edit selection, table toolbar buttons, mock table data, and `VxePlusTable` usage.
+- `02-form-entry.md`: standalone add/edit/create pages and form-heavy entry pages.
+- `03-detail-display.md`: detail/read-only pages, approval-like detail layouts, and subtable display.
+
+## Rule Resources
+
+- `05-dialog-patterns.md`: load only when the page packet mentions add/edit/detail/change dialogs, drawers, upload, attachment view, attachment delete, or any modal behavior.
+- `06-backend-request-patterns.md`: load only when the product document explicitly names backend service and method names. If only page codes or generic CRUD words exist, stay mock-backed and do not load this file.
+
+## Example Resource
+
+- `examples/few-shot-examples.md`: search by keyword and read the smallest relevant snippet. Useful search terms: `查询条件`, `结果集`, `vxe-modal`, `@brms-explicit-interface`, `toolbarButtonClick`, `附件`, `page package`.
+
+## Page Type To Resources
+
+| Page packet type        | Required resources                                 | Conditional resources                                     |
+| ----------------------- | -------------------------------------------------- | --------------------------------------------------------- |
+| `list-query`            | `01-list-query.md`                                 | `05-dialog-patterns.md`, `06-backend-request-patterns.md` |
+| `list-maintenance`      | `01-list-query.md`                                 | `05-dialog-patterns.md`, `06-backend-request-patterns.md` |
+| `master-detail`         | `01-list-query.md`, `04-composite-page-package.md` | `05-dialog-patterns.md`                                   |
+| `form-entry`            | `02-form-entry.md`                                 | `06-backend-request-patterns.md`                          |
+| `detail-display`        | `03-detail-display.md`                             | `06-backend-request-patterns.md`                          |
+| `attachment-management` | `01-list-query.md`, `05-dialog-patterns.md`        | `06-backend-request-patterns.md`                          |
+| `task-management`       | `01-list-query.md`                                 | `05-dialog-patterns.md`, `06-backend-request-patterns.md` |
+
+## Multi-Page Context Rule
+
+For 4+ pages, do not keep the full product document in context for each page. Use `plan-pages.mjs` and give each generation worker only:
+
+- the global plan summary;
+- its own page packet;
+- the required resources listed in that page packet;
+- the shared data contract if already created;
+- the validation command for its file.