@brms/ai-skills 0.1.0

package/skills/brms-prototype-generator/templates/user-input-template.md

@@ -0,0 +1,182 @@
+# 页面生成请求模板
+
+产品经理填写此模板后，复制内容在 Claude Code 中发起对话即可生成原型页面。
+
+---
+
+## 快速使用
+
+1. 复制下方模板
+2. 填入你的业务需求
+3. 在 Claude Code 中粘贴，发送
+4. AI 生成后优先运行目标项目对应的 `pnpm --filter <target-package-name> exec vue-tsc --noEmit --pretty false` 验证
+
+---
+
+## 模板
+
+```
+请根据以下需求生成 BRMS 原型页面：
+
+### 页面类型
+[ ] 列表查询页（搜索 + 表格）
+[ ] 表单录入页（新增/编辑表单）
+[ ] 详情展示页（只读查看 + 子表）
+[ ] 组合页面包（多个页面 + 页面间跳转）
+
+### 生成方式（组合页面包可选；不填则由 AI 分析后询问）
+[ ] 整包一次性生成（1-3 个页面推荐）
+[ ] 总控逐页顺序生成（页面较多、希望更稳）
+[ ] 总控 + 子智能体逐页生成（4 个以上页面且工具支持子智能体时推荐）
+
+### 基本信息
+- 页面编码：<6位大写字母，如 FMXR01>
+- 页面标题（中文）：<如 汇率管理>
+- 所属菜单（中文）：<如 财务管理>
+- 页面包编码前缀（组合页面包填写）：<如 MNRG，生成 MNRG01、MNRG02...>
+- 页面包名称（组合页面包填写）：<如 矿权管理>
+
+### 后端服务
+- 服务名：<如 FMXR01>
+- 查询方法：query
+- 新增方法：add（如需要）
+- 更新方法：save（如需要）
+- 删除方法：delete（如需要）
+
+### 查询条件（列表页）
+| 字段名 | 显示名 | 类型 | 字典/说明 |
+|--------|--------|------|-----------|
+| <fieldName> | <显示名> | input/select/date/dateRange | <字典编码或留空> |
+| ... | ... | ... | ... |
+
+### 表格列（列表页）或 表单字段（录入页）
+| 字段名 | 显示名 | 类型 | 是否可编辑 | 字典/说明 |
+|--------|--------|------|-----------|-----------|
+| <fieldName> | <显示名> | text/select/date/input | Yes/No | <字典编码或留空> |
+| ... | ... | ... | ... | ... |
+
+### 工具栏按钮（列表页）
+[ ] 新增按钮
+[ ] 删除按钮（需勾选行）
+[ ] 导出按钮
+[ ] 其他：<描述>
+
+### 特殊需求
+[ ] Tab 切换多表格（请描述每个 tab：<tab1名称, tab2名称>）
+[ ] 级联下拉（请描述级联关系：<大类→中类→小类>）
+[ ] 附件上传（请描述附件类型：<如 A1P001>）
+[ ] 行内编辑
+[ ] 审批操作
+[ ] 其他：<描述>
+
+### 组合页面包清单（选择“组合页面包”时填写）
+请按功能模块列出每个页面。AI 会根据清单拆分页面、生成菜单和跳转关系。
+
+| 序号 | 页面标题 | 页面类型 | 主要区域 | 主要操作 | 跳转关系 |
+|------|----------|----------|----------|----------|----------|
+| 1 | <区域公司结构管理> | 主从维护页 | <区域公司列表、公司列表、编辑弹窗> | <新增、编辑、删除、查看下属公司> | <无> |
+| 2 | <矿权项目维护> | 列表维护页 | <筛选区、项目列表、编辑弹窗> | <新增、编辑、删除、查看矿权> | <查看矿权 -> 矿权信息维护> |
+
+### 共享数据/枚举（组合页面包可选）
+| 数据名称 | 字段 | 说明 |
+|----------|------|------|
+| <区域公司> | <name> | <固定6个区域公司> |
+| <公司> | <name, regionName> | <公司隶属于区域公司> |
+
+### 页面间导航关系（组合页面包可选）
+文本树：
+首页/工作台
+  ├── <页面A>
+  │     └── <页面B（从页面A带参数跳转）>
+  └── <页面C>
+```
+
+---
+
+## 填写示例
+
+以下是一个已经填好的示例，供参考格式：
+
+```
+请根据以下需求生成 BRMS 原型页面：
+
+### 页面类型
+[x] 列表查询页（搜索 + 表格）
+
+### 基本信息
+- 页面编码：FMXR01
+- 页面标题（中文）：汇率管理
+- 所属菜单（中文）：财务管理
+
+### 后端服务
+- 服务名：FMXR01
+- 查询方法：query
+- 新增方法：add
+- 更新方法：save
+- 删除方法：delete
+
+### 查询条件（列表页）
+| 字段名 | 显示名 | 类型 | 字典/说明 |
+|--------|--------|------|-----------|
+| currencyCodeLike | 币种代码 | input | |
+| effectiveDate | 生效日期 | dateRange | |
+
+### 表格列（列表页）
+| 字段名 | 显示名 | 类型 | 是否可编辑 | 字典/说明 |
+|--------|--------|------|-----------|-----------|
+| currencyCode | 币种代码 | text | Yes | |
+| currencyName | 币种名称 | text | Yes | |
+| exchangeRate | 汇率 | text | Yes | |
+| effectiveDate | 生效日期 | date | Yes | |
+
+### 工具栏按钮（列表页）
+[x] 新增按钮
+[x] 删除按钮（需勾选行）
+
+### 特殊需求
+无
+```
+
+---
+
+## 组合页面包填写示例
+
+```
+请根据以下需求生成 BRMS 原型页面：
+
+### 页面类型
+[x] 组合页面包（多个页面 + 页面间跳转）
+
+### 生成方式（组合页面包可选；不填则由 AI 分析后询问）
+[ ] 整包一次性生成（1-3 个页面推荐）
+[ ] 总控逐页顺序生成（页面较多、希望更稳）
+[x] 总控 + 子智能体逐页生成（4 个以上页面且工具支持子智能体时推荐）
+
+### 基本信息
+- 页面包编码前缀：MNRG
+- 页面包名称：矿权管理
+- 所属菜单（中文）：矿权管理
+
+### 组合页面包清单
+| 序号 | 页面标题 | 页面类型 | 主要区域 | 主要操作 | 跳转关系 |
+|------|----------|----------|----------|----------|----------|
+| 1 | 区域公司结构管理 | 主从维护页 | 区域公司列表、公司列表、公司编辑弹窗 | 新增公司、编辑公司、删除公司、查看下属公司 | 无 |
+| 2 | 矿权项目维护 | 列表维护页 | 项目列表、项目编辑弹窗 | 新增项目、编辑项目、删除项目、查看矿权 | 查看矿权 -> 矿权信息维护 |
+| 3 | 矿权信息维护 | 列表维护页 | 筛选区、矿权列表、合计行、矿权编辑弹窗、附件弹窗 | 新增矿权、编辑矿权、删除矿权、上传附件、查看附件 | 附件管理 -> 项目资料上传；任务管理 -> 矿权任务管理 |
+
+### 共享数据/枚举
+| 数据名称 | 字段 | 说明 |
+|----------|------|------|
+| 区域公司 | regionName | 固定6个：BLUE HILLS、KOOLANOOKA、ROBINSON RANGE、JACK HILLS、WELD RANGE、CROSSLANDS |
+| 公司 | companyName, regionName | 公司隶属于区域公司 |
+| 项目 | projectName, projectCode, regionName, companyName | 项目隶属于公司 |
+
+### 页面间导航关系
+首页/工作台
+  ├── 矿权项目维护
+  │     └── 矿权信息维护（项目详情页跳转）
+  │           └── 项目资料上传（附件管理）
+  │           └── 矿权任务管理（任务管理）
+  └── 矿权信息综合查询
+        └── 矿权详情（查询结果跳转）
+```

