@mingfuyun/star-allinone 0.2.0 → 0.3.1

package/scripts/gen/ts.js

@@ -0,0 +1,121 @@
+const { deref, refName, pointerValue } = require('./spec');
+
+function isNullable(schema) {
+  if (!schema) return false;
+  if (schema.nullable) return true;
+  if (Array.isArray(schema.type) && schema.type.includes('null')) return true;
+  return false;
+}
+
+function withNull(type, schema) {
+  if (!isNullable(schema) || type.includes('| null')) return type;
+  return `${type} | null`;
+}
+
+function collectRefs(spec, schema, bag = new Set(), seen = new Set()) {
+  if (!schema) return bag;
+  if (schema.$ref) {
+    if (seen.has(schema.$ref)) return bag;
+    seen.add(schema.$ref);
+    bag.add(schema.$ref);
+    collectRefs(spec, deref(spec, schema), bag, seen);
+    return bag;
+  }
+  const nested = [
+    schema.items,
+    ...(schema.allOf || []),
+    ...(schema.oneOf || []),
+    ...(schema.anyOf || []),
+    ...Object.values(schema.properties || {}),
+    schema.additionalProperties && typeof schema.additionalProperties === 'object'
+      ? schema.additionalProperties
+      : null,
+  ].filter(Boolean);
+  nested.forEach((item) => collectRefs(spec, item, bag, seen));
+  return bag;
+}
+
+function schemaToTs(spec, schema, namedRefs = new Map()) {
+  if (!schema) return 'unknown';
+  if (schema.$ref) {
+    if (namedRefs.has(schema.$ref)) return namedRefs.get(schema.$ref);
+    return refName(schema.$ref) || 'unknown';
+  }
+  if (schema.enum?.length) {
+    return withNull(schema.enum.map((value) => JSON.stringify(value)).join(' | '), schema);
+  }
+  if (schema.oneOf?.length) {
+    return withNull(
+      schema.oneOf.map((item) => schemaToTs(spec, item, namedRefs)).join(' | '),
+      schema,
+    );
+  }
+  if (schema.anyOf?.length) {
+    return withNull(
+      schema.anyOf.map((item) => schemaToTs(spec, item, namedRefs)).join(' | '),
+      schema,
+    );
+  }
+  if (schema.allOf?.length) {
+    const merged = deref(spec, schema);
+    return schemaToTs(spec, { ...merged, allOf: undefined }, namedRefs);
+  }
+  const types = Array.isArray(schema.type) ? schema.type.filter((item) => item !== 'null') : [schema.type];
+  const type = types[0];
+  if (type === 'array' || schema.items) {
+    return withNull(`${schemaToTs(spec, schema.items, namedRefs)}[]`, schema);
+  }
+  if (type === 'integer' || type === 'number') return withNull('number', schema);
+  if (type === 'boolean') return withNull('boolean', schema);
+  if (type === 'string') return withNull('string', schema);
+  if (type === 'object' || schema.properties || schema.additionalProperties) {
+    const properties = schema.properties || {};
+    const required = new Set(schema.required || []);
+    const lines = Object.entries(properties).map(([key, value]) => {
+      const optional = required.has(key) ? '' : '?';
+      return `    ${key}${optional}: ${schemaToTs(spec, value, namedRefs)};`;
+    });
+    if (!lines.length && schema.additionalProperties) {
+      const valueType =
+        schema.additionalProperties === true
+          ? 'unknown'
+          : schemaToTs(spec, schema.additionalProperties, namedRefs);
+      return withNull(`Record<string, ${valueType}>`, schema);
+    }
+    if (!lines.length) return withNull('Record<string, unknown>', schema);
+    return `{\n${lines.join('\n')}\n  }`;
+  }
+  return withNull('unknown', schema);
+}
+
+function emitNamedType(spec, name, schema, namedRefs) {
+  const resolved = schema?.$ref ? pointerValue(spec, schema.$ref) : schema;
+  if (!resolved) return `  type ${name} = unknown;`;
+  if (resolved.enum?.length) {
+    return `  type ${name} = ${schemaToTs(spec, resolved, namedRefs)};`;
+  }
+  const body = schemaToTs(spec, { ...resolved, $ref: undefined }, namedRefs);
+  return `  type ${name} = ${body};`;
+}
+
+function emitQueryType(spec, name, params, namedRefs) {
+  if (!params.length) return null;
+  const required = new Set(params.filter((param) => param.required).map((param) => param.name));
+  const lines = params.map((param) => {
+    const optional = required.has(param.name) ? '' : '?';
+    return `    ${param.name}${optional}: ${schemaToTs(spec, param.schema, namedRefs)};`;
+  });
+  return `  type ${name} = {\n${lines.join('\n')}\n  };`;
+}
+
+function paramType(spec, param, namedRefs) {
+  return schemaToTs(spec, param.schema, namedRefs);
+}
+
+module.exports = {
+  collectRefs,
+  schemaToTs,
+  emitNamedType,
+  emitQueryType,
+  paramType,
+};

