@brms/ai-skills 0.1.0

package/skills/brms-prototype-generator/SKILL.md

@@ -0,0 +1,129 @@
+---
+name: brms-prototype-generator
+description: Generate BRMS/eplat-vue-base Vue prototype pages from product Markdown into a confirmed project under project/*. Use when users mention function.md, requirements.md, product docs, page packages, prototype Vue pages, mock-first BRMS UI, explicit EiInfo interfaces, route/menu handoff, or this repo's Codex/Claude skill workflow.
+---
+
+# BRMS Prototype Generator
+
+Use this skill as a coordinator, not as a full prompt dump. Keep `SKILL.md` loaded, then read only the referenced resource files needed for the current page type.
+
+## Safety
+
+- Before executing the workflow in any repo, run the project check:
+
+```bash
+node .claude/skills/brms-prototype-generator/scripts/check-project.mjs --repo-root . --format both
+```
+
+If the user already named a target project, include it:
+
+```bash
+node .claude/skills/brms-prototype-generator/scripts/check-project.mjs --repo-root . --target-project project/<name> --format both
+```
+
+Stop only on `Blockers`. Treat `Warnings` as planning notes, because BRMS projects may differ by route/menu style or documentation completeness.
+If the blocker says multiple project candidates were found, list the candidates and ask the user to choose the target project before generating code.
+- Work only in the user-confirmed target project under `project/*`.
+- Do not install, update, remove, or repair dependencies.
+- Do not delete or recreate `node_modules`, `.pnpm`, lockfiles, or pnpm stores.
+- Use Node `18.17.0` and pnpm `8.10.4`; stop if the active versions differ.
+- Do not edit route/menu files until the target route style is known. If the target uses `src/routers/localMenuList.json` or permission-center dynamic routes, plan route/menu handoff instead of inventing `routers/config`.
+- Default to mock-backed prototypes. Use real EiInfo/serviceConfig wiring only when the product document explicitly names service and method names.
+
+## Required Flow
+
+1. Discover candidate target projects:
+
+```bash
+node .claude/skills/brms-prototype-generator/scripts/discover-targets.mjs --repo-root . --format both
+```
+
+Ask the user to confirm the target, even when only one candidate is found.
+If multiple candidates are found, stop here until the user chooses the exact `project/<name>`.
+If the discovery reports `local-menu` or `dynamic-router`, do not assume the old static route config layout; inspect the reported route file and use it only when the user confirms local menu edits.
+
+2. Analyze the product Markdown:
+
+```bash
+node .claude/skills/brms-prototype-generator/scripts/analyze-doc.mjs <entry-md> --repo-root . --format both
+```
+
+Stop if `summary.completePages` is `0`. If field keys are missing, ask whether to supplement table design; if the user declines, derive lowerCamelCase keys and add TODO comments.
+
+3. For 4+ complete pages, create a compact generation plan before writing Vue:
+
+```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>` must be the real 4+ character page prefix, for example `DMDA` -> `DMDA01`. Do not use a 2-character module prefix such as `KQ` because it produces invalid short page codes like `KQ01`.
+
+Use the plan's page packets as the source of truth. Do not keep rereading the full product document for every page.
+
+4. Pick the generation mode:
+
+- `single-agent-package`: 1-3 complete pages.
+- `coordinator-subagents`: 4+ complete pages when subagents are available.
+- `coordinator-sequential`: 4+ complete pages when subagents are unavailable.
+
+For multi-page work, the coordinator owns the plan, shared `data.ts`, route config, final validation, and handoff summary. A worker may edit only its assigned page file.
+
+## Lazy Resource Loading
+
+Read [resource-index.md](references/resource-index.md) after analysis. It tells you which detailed reference files to load for each page type and rule family.
+
+Do not load all references or all examples by default. Load only:
+
+- the page pattern file named by the page packet;
+- `references/04-composite-page-package.md` for 4+ page packages;
+- `references/05-dialog-patterns.md` only when dialogs, drawers, upload, or attachment behavior is present;
+- `references/06-backend-request-patterns.md` only when explicit backend service and method names are present;
+- `examples/few-shot-examples.md` only when a concrete snippet is needed, and search within it instead of reading it all.
+
+Treat `references/system-prompt.md` as a legacy full prompt for external/manual use. Do not load it during normal skill execution.
+
+## Hard Gates
+
+- Every generated `.vue` template has exactly one top-level root element.
+- Generated dialogs stay inside the same root wrapper as page content.
+- Mock-backed `VxePlusTable` with `:columns` must bind `:data`.
+- Interface-backed pages must include `// @brms-explicit-interface <source>: <Service.method>`.
+- Mock-backed data and local mock logic must be searchable for later cleanup: put `// @brms-mock-data <source-or-page>: <purpose>` before mock arrays/objects/row refs, and `// @brms-mock-handler <source-or-page>: <operation>` before local query/save/delete/upload/status handlers. A plain `TODO: 接入后台接口` is not enough.
+- Do not generate REST `http.*` calls unless the product doc explicitly asks for REST.
+- Do not generate operation/action columns or checkbox columns in `createColumns`; use table toolbar buttons and `:show-checkbox`.
+- Page codes must be 6+ uppercase letters/digits; the first 2 characters are the module folder and the next 2 are the submodule folder, for example `DMDA01` -> `src/views/DM/DA/DMDA01.vue`.
+- Do not generate short page codes such as `KQ01`; ask for or derive a 4+ character page prefix first.
+- Dynamic route config `path` uses only `/<PAGE_CODE>` because `auth.ts` prefixes `/web`; keep physical folders only in `component`.
+- Hidden detail/jump-only pages in a page package stay in the same parent menu `children` with `meta.isHide: true`; do not put them as separate top-level routes outside the parent array item.
+- In-page navigation uses `/web/<PAGE_CODE>`, for example `/web/DMDA01`, not `/web/DM/DA/DMDA01`.
+- Every documented cross-page navigation edge must have both sides wired: a visible source UI entry that calls `router.push` with `query`, and a target page that reads `route.query` as default filter or context.
+- Generated add/edit/delete actions belong in `VxePlusTable :toolbar-buttons`, not in result-header `BxContainer :custom-btn-list`, to avoid duplicate buttons.
+- Choose exactly one edit model per table: row edit uses `VxePlusTable :is-edit="true"` plus column `editRender`; dialog edit uses `vxe-modal + VxePlusForm` and must not enable table row edit. Do not use `cell-click` as a default edit opener.
+- `vxe-modal show-footer` must explicitly set `show-cancel-button`, `show-confirm-button`, `cancel-button-text`, and `confirm-button-text`.
+- Do not invent components such as `VxePlusDialog`, `FileUploadDialog`, `UploadDialog`, `BxUploadDialog`, or `AttachmentDialog`.
+- Dialog `VxePlusForm` uses `:form-options`, not `:form-config`.
+- Required validation for `VxePlusForm` must be written in form-level `rules`, for example `rules: { portCode: [{ required: true, message: '请输入港口代码' }] }`.
+- Do not use `titlePrefix: { content: '必填' }` as validation. It only decorates the title and does not validate input.
+- Do not put `required: true` on `formOption.items`; item-level `required` is ineffective in this VxePlusForm wrapper.
+- Attachment upload/view actions use `useFileUpload().openFileBFSS0001` when available.
+
+Keep the details for these gates in references and `validate-generated.mjs`; do not expand them in chat unless fixing a failure.
+
+## Validation
+
+Validate only generated or modified files, not the whole `src/views` tree:
+
+```bash
+node .claude/skills/brms-prototype-generator/scripts/validate-generated.mjs <generated-vue-or-route-files> --repo-root .
+pnpm --filter <target-package-name> exec vue-tsc --noEmit --pretty false
+```
+
+If `vue-tsc` is not available through the target package, report that instead of changing dependencies.
+
+For 4+ page packages, write a compact handoff summary:
+
+```text
+<target-project>/.generation-summaries/<lowercase-page-prefix>-<yyyymmddhhmmss>.md
+```
+
+Include entry doc, confirmed target, generation plan path/output, generated files, route/menu handoff, per-page functions, validation output, and unresolved TODOs. Tell Claude Code users they may run `/compact` after the summary is written.

package/skills/brms-prototype-generator/agents/openai.yaml

@@ -0,0 +1,7 @@
+interface:
+  display_name: "BRMS Prototype Generator"
+  short_description: "Plan and generate BRMS prototypes with compact page packets"
+  default_prompt: "Use $brms-prototype-generator to discover the target BRMS project, analyze the product Markdown, create a compact page plan for multi-page work, and generate only the confirmed BRMS prototype pages."
+
+policy:
+  allow_implicit_invocation: true