package/skills/brms-vxe-plus-developer/SKILL.md

@@ -0,0 +1,105 @@
+---
+name: brms-vxe-plus-developer
+description: Real BRMS project/* Vue development with VxePlusForm, VxePlusTable, EiInfo, and local business examples. Use when Codex/Claude needs to implement or modify real BRMS pages under project/*/src/views, convert prototype pages into production-style views, wire explicit backend EiInfo service methods, review VxePlus usage, fix VxePlusForm/VxePlusTable bugs, or help new developers use AI for BRMS real development.
+---
+
+# BRMS VxePlus Developer
+
+Use this skill for real development in a confirmed `project/*/src/views` application, not mock-first prototype generation.
+
+This skill is downstream of `brms-prototype-generator`: prototypes may provide page structure and mock behavior, but this skill owns real target-project view implementation, EiInfo wiring, VxePlus usage, and delivery review.
+
+## Project Check
+
+Before writing or reviewing VxePlus code in any repo, run:
+
+```bash
+node .claude/skills/brms-vxe-plus-developer/scripts/check-project.mjs --repo-root . --format both
+```
+
+If the user already named a target project, include it:
+
+```bash
+node .claude/skills/brms-vxe-plus-developer/scripts/check-project.mjs --repo-root . --target-project project/<name> --format both
+```
+
+Stop on `Blockers`. Treat `Warnings` as local context to inspect, not automatic failure. BRMS repos may use different project names (`project/base`, `project/bmnc`, etc.), route styles, and documentation layouts.
+If the blocker says multiple project candidates were found, list the candidates and ask the user to choose the target project before editing or generating code.
+
+## Core Rule
+
+Before writing or reviewing VxePlus code, use the packaged knowledge-base entry:
+
+```text
+references/vxe-plus-knowledge/README.md
+```
+
+Then load only the needed knowledge files:
+
+- `01-mental-model.md`: page type and component split.
+- `02-vxe-plus-form.md`: `VxePlusForm`, renderers, validation, DatePicker pitfalls.
+- `03-vxe-plus-table.md`: `VxePlusTable`, columns, editable grids, toolbar buttons.
+- `04-example-map.md`: embedded code examples and offline `sources/project/base/src/views` examples.
+- `05-request-and-eiinfo.md`: EiInfo query/save/transform rules.
+- `90-anti-patterns.md`: final hard-stop checks.
+
+If the business project also has `doc/components/vxe-plus-knowledge`, use it as a project-local supplement. If it is missing, use local docs such as `doc/vibeCoding/README.md`, `libs/components/src`, and neighboring pages under the confirmed `project/*/src/views` as supplement.
+
+Do not load every source example by default. Search within the confirmed project's `src/views`, plus packaged examples under `references/vxe-plus-knowledge/sources/project/*/src/views`, by page pattern, component name, service name, renderer name, or business module.
+
+## Workflow
+
+1. Classify the task:
+   - new real project page;
+   - modify existing project page;
+   - convert prototype to real project page;
+   - wire backend EiInfo interfaces;
+   - fix VxePlus behavior;
+   - review generated or newcomer code.
+
+2. Read the corresponding reference:
+   - resource selection: `references/resource-index.md`;
+   - real project implementation: `references/real-base-development.md`;
+   - prototype-to-real migration: `references/prototype-to-real.md`;
+   - review or handoff checks: `references/review-checklist.md`.
+
+3. Inspect local code before editing:
+   - target file or planned target path under the confirmed `project/*/src/views`;
+   - neighboring pages in the same module;
+   - relevant embedded examples under `references/vxe-plus-knowledge/sources/project/*/src/views` when present;
+   - relevant component source under `libs/components/src` when docs are missing or unclear;
+   - explicit service/method/interface notes from the user or product document.
+
+4. Implement conservatively:
+   - follow local module style;
+   - prefer direct `itemRender` / `editRender` component contracts for new files;
+   - do not introduce new `useForm` helper layers;
+   - keep mock logic only when the user explicitly asks for mock behavior;
+   - use real `EiCommunicator.send` only when service and method names are explicit.
+
+5. Validate:
+   - run `node .claude/skills/brms-vxe-plus-developer/scripts/check-vxe-plus-page.mjs <files> --repo-root .` for modified Vue/TS files;
+   - run the narrowest available type/lint command if practical;
+   - report anything not run.
+
+## Hard Rules
+
+- `VxePlusForm` uses `:form-options`, never `:form-config`.
+- `VxePlusForm` required validation must live in form-level `rules`, for example `rules: { portCode: [{ required: true, message: '请输入港口代码' }] }`.
+- Do not use `titlePrefix: { content: '必填' }` as validation; it only decorates the title.
+- Do not put `required: true` on `formOptions.items`; item-level `required` is ineffective in this wrapper.
+- `VxePlusTable` query config uses `:form-config`.
+- Dialog forms also use `VxePlusForm :form-options`.
+- New generated real pages should not import `useForm()` solely to get helper renderers.
+- `VxeDatePicker type="month"` must not use `valueFormat: 'MM'`; use `valueFormat: 'yyyy-MM'` plus `labelFormat: 'MM'`.
+- Table actions belong in `toolbarButtons` / `toolbarButtonClick` unless the existing page has a clear different pattern.
+- Do not add operation/action columns by default.
+- Do not generate REST `http.*` calls when the interface is EiInfo.
+- Do not add compatibility code for old data unless explicitly requested.
+- For attachment upload/view, use the shared project flow such as `useFileUpload().openFileBFSS0001` when available.
+
+## Relationship To Prototype Skill
+
+Use `brms-prototype-generator` when the task is to create mock-first prototype pages from product Markdown.
+
+Use this skill when the task is to make real `project/*` development deliverable: connect interfaces, align with existing views code, fix component usage, or prepare newcomer handoff-ready code.