package/skills/README.md

@@ -6,76 +6,51 @@
 
 ## 推荐目录
 
-以 `starscope-frontend` 为例：
-
 ```text
-starscope-frontend/
+business-app/
+├── AGENTS.md
 ├── .star-allinone.json
 └── .agents/
     ├── skills/
     │   ├── shared-api-to-service/
-    │   ├── shared-api-mock/
     │   ├── shared-design-to-page/
-    │   ├── shared-verify/
     │   ├── shared-review-and-submit/
     │   ├── shared-publish-test/
-    │   └── custom-device-management/
+    │   ├── shared-project-conventions/   ← 无 SKILL.md，给入口读
+    │   ├── shared-i-have-adhd/           ← 无 SKILL.md，给入口读
+    │   └── custom-*                      ← 仅真正的业务特例
     └── project/
         ├── conventions.md
         ├── review-rules.md
         └── openapi.json
 ```
 
-StarLink：
-
-```text
-starlink-frontend/
-└── .agents/
-    └── skills/
-        ├── shared-api-to-service/
-        ├── shared-api-mock/
-        ├── shared-design-to-page/
-        ├── shared-verify/
-        ├── shared-review-and-submit/
-        ├── shared-publish-test/
-        └── custom-node-management/
-```
-
 命名约定：
 
 ```text
-shared-*   公共 skill，由 star-allinone 提供，经 CLI 同步后提交到业务仓库
-custom-*   业务定制 skill，由业务项目维护
+shared-*   公共内容，由 star-allinone 提供，经 CLI 同步后提交到业务仓库
+custom-*   业务定制，由业务项目维护；禁止做成第二套页面/审查/单接口生成入口
 ```
 
-这样所有 skill 都在业务项目中，Codex 可以直接发现；同时通过名称可以清楚区分来源。
+Cursor / Codex 的常驻说明只放仓库根 `AGENTS.md`（模板见 `examples/AGENTS.md`）。项目差异放 `.agents/project/`。不要新增 `.cursor/rules`。
 
 ## npm 包的职责
 
-`@mingfuyun/star-allinone` 包中保存公共 skill 源文件。每个 skill 包含可执行规则，细节放在同目录 `references/`：
+`@mingfuyun/star-allinone` 只发布 **4 个用户入口**。其余是入口的 `references/` 或无 `SKILL.md` 的共享文件：
 
 ```text
 @mingfuyun/star-allinone/
 └── skills/
     └── shared/
-        ├── api-to-service/
-        │   ├── SKILL.md
-        │   └── references/
-        │       ├── service-conventions.md
-        │       └── api-artifact-generation.md
-        ├── api-mock/
-        ├── design-to-page/          # page-conventions.md + overlays.md
+        ├── api-to-service/          # 单接口；mock 规则在 references/
+        ├── design-to-page/          # 页面；标准列表内部跑 gen page
+        ├── review-and-submit/       # 审查并提交；步骤在 references/
+        ├── publish-test/            # 测发
         ├── project-conventions/     # architecture / review-checklist / quality-checklist
-        ├── verify/
-        ├── review-and-submit/
-        ├── impact-analysis/
-        ├── ai-review/
-        ├── commit-current-changes/
-        ├── i-have-adhd/               # 同步为 shared-i-have-adhd；其他 shared skill 的用户输出格式
-        └── publish-test/              # 流水线 ID 从 .star-allinone.json 读取
+        └── i-have-adhd/             # 用户输出格式
 ```
 
-公共 skill 写死两边已对齐的硬规则，例如：页面走 `MFRequest`、DTO 放 namespace typings、`MFProTable` + `ProForm`、弹层用 `BaseModal` / `CustomDrawer` / `HocModal`、`await` 必须 try/catch、禁止无说明的 `any`。
+公共入口写死两边已对齐的硬规则，例如：页面走 `MFRequest`、DTO 放 namespace typings、`MFProTable` + `ProForm`、弹层用 `BaseModal` / `CustomDrawer` / `HocModal`、`await` 必须 try/catch、禁止无说明的 `any`。
 
 业务项目的 `.agents/project/` 只写差异：路径、权限体系、OpenAPI 位置、领域特例。项目文件可以补充，但不能削弱公共硬规则。
 
@@ -87,13 +62,7 @@ npm 包中的 skills/shared
 业务项目 .agents/skills/shared-*
 ```
 
-不会写入：
-
-```text
-~/.codex/skills
-```
-
-也不会管理业务项目的 `custom-*` skill。
+不会写入 `~/.codex/skills`，也不会管理业务项目的 `custom-*`。`skills list` 只列出带 `SKILL.md` 的入口。无 `SKILL.md` 的目录仍会同步，供入口阅读。
 
 ## CLI 使用方式
 
@@ -103,40 +72,11 @@ npm 包中的 skills/shared
 pnpm exec star-allinone skills sync
 ```
 
-CLI 根据当前业务项目的 `.star-allinone.json`，直接将公共 skill 写入当前项目：
-
-```text
-当前项目/.agents/skills/shared-*/
-```
-
-例如：
-
-```bash
-cd /path/to/starscope-frontend
-pnpm exec star-allinone skills sync
-```
-
-结果：
-
-```text
-.agents/skills/
-├── shared-api-to-service/
-├── shared-api-mock/
-├── shared-review-and-submit/
-├── shared-publish-test/
-└── custom-*/
-```
-
-公共 skill 的更新不会影响业务定制 skill。同步会整体替换 `shared-*` 目录，并删除包中已不存在的过期 `shared-*`，但不会改动 `custom-*`。
+同步会整体替换 `shared-*` 目录，并删除包中已不存在的过期 `shared-*`，但不会改动 `custom-*`。
 
 ## 新增或修改公共 skill
 
-管理者操作：
-
-```text
-修改 star-allinone/skills/shared/api-to-service/SKILL.md
-→ 发布新版本 @mingfuyun/star-allinone
-```
+管理者操作：修改 `star-allinone/skills/shared/<entry>/SKILL.md` → 发布新版本。
 
 业务项目操作：
 