package/skills/brms-vxe-plus-developer/agents/openai.yaml

@@ -0,0 +1,7 @@
+interface:
+  display_name: "BRMS VxePlus Developer"
+  short_description: "Develop real BRMS project views with VxePlus and EiInfo"
+  default_prompt: "Use $brms-vxe-plus-developer to check the BRMS project shape, then turn requirements or prototype pages into real project/* Vue pages using VxePlusForm, VxePlusTable, EiInfo requests, and local examples."
+
+policy:
+  allow_implicit_invocation: true

package/skills/brms-vxe-plus-developer/references/prototype-to-real.md

@@ -0,0 +1,54 @@
+# Prototype To Real BRMS Page
+
+Use this reference when converting pages generated by `brms-prototype-generator` into real code under the confirmed `project/*`.
+
+## Conversion Order
+
+1. Read the prototype page and generation summary, if available.
+2. Identify mock markers:
+   - `@brms-mock-data`
+   - `@brms-mock-handler`
+   - TODO backend toasts
+3. Read product/interface notes for explicit service and method names.
+4. Select similar real examples from `references/vxe-plus-knowledge/sources/project/base/src/views`.
+5. Replace mock-only behavior with real `serviceConfig`, `transformParams`, `transformResponse`, or explicit `EiInfo`.
+6. Keep undocumented interactions local/mock only if the user asks for staged delivery.
+7. Run the skill checker and any practical type/lint command.
+
+## What To Preserve
+
+- Page intent, query fields, result fields, toolbar actions, dialogs, navigation edges.
+- Existing route/query contracts from the prototype when they match the desired real workflow.
+- Clear mock markers until the corresponding behavior is truly wired.
+
+## What To Replace
+
+- Local mock query arrays once `serviceName.queryMethod` is explicit.
+- Local save/delete handlers once corresponding service methods are explicit.
+- Prototype-only layout or placeholder components that do not exist in the confirmed target project.
+- Any generated dialog form using `:form-config`; real `VxePlusForm` uses `:form-options`.
+
+## Request Wiring Rules
+
+Use `VxePlusTable :service-config` for table queries when the backend returns a table block matching the table `id`.
+
+Use explicit `EiCommunicator.send` for actions that are not a simple table query:
+
+- confirm/submit/approve;
+- batch delete with custom block names;
+- save mixed master-detail data;
+- export/queryExport;
+- attachment operations.
+
+Do not infer method names. If the prototype or product document says only "save" generically and does not name a service/method, ask or keep a marked TODO.
+
+## Handoff To New Developers
+
+When finishing a prototype-to-real conversion, report:
+
+- files changed;
+- services/methods wired;
+- mock markers removed or remaining;
+- VxePlus knowledge-base examples used;
+- validation command output;
+- follow-up interface questions.