@@ -147,82 +87,20 @@ git add package.json pnpm-lock.yaml .agents/skills/shared-*
 git commit -m "chore(skill): 更新公共 skill"
 ```
 
-团队成员只需要：
+团队成员只需要 `git pull` 和 `pnpm install`。不要手动修改 `shared-*`。
 
-```bash
-git pull
-pnpm install
-```
+## 新增或修改业务定制
 
-由于公共 skill 已经提交到业务仓库，所以团队成员不需要手动安装全局 skill，也不需要拥有 `star-allinone` 源码。
-
-## 新增或修改业务定制 skill
-
-业务项目直接维护：
-
-```text
-.agents/skills/custom-device-management/SKILL.md
-```
-
-提交即可：
-
-```bash
-git add .agents/skills/custom-device-management
-git commit -m "feat(skill): 增加设备管理 skill"
-```
+`custom-*` 只用于真正的业务特例：领域不变量、全量契约脚本、度量。审查、提交、测发、单接口、页面生成都走公共入口。
 
-不需要修改 `star-allinone`，也不需要重新发布 npm。
-
-审查、提交、测试环境发布、Mock 和 Service 生成都走公共 skill。只有流水线 ID 放在业务项目的 `.star-allinone.json`。`custom-*` 只用于真正的业务特例，例如设备管理或节点管理。
+全量契约重建若必须留在 custom：加上 `disable-model-invocation: true`，在 `AGENTS.md` 写清要跑的命令，不要作为用户入口。度量类 custom 不得生成代码。
 
 ## 公共部分和业务定制组合
 
-例如业务定制 skill 需要复用公共 API 生成流程：
-
-```text
-.agents/skills/custom-device-service/SKILL.md
-```
-
-内容中引用公共 skill：
-
-```md
----
-name: custom-device-service
-description: Generate StarScope device service code.
----
-
-本任务需要结合公共 skill `shared-api-to-service` 执行。
-
-先读取并遵循：
-
-`.agents/skills/shared-api-to-service/SKILL.md`
-
-再读取当前项目的：
-
-- OpenAPI 文件
-- Service 约定
-- 项目类型和权限规则
-
-只生成符合当前项目结构的设备相关 service。
-```
-
-公共 skill 负责通用流程，业务 skill 负责具体业务规则。
+业务定制需要复用公共流程时，在 `custom-*` 里 **读取** 对应入口的 `SKILL.md`，不要再做一个可 `$` 调用的生成入口。领域规则示例见 `examples/skills/custom-domain-invariants/`。
 
 ## 项目配置
 
-项目差异配置放在业务项目中，例如：
-
-```text
-starscope-frontend/
-├── .star-allinone.json
-└── .agents/
-    ├── skills/
-    └── project/
-        ├── conventions.md
-        ├── review-rules.md
-        └── openapi.json
-```
-
 ```json
 {
   "project": "starscope-frontend",
@@ -233,66 +111,45 @@ starscope-frontend/
 }
 ```
 
-StarLink 使用：
+完整示例见 `examples/projects/`。可选字段 `sharedSkills` 只限制用户入口；`project-conventions` 和 `i-have-adhd` 仍会同步。
 
-```json
-{
-  "project": "starlink-frontend",
-  "publicSkillPrefix": "shared-",
-  "publishPipelineId": "5245265"
-}
-```
+## 用户入口
 
-完整示例见 `examples/projects/`。
+对话里只点这些：
 
-可选字段 `sharedSkills` 用于只同步部分公共 skill；省略时同步 `skills/shared` 下的全部公共 skill。
+| 入口 | 用途 |
+| --- | --- |
+| `shared-api-to-service` | 单个 `METHOD /path/` → 类型、`MFRequest`、默认 mock |
+| `shared-design-to-page` | 页面：标准列表内部 `gen page`，其余按设计稿实现 |
+| `shared-review-and-submit` | 审查并提交 |
+| `shared-publish-test` | 测发 |
 
 ## 公共规则写在哪里
 
-| Skill | 规则位置 | 覆盖内容 |
+| 入口 | 规则位置 | 覆盖内容 |
 | --- | --- | --- |
-| `shared-api-to-service` | SKILL + `references/service-conventions.md`、`api-artifact-generation.md` | 指定 operation、`MFRequest` 映射、namespace 类型、snake_case、schema 闭包、禁止改 transport |
-| `shared-api-mock` | SKILL + `references/mock-conventions.md` | 对话 JSON 默认、完整响应信封、分页/空列表/错误场景、禁止 handler 和随机数 |
-| `shared-design-to-page` | SKILL + `references/page-conventions.md`、`overlays.md` | 页面分层、`MFProTable`、`ProForm`、权限、异步、`HocModal` 弹层合同 |
-| `shared-project-conventions` | SKILL + `references/architecture.md`、`review-checklist.md`、`quality-checklist.md` | 架构边界、质量禁令、审查清单；其他 skill 会引用这些文件 |
-| `shared-verify` | SKILL | 成套产物检查、await/loading/弹层、验证命令和报告格式 |
-| `shared-impact-analysis` | SKILL | 只读影响分类和回归路径 |
-| `shared-ai-review` | SKILL | Hooks、契约、权限、性能、安全的 P0–P3 审查 |
-| `shared-commit-current-changes` | SKILL | 确认门禁、中文 Conventional Commit、禁止未确认就提交 |
-| `shared-review-and-submit` | SKILL | impact → verify → commit review 编排 |
-| `shared-publish-test` | SKILL + `scripts/publish-current-branch.sh` | 云效测试流水线发布；只从配置读 `publishPipelineId`；git push 后不自动跑，需单独确认「推送流水线」 |
+| `shared-api-to-service` | SKILL + `references/service-conventions.md`、`api-artifact-generation.md`、`mock.md` | 指定 operation、`MFRequest`、namespace 类型、snake_case、mock |
+| `shared-design-to-page` | SKILL + `page-conventions.md`、`overlays.md`、`list-page-template.md` | 页面分层、标准列表 CLI、弹层合同 |
+| `shared-review-and-submit` | SKILL + `impact-analysis.md`、`verify.md`、`ai-review.md`、`commit.md` | 影响分析 → 验证 → 确认后提交 |
+| `shared-publish-test` | SKILL + `scripts/publish-current-branch.sh` | 云效测发；只读 `publishPipelineId` |
+| （非入口）`shared-project-conventions` | `architecture.md`、`review-checklist.md`、`quality-checklist.md` | 架构与质量清单 |
+| （非入口）`shared-i-have-adhd` | `i-have-adhd.md` | 用户输出格式 |
 
 以下内容**不**写进公共 skill 源码：
 
-- 流水线 ID：放在业务项目 `.star-allinone.json` 的 `publishPipelineId`
-- OpenAPI 快照：业务仓库数据文件，路径由 `.star-allinone.json` 的 `openapi` 指向
-- 真正的业务特例：权限常量名、Clear Cache 登记、IP 校验、设备/节点领域规则，放 `custom-*`
+- 流水线 ID：`.star-allinone.json` 的 `publishPipelineId`
+- OpenAPI 快照：业务仓库数据文件
+- 真正的业务特例：权限常量名、IP 校验、设备/节点领域规则
 
 ## 最终推荐流程
 
-公共 skill：
-
 ```text
-star-allinone 修改
-→ 发布 npm
-→ 业务项目升级 npm
-→ 执行 skills sync
-→ 提交 .agents/skills/shared-*
+star-allinone 修改 → 发布 npm → 业务项目升级并 skills sync → 提交 .agents/skills/shared-*
 ```
 
-业务定制 skill：
-
-```text
-业务项目直接新增或修改 custom-*
-→ 提交业务项目
-```
-
-最终结构和责任边界：
-
 ```text
+AGENTS.md
 .agents/skills/
-├── shared-*    ← npm 包同步，不能在业务项目直接维护
+├── shared-*    ← npm 包同步
 └── custom-*    ← 业务项目自己维护
 ```
-
-这比全局安装更适合团队协作，也比把公共 skill 藏在 `node_modules` 中更可靠，因为公共 skill 最终会进入业务项目仓库，团队成员拉取代码后即可直接使用。

package/skills/shared/api-to-service/SKILL.md

@@ -1,10 +1,12 @@
 ---
 name: {{sharedSkillName}}
-description: Generate frontend TypeScript API types, MFRequest service methods, aggregate exports, and contract-aligned mock artifacts for an explicitly selected API operation. Use when the user names an endpoint or operationId and asks to generate or update service, types, or mock data.
+description: User-facing. Generate or update one OpenAPI/Swagger operation as TypeScript types, an MFRequest method, and optional mock JSON. Use for a named METHOD /path or operationId. Do not use for full-spec domain regen.
 ---
 
 # API to Service
 
+User-facing entry for **one** `METHOD /path/` or `operationId`. Do not regenerate an entire Swagger/OpenAPI domain here. Full-spec rebuilds, if the project has one, live in that project's `custom-*` and are not this skill.
+
 This skill is fully shared. Generate only the requested `METHOD /path/` or `operationId`. Do not guess undocumented fields or change unrelated endpoints.
 
 Read before editing:
@@ -12,7 +14,7 @@ Read before editing:
 1. `.star-allinone.json`
 2. [references/service-conventions.md](references/service-conventions.md)
 3. [references/api-artifact-generation.md](references/api-artifact-generation.md)
-4. `.agents/skills/shared-api-mock/references/mock-conventions.md` before producing JSON
+4. [references/mock-conventions.md](references/mock-conventions.md) before producing JSON
 
 OpenAPI lookup order:
 
@@ -25,12 +27,18 @@ OpenAPI lookup order:
 ## Workflow
 
 1. Resolve one exact operation. If a path has multiple methods and intent is unclear, ask for the method. Never infer a destructive method.
-2. Recursively resolve parameters, request body, responses, and local `$ref`s. Neighboring methods that share a path are out of scope.
-3. Build the target matrix in `api-artifact-generation.md`. Compare existing types, methods, exports, and mocks. Classify create / update / reuse / conflict.
-4. Report contract conflicts before overwriting deployed behavior.
-5. Update `src/services/<Domain>/typings.d.ts`, the thin `MFRequest` method, and `src/services/index.ts` when the domain export is missing.
-6. Produce the default successful JSON mock. Add empty or error variants only when requested.
-7. Verify formatting, TypeScript, JSON parsing, exact method/path, and a focused diff.
+2. From the business project root, generate the artifacts with the CLI. Do not hand-write types or `MFRequest` methods when the spec exists:
+
+```bash
+pnpm exec star-allinone gen service --operation "GET /api/v1/devices/"
+```
+
+Use `--spec <file>` when `.star-allinone.json` has no `openapi`. Use `--domain <Name>` when the folder cannot be inferred. Use `--mock-file` only when the user asked for a mock file; otherwise keep the default conversation JSON.
+
+3. If the CLI reports reuse, keep the existing method. If it reports a conflict, stop and show the diff; do not overwrite.
+4. Review the generated types against the spec: snake_case, optionality, `| null`, unwrapped `data`, and exact method/path.
+5. Produce extra empty or error mocks only when requested, using [references/mock.md](references/mock.md).
+6. Verify formatting, TypeScript, JSON parsing, exact method/path, and a focused diff.
 
 ## Hard rules
 
@@ -45,11 +53,11 @@ OpenAPI lookup order:
 
 ```bash
 pnpm exec prettier --check <changed-service-and-json-files>