package/skills/brms-vxe-plus-developer/references/real-base-development.md

@@ -0,0 +1,110 @@
+# Real BRMS Project Development Workflow
+
+Use this reference for real development under the user-confirmed `project/*/src/views`.
+
+## Inputs To Collect
+
+- Target project plus page code and path, for example `project/bmnc` and `BMBR01 -> project/bmnc/src/views/BM/BR/BMBR01.vue`.
+- Whether this is a new page, existing page change, or prototype conversion.
+- Backend service names and method names, if real interface wiring is required.
+- Neighboring module examples and any similar page code.
+
+## Page Discovery
+
+For a page code with 6+ characters:
+
+```text
+KCKZ01 -> project/<name>/src/views/KC/KZ/KCKZ01.vue
+A1P101 -> project/<name>/src/views/A1/P1/A1P101.vue
+```
+
+Replace `project/<name>` with the confirmed target project, such as `project/bmnc`.
+
+Before editing, inspect:
+
+- the target file if it exists;
+- sibling pages in the same folder;
+- same module `component/<PAGE_CODE>/formConfig.ts` or `columns.ts` if present;
+- relevant packaged examples in `references/vxe-plus-knowledge/sources/project/base/src/views`.
+
+## Implementation Defaults
+
+- New simple query pages use a query `BxContainer + VxePlusForm` and a result `BxContainer + VxePlusTable`.
+- Query and reset live in the query container.
+- Table add/save/delete live in `VxePlusTable :toolbar-buttons`.
+- Use direct renderer configs in new code:
+
+```ts
+{ field: 'name', title: '名称', itemRender: { name: 'VxeInput' } }
+{ field: 'status', title: '状态', itemRender: { name: 'formSelect', props: { codeSet: 'xxx' } } }
+{ field: 'name', title: '名称', editRender: { name: 'VxeInput' } }
+```
+
+Do not create a new helper wrapper around renderers.
+
+## Existing Helper Policy
+
+Many old pages use `useForm()` / `useTable()` helpers. Treat them as historical code vocabulary:
+
+- Editing a file that already uses helpers: local consistency is acceptable.
+- Creating a new file or large new block: prefer direct `itemRender` / `editRender` contracts from `references/vxe-plus-knowledge`.
+- Do not refactor existing helper-heavy pages just to remove helpers unless the user asks.
+
+## EiInfo Requests
+
+Read `references/vxe-plus-knowledge/05-request-and-eiinfo.md` before wiring requests.
+
+Use `serviceConfig` for ordinary table query:
+
+```ts
+const tableFormConfig = reactive({
+  id: 'inqu_status',
+  data: formData,
+})
+
+const serviceConfig = reactive({
+  serviceName: 'SERVICE01',
+  queryMethod: 'query',
+})
+```
+
+Use `transformParams(formEi)` to add attrs, blocks, or special fields without discarding default form/paging/sort params.
+
+Use explicit `EiInfo` construction for complex save/confirm/delete:
+
+```ts
+const ei = new EiInfo()
+ei.addBlock(EiBlock.build('result', rows))
+ei.addBlock(EiBlock.build('inqu', [formData]))
+await EiCommunicator.send('SERVICE01', 'save', ei)
+```
+
+## Business Example Selection
+
+Use the offline examples under:
+
+```text
+references/vxe-plus-knowledge/sources/project/base/src/views
+```
+
+Start from:
+
+- `BM/BR/BMBR01.vue` for standard query pages.
+- `SM/SW/SMSW0101.vue` for direct renderer configs, `transformParams`, and selected-row submit.
+- `A1/P0/A1P01601.vue` for editable table patterns.
+- `AM/AF/component/AMAF0601` for dialog selection and complex form/table configs.
+- `PM/PC/component/PMPC0101` only for real complex detail pages.
+
+## DatePicker Guard
+
+For month pickers:
+
+```ts
+// bad
+{ type: 'month', valueFormat: 'MM' }
+
+// good
+{ type: 'month', valueFormat: 'yyyy-MM', labelFormat: 'MM' }
+```
+
+Reason: pure month strings cannot be parsed back into valid Date values by `xe-utils`.