-pnpm exec tsc --noEmit
+pnpm typecheck
 ```
 
 Parse changed JSON files. Search generated names, operationId, and exact API paths for omissions and collisions. Run `pnpm lint` for broad service changes. Cite the OpenAPI path, method, operationId, and schema names in the handoff.
 
 ## User-facing output
 
-Read and apply `.agents/skills/shared-i-have-adhd/SKILL.md` to every response this skill sends to the user.
+Read and apply `.agents/skills/shared-i-have-adhd/i-have-adhd.md` to every response this skill sends to the user.

package/skills/shared/{api-mock/SKILL.md → api-to-service/references/mock.md}

@@ -1,11 +1,8 @@
----
-name: {{sharedSkillName}}
-description: Generate deterministic API mock responses matching the active frontend project's OpenAPI contract and service types. Use when the user asks for JSON fixtures, proxy-ready mock data, empty or error scenarios, or mock files for a specified endpoint.
----
-
 # API Mock
 
-This skill is fully shared. Read [references/mock-conventions.md](references/mock-conventions.md), `.star-allinone.json`, the related service types, and the OpenAPI file from `openapi` in `.star-allinone.json` (or the document provided in this conversation).
+`shared-api-to-service` reads this file when extra mock scenarios are needed. Generating types or `MFRequest` methods is not this file's job.
+
+Read [mock-conventions.md](mock-conventions.md), `.star-allinone.json`, the related service types, and the OpenAPI file from `openapi` in `.star-allinone.json` (or the document provided in this conversation).
 
 If the service contract is missing, first follow `.agents/skills/shared-api-to-service/SKILL.md`.
 
@@ -21,7 +18,3 @@ If the service contract is missing, first follow `.agents/skills/shared-api-to-s
 ## Handoff
 
 For every endpoint, report HTTP method, path, scenario label, and one strict parseable JSON block. If files were written, list the paths and confirm they parse as JSON.
-
-## User-facing output
-
-Read and apply `.agents/skills/shared-i-have-adhd/SKILL.md` to every response this skill sends to the user.

package/skills/shared/design-to-page/SKILL.md

@@ -1,11 +1,13 @@
 ---
 name: {{sharedSkillName}}
-description: Implement frontend pages from designs using the active project's React, Umi, Ant Design Pro, service, permission, routing, and component conventions. Use when translating Figma, screenshots, wireframes, or UI specs into page code.
+description: User-facing. Generate or update a page. Standard table + drawer + confirm lists use star-allinone gen page inside this skill. Use for Figma, screenshots, UI specs, or CRUD list pages.
 ---
 
 # Design to Page
 
-Translate a design into repository-native code. Reuse existing architecture; do not invent a parallel stack.
+User-facing entry for **pages**. Do not send the user to another page skill.
+
+If the request is a standard management list (table + query + drawer form + confirm), run the CLI in the standard-list path below. Dashboards, iframes, and one-off layouts stay on the design path.
 
 Before implementation, read:
 
@@ -18,13 +20,47 @@ If `.agents/project/conventions.md` exists, use it only for extra paths.
 
 Inspect the nearest existing page of the same type before proposing files.
 
-## Workflow
+## Standard list
+
+When the page is table + query + drawer + confirm, collect any missing item then generate. Do not guess the file tree.
+
+Required inputs:
+
+- Feature folder (`src/pages/<Feature>`)
+- Route path and menu title
+- List operation (`METHOD /path/` or `operationId`)
+- Optional create / update / delete operations
+- Optional permission codes for create / edit / delete
+
+1. Run the CLI from the business project root:
+
+```bash
+pnpm exec star-allinone gen page \
+  --feature <Feature> \
+  --route /path \
+  --title <中文标题> \
+  --list-operation "GET /api/v1/resource/" \
+  --create-operation "POST /api/v1/resource/" \
+  --update-operation "PATCH /api/v1/resource/{id}/" \
+  --delete-operation "DELETE /api/v1/resource/{id}/"
+```
+
+Add `--permission-create`, `--permission-edit`, `--permission-delete` when codes are known.
+
+2. If only services are missing, run `pnpm exec star-allinone gen service --operation "METHOD /path/"` first. Follow `.agents/skills/shared-api-to-service/SKILL.md`.
+3. Fill generated placeholders using [references/list-page-template.md](references/list-page-template.md): columns, form fields, rowKey, permission constants, and pagination adapter (`results/count` vs `list/total`).
+4. If `src/components/Page/Container/config.tsx` exists, register the new page as a tab after generating the standalone files. Do not invent a second page shell.
+5. Do not overwrite existing page files. Tell the user the CLI refused, then edit in place.
+
+## Design path
+
+For non-standard layouts:
 
 1. List visible states: default, loading, empty, error, disabled, overflow, permission, and narrow-screen.
 2. Resolve ambiguities that affect APIs, route ownership, permissions, or component boundaries. For minor visual gaps, follow the closest precedent and state the assumption.
 3. Write a short implementation contract: route, sections, query fields, columns, actions, APIs, permissions, states, and files.
 4. Implement the smallest complete vertical slice. Keep columns and actions outside render. Keep overlay concerns in focused components.
-5. API-backed pages include types, `MFRequest` methods, aggregate exports, and page consumption in the same change. Use `.agents/skills/shared-api-to-service/SKILL.md` for missing services. Use `.agents/skills/shared-api-mock/SKILL.md` for deterministic data. Do not embed production fake data.
+5. API-backed pages include types, `MFRequest` methods, aggregate exports, and page consumption in the same change. Use `.agents/skills/shared-api-to-service/SKILL.md` for missing services. Use `.agents/skills/shared-api-to-service/references/mock.md` for extra mock scenarios. Do not embed production fake data.
 6. Compare desktop and narrow layouts against the design. Fix structure and spacing before decoration.
 7. Run focused verification. Do not claim visual fidelity without inspecting the rendered page.
 
@@ -33,8 +69,11 @@ Inspect the nearest existing page of the same type before proposing files.
 - React function components, TypeScript, Ant Design 5, Pro Components, Less.
 - `ProForm` for business forms. `MFProTable` for management lists.
 - Overlays from `@mingfuyun/star-allinone`: `CustomDrawer`, `BaseModal`, `HocModal`.
+- Pages consume `import Service from '@/services'` only.
+- Keep columns and toolbar builders in `const.tsx`. Empty cells render as `-`.
 - Every `await` uses `try-catch`; loading restores in `finally`; `validateFields()` failures are logged and stop the request.
 - Mutations guard duplicate submit, show feedback, and reload affected lists.
+- Do not use `Modal.confirm` or feature-level Ant Design `Modal` / `Drawer` shells.
 - Do not add a UI library, state library, or CSS-in-JS system without approval.
 - Do not refactor unrelated code.
 
@@ -42,11 +81,11 @@ Inspect the nearest existing page of the same type before proposing files.
 
 ```bash
 pnpm exec prettier --check <changed-files>
-pnpm exec tsc --noEmit
+pnpm typecheck
 ```
 
 Run `pnpm lint` for broad or shared changes. Run the project's documented build command when routes, entry, or multiple pages change.
 
 ## User-facing output
 
-Read and apply `.agents/skills/shared-i-have-adhd/SKILL.md` to every response this skill sends to the user.
+Read and apply `.agents/skills/shared-i-have-adhd/i-have-adhd.md` to every response this skill sends to the user.