package/skills/brms-vxe-plus-developer/references/resource-index.md

@@ -0,0 +1,43 @@
+# Resource Index
+
+Load only the reference needed for the current task.
+
+## Always Start Here
+
+- `references/vxe-plus-knowledge/README.md`: packaged entrypoint for VxePlusForm, VxePlusTable, EiInfo, examples, and anti-patterns.
+- `doc/components/vxe-plus-knowledge/README.md`: optional project-local supplement when the business project has one.
+
+## Skill References
+
+- `real-base-development.md`: use for new real pages, modifying existing `project/*/src/views`, or wiring explicit backend methods.
+- `prototype-to-real.md`: use when the input is a mock prototype page or output from `brms-prototype-generator`.
+- `review-checklist.md`: use for code review, newcomer handoff, and final delivery checks.
+
+## Knowledge Base Files
+
+- `references/vxe-plus-knowledge/01-mental-model.md`: page shape and component responsibility.
+- `references/vxe-plus-knowledge/02-vxe-plus-form.md`: form renderers, validation, select dialogs, DatePicker traps.
+- `references/vxe-plus-knowledge/03-vxe-plus-table.md`: table columns, edit mode, toolbar buttons, slots.
+- `references/vxe-plus-knowledge/04-example-map.md`: embedded examples for direct copying and adaptation.
+- `references/vxe-plus-knowledge/05-request-and-eiinfo.md`: EiInfo query/save/transform behavior.
+- `references/vxe-plus-knowledge/90-anti-patterns.md`: hard-stop mistakes.
+
+## Offline Source Examples
+
+Search under:
+
+```text
+references/vxe-plus-knowledge/sources/project/base/src/views
+```
+
+Use focused search terms:
+
+- `VxePlusForm`
+- `VxePlusTable`
+- `formSelectDialog`
+- `tableSelectDialog`
+- `transformParams`
+- `transformResponse`
+- `toolbarButtonClick`
+- `EiCommunicator.send`
+- `valueFormat`

package/skills/brms-vxe-plus-developer/references/review-checklist.md

@@ -0,0 +1,49 @@
+# Review Checklist
+
+Use this reference before handing real BRMS VxePlus code to a newcomer or reviewer.
+
+## Form Checks
+
+- `VxePlusForm` uses `:form-options`.
+- Dialog forms also use `:form-options`.
+- Form config has `id`, `data`, and `items`.
+- Required validation is defined in `formOptions.rules`, keyed by field.
+- Form items do not use `required: true` or `titlePrefix: { content: '必填' }` as validation.
+- New code does not introduce another `useForm()` helper layer.
+- `fields` / `dialogFields` are one-to-one for `formSelectDialog`.
+- `VxeDatePicker type="month"` does not use `valueFormat: 'MM'`.
+
+## Table Checks
+
+- `VxePlusTable` has a meaningful `id`, usually `<PAGE>_result`.
+- `:form-config` points to query form data.
+- `serviceConfig` is used only when service/method names are real.
+- Editable table uses `:is-edit="true"` and `editRules` where needed.
+- Dialog edit and row edit are not mixed accidentally.
+- Add/save/delete buttons are in `toolbarButtons` unless local code clearly uses another pattern.
+- No default operation/action column was generated without a concrete reason.
+- Checkbox selection is controlled by `:show-checkbox`, not a generated checkbox column.
+
+## Request Checks
+
+- `transformParams(formEi)` mutates or augments the incoming EiInfo and returns it.
+- `transformParams` does not create a new empty EiInfo unless intentionally discarding defaults.
+- `transformResponse(rows)` expects mapped rows, not a full EiInfo, under the normal `serviceConfig` path.
+- Complex save/confirm/delete builds explicit `EiInfo` blocks matching the backend contract.
+- No speculative old-data compatibility was added.
+
+## Example And Knowledge Checks
+
+- The implementation can point to a nearby real `project/*/src/views` example or a packaged offline source under `references/vxe-plus-knowledge/sources/project/base/src/views`.
+- Any deviation from the knowledge-base pattern is explained by local module code or interface contract.
+- Known anti-patterns from `references/vxe-plus-knowledge/90-anti-patterns.md` were checked.
+
+## Validation Checks
+
+Run:
+
+```bash
+node .claude/skills/brms-vxe-plus-developer/scripts/check-vxe-plus-page.mjs <changed-files> --repo-root .
+```
+
+Then run the narrowest available project validation, such as typecheck or lint for the affected package. If not run, say why.