@mingfuyun/star-allinone 0.3.0 → 0.3.2

package/README.md

@@ -77,7 +77,7 @@ StarLink 示例见 `examples/projects/`。
 pnpm exec star-allinone skills sync
 ```
 
-4. 把真正的业务特例放到 `.agents/skills/custom-*`。审查、提交、发布、单接口 Mock/Service、标准列表生成不要做成 `custom-*`。全量契约重建（若需要）必须在 custom 里写明「只用于全量」。
+4. 把真正的业务特例放到 `.agents/skills/custom-*`。审查、提交、发布、单接口、页面生成不要做成 `custom-*`。全量契约重建（若需要）必须 `disable-model-invocation`，并在 `AGENTS.md` 写清命令。
 
 5. 仓库根放 `AGENTS.md`（可从包内 `examples/AGENTS.md` 复制）。`skills sync` 只在该文件缺失时补一份，不会覆盖已有内容。常驻约定只写这一份，不要加 `.cursor/rules`。
 
@@ -90,20 +90,15 @@ git commit -m "chore(skill): 接入公共 skill"
 
 ### 业务项目：日常调用
 
-只使用下面这些**用户入口**。不要直接 `$shared-verify`、`$shared-api-mock`、`$shared-commit-current-changes` 等内部 skill。
+只使用下面这些**用户入口**。
 
 ```text
 使用 $shared-api-to-service，为 GET /api/v1/devices/ 生成类型、Service 和 JSON Mock。
 ```
 
 ```text
-使用 $shared-page-recipe，生成 /widgets 标准列表页。
-列表接口 GET /api/v1/widgets/。
-```
-
-```text
-使用 $shared-design-to-page，根据我上传的设计稿生成非标准页面。
-缺少的 Service、类型和 Mock 一并生成。
+使用 $shared-design-to-page，生成 /widgets 页面。
+标准列表接口 GET /api/v1/widgets/。
 ```
 
 ```text
@@ -115,7 +110,7 @@ git commit -m "chore(skill): 接入公共 skill"
 使用 $shared-publish-test，把当前分支发布到测试环境。
 ```
 
-公共流程用 `shared-*`，项目专属规则用 `custom-*`。`custom-*` 不能再实现一遍 Service/页面生成；星链全量 swagger 重建除外。业务定制 skill 需要复用公共流程时，在 `custom-*` 的 `SKILL.md` 里写明先读取对应的 `.agents/skills/shared-*/SKILL.md`。
+公共流程用 `shared-*`，项目专属规则用 `custom-*`。`custom-*` 不能再实现一遍 Service/页面生成/审查。全量契约重建若需要，写成不可调用的脚本，并在 `AGENTS.md` 写命令。业务定制需要复用公共流程时，读取对应的 `.agents/skills/shared-*/SKILL.md`，不要再抛一个入口。
 
 ### 业务项目：更新公共 skill
 

package/examples/AGENTS.md

@@ -9,16 +9,13 @@ Always-on instructions are this file. Do not add `.cursor/rules`.
 User-facing shared entries only:
 
 - One endpoint: `pnpm exec star-allinone gen service --operation "METHOD /path/"` or `$shared-api-to-service`.
-- Standard list: `$shared-page-recipe` / `pnpm exec star-allinone gen page`.
-- Non-standard UI: `$shared-design-to-page`.
+- Pages: `$shared-design-to-page`. Standard lists run `pnpm exec star-allinone gen page` inside that skill.
 - Review and commit: `$shared-review-and-submit`. Wait for confirmation.
 - Test publish: `$shared-publish-test` after explicit pipeline confirmation.
 
-Do not invoke `shared-api-mock`, `shared-verify`, `shared-impact-analysis`, `shared-ai-review`, `shared-commit-current-changes`, or `shared-project-conventions` directly.
-
 ## Hard rules
 
-- For non-trivial changes, read `.agents/skills/shared-project-conventions` (do not `$` invoke it).
+- For non-trivial changes, read `.agents/skills/shared-project-conventions/references/architecture.md`.
 - Pages use `import Service from '@/services'`. Do not call axios or `src/services/request.tsx` from pages.
 - Lists: `MFProTable`. Forms: `ProForm`. Overlays: `CustomDrawer`, `BaseModal`, `HocModal` from `@mingfuyun/star-allinone`.
 - Keep columns and actions in `const.tsx`. Empty cells render as `-`.

package/examples/skills/custom-domain-invariants/SKILL.md

@@ -0,0 +1,16 @@
+---
+name: custom-domain-invariants
+description: Internal. Project domain extras for review. Do not invoke. Not a generate, page, or review entry.
+disable-model-invocation: true
+---
+
+# Domain invariants
+
+Not a user-facing entry. Pages, services, and review still go through `$shared-design-to-page`, `$shared-api-to-service`, and `$shared-review-and-submit`.
+
+Read this file only as extra checks after those shared skills. Do not generate pages, services, or mocks here.
+
+Example extras (replace with the project's real invariants):
+
+- IPv4 and IPv6 branches must both be checked.
+- Do not invent query param aliases that are missing from swagger.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mingfuyun/star-allinone",
-  "version": "0.3.0",
+  "version": "0.3.2",
   "description": "星系运维前端能力包",
   "main": "dist/index.js",
   "bin": {

package/scripts/cli.js

@@ -39,8 +39,12 @@ function listSharedSkillNames() {
     .sort();
 }
 
+function hasSkillMarkdown(name) {
+  return fs.existsSync(path.join(skillsRoot, name, 'SKILL.md'));
+}
+
 function listSkills() {
-  const skills = listSharedSkillNames();
+  const skills = listSharedSkillNames().filter(hasSkillMarkdown);
   if (!skills.length) {
     console.log('No shared skills found.');
     return;
@@ -142,12 +146,14 @@ function pruneStaleShared(destination, prefix, syncedNames, options) {
 
 function selectedSharedSkills(config) {
   const available = listSharedSkillNames();
+  const support = available.filter((name) => !hasSkillMarkdown(name));
   if (!config.sharedSkills) return available;
   const missing = config.sharedSkills.filter((name) => !available.includes(name));
   if (missing.length) {
     throw new Error(`Unknown sharedSkills: ${missing.join(', ')}`);
   }
-  return available.filter((name) => config.sharedSkills.includes(name));
+  const selected = available.filter((name) => config.sharedSkills.includes(name));
+  return [...new Set([...support, ...selected])];
 }
 
 function syncProject(options) {

package/skills/README.md

@@ -6,83 +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-page-recipe/
-    │   ├── 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.md
-└── .agents/
-    └── skills/
-        ├── shared-api-to-service/
-        ├── shared-api-mock/
-        ├── shared-design-to-page/
-        ├── shared-page-recipe/
-        ├── 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
-        ├── page-recipe/             # 标准列表页；CLI `gen page`
+        ├── 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 位置、领域特例。项目文件可以补充，但不能削弱公共硬规则。
 
@@ -94,13 +62,7 @@ npm 包中的 skills/shared
 业务项目 .agents/skills/shared-*
 ```
 
-不会写入：
-
-```text
-~/.codex/skills
-```
-
-也不会管理业务项目的 `custom-*` skill。
+不会写入 `~/.codex/skills`，也不会管理业务项目的 `custom-*`。`skills list` 只列出带 `SKILL.md` 的入口。无 `SKILL.md` 的目录仍会同步，供入口阅读。
 
 ## CLI 使用方式
 
@@ -110,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` → 发布新版本。
 
 业务项目操作：
 
@@ -154,83 +87,20 @@ git add package.json pnpm-lock.yaml .agents/skills/shared-*
 git commit -m "chore(skill): 更新公共 skill"
 ```
 
-团队成员只需要：
-
-```bash
-git pull
-pnpm install
-```
+团队成员只需要 `git pull` 和 `pnpm install`。不要手动修改 `shared-*`。
 
-由于公共 skill 已经提交到业务仓库，所以团队成员不需要手动安装全局 skill，也不需要拥有 `star-allinone` 源码。
+## 新增或修改业务定制
 
-## 新增或修改业务定制 skill
+`custom-*` 只用于真正的业务特例：领域不变量、全量契约脚本、度量。审查、提交、测发、单接口、页面生成都走公共入口。
 
-业务项目直接维护：
-
-```text
-.agents/skills/custom-device-management/SKILL.md
-```
-
-提交即可：
-
-```bash
-git add .agents/skills/custom-device-management
-git commit -m "feat(skill): 增加设备管理 skill"
-```
-
-不需要修改 `star-allinone`，也不需要重新发布 npm。
-
-审查、提交、测试环境发布、单接口 Mock/Service、标准列表都走公共入口 skill。`custom-*` 只用于真正的业务特例。单接口生成禁止再做 custom；只有整份契约全量重建才允许留在 custom，并必须在 description 里写明「只用于全量」。度量类 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/
-├── AGENTS.md
-├── .star-allinone.json
-└── .agents/
-    ├── skills/
-    └── project/
-        ├── conventions.md
-        ├── review-rules.md
-        └── openapi.json
-```
-
 ```json
 {
   "project": "starscope-frontend",
@@ -241,86 +111,45 @@ starscope-frontend/
 }
 ```
 
-StarLink 使用：
-
-```json
-{
-  "project": "starlink-frontend",
-  "publicSkillPrefix": "shared-",
-  "publishPipelineId": "5245265"
-}
-```
-
-完整示例见 `examples/projects/`。
-
-可选字段 `sharedSkills` 用于只同步部分公共 skill；省略时同步 `skills/shared` 下的全部公共 skill。
+完整示例见 `examples/projects/`。可选字段 `sharedSkills` 只限制用户入口；`project-conventions` 和 `i-have-adhd` 仍会同步。
 
-## 用户入口 vs 内部 skill
+## 用户入口
 
-对话里只点这些入口：
+对话里只点这些：
 
 | 入口 | 用途 |
 | --- | --- |
 | `shared-api-to-service` | 单个 `METHOD /path/` → 类型、`MFRequest`、默认 mock |
-| `shared-page-recipe` | 标准列表页（表格 + 抽屉 + 确认） |
-| `shared-design-to-page` | 非标准设计稿 |
-| `shared-review-and-submit` | 审查并提交（内部会读 impact / verify / commit） |
+| `shared-design-to-page` | 页面：标准列表内部 `gen page`，其余按设计稿实现 |
+| `shared-review-and-submit` | 审查并提交 |
 | `shared-publish-test` | 测发 |
 
-下面这些会随包同步，但 **不要作为用户入口调用**（`disable-model-invocation`）。入口 skill 会去读对应 `SKILL.md`：
-
-`shared-api-mock`、`shared-project-conventions`、`shared-verify`、`shared-impact-analysis`、`shared-ai-review`、`shared-commit-current-changes`、`shared-i-have-adhd`
-
-`custom-*` 禁止再实现一遍上述入口。单接口生成走公共 CLI；只有「整份契约全量重建」才允许留在 custom（例如 StarLink `custom-swagger-to-markdown`）。度量类 custom 不得生成代码。
-
 ## 公共规则写在哪里
 
-| 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-page-recipe` | SKILL + `references/list-page-template.md` | 标准列表页文件树；先跑 `star-allinone gen page` |
-| `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-*
-```
-
-业务定制 skill：
-
 ```text
-业务项目直接新增或修改 custom-*
-→ 提交业务项目
+star-allinone 修改 → 发布 npm → 业务项目升级并 skills sync → 提交 .agents/skills/shared-*
 ```
 
-最终结构和责任边界：
-
 ```text
-AGENTS.md           ← 常驻约定，不要加 .cursor/rules
+AGENTS.md
 .agents/skills/
-├── shared-*        ← npm 包同步，不能在业务项目直接维护
-└── custom-*        ← 业务项目自己维护
+├── shared-*    ← npm 包同步
+└── custom-*    ← 业务项目自己维护
 ```
-
-这比全局安装更适合团队协作，也比把公共 skill 藏在 `node_modules` 中更可靠，因为公共 skill 最终会进入业务项目仓库，团队成员拉取代码后即可直接使用。

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

@@ -5,7 +5,7 @@ description: User-facing. Generate or update one OpenAPI/Swagger operation as Ty
 
 # API to Service
 
-User-facing entry for **one** `METHOD /path/` or `operationId`. Do not regenerate an entire Swagger domain here. StarLink full-spec rebuilds stay on `custom-swagger-to-markdown`.
+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.
 
@@ -14,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:
 
@@ -37,7 +37,7 @@ Use `--spec <file>` when `.star-allinone.json` has no `openapi`. Use `--domain <
 
 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 `.agents/skills/shared-api-mock/SKILL.md`.
+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
@@ -60,4 +60,4 @@ Parse changed JSON files. Search generated names, operationId, and exact API pat
 
 ## 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,14 +1,8 @@
----
-name: {{sharedSkillName}}
-description: Internal. Do not invoke. Called by shared-api-to-service when extra mock scenarios are needed. Not a user-facing generate-service entry.
-disable-model-invocation: true
----
-
 # API Mock
 
-Not a user-facing entry. Do not invoke this skill. `shared-api-to-service` reads this file when extra mock scenarios are needed. Generating types or `MFRequest` methods is not this skill's job.
+`shared-api-to-service` reads this file when extra mock scenarios are needed. Generating types or `MFRequest` methods is not this file's job.
 
-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).
+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`.
 
@@ -24,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,13 +1,13 @@
 ---
 name: {{sharedSkillName}}
-description: User-facing. Implement a non-standard page from Figma, screenshots, or UI specs. For a standard table + drawer + confirm list, use shared-page-recipe instead.
+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
 
-User-facing entry for **non-standard** pages. If the request is a standard table + drawer + confirm list, stop and follow `shared-page-recipe` instead.
+User-facing entry for **pages**. Do not send the user to another page skill.
 
-Translate a design into repository-native code. Reuse existing architecture; do not invent a parallel stack.
+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:
 
@@ -20,15 +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.
 
-If the request is a standard management list (table + query + drawer form + confirm), use `.agents/skills/shared-page-recipe/SKILL.md` and `pnpm exec star-allinone gen page` instead of guessing the file tree.
+## Standard list
 
-## Workflow
+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.
 
@@ -37,8 +69,11 @@ If the request is a standard management list (table + query + drawer form + conf
 - 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.
 
@@ -46,11 +81,11 @@ If the request is a standard management list (table + query + drawer form + conf
 
 ```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.

package/skills/shared/{page-recipe → design-to-page}/references/list-page-template.md

@@ -39,6 +39,6 @@ src/pages/<Feature>/
 - `confirmLoading` tied to the async `onConfirm`.
 - Do not use `Modal.confirm`.
 
-## StarScope tabs
+## Container tabs
 
 If the project uses `src/components/Page/Container/config.tsx`, the generated `src/pages/<Feature>/index.tsx` is still the source of truth. Add a tab entry that renders the feature component. Do not duplicate fetch logic inside Container.

package/skills/shared/design-to-page/references/page-conventions.md

@@ -75,7 +75,7 @@ Follow [overlays.md](overlays.md). Use `CustomDrawer`, `BaseModal`, and `HocModa
 - API-backed pages include types, service methods, aggregate exports, and page consumption in the same change.
 - Do not embed production fake data or invented response fields.
 - If the backend contract is unavailable, label proposed methods, paths, and fields as proposed.
-- Pair missing services with `.agents/skills/shared-api-to-service/SKILL.md`. Pair missing deterministic data with `.agents/skills/shared-api-mock/SKILL.md`.
+- Pair missing services with `.agents/skills/shared-api-to-service/SKILL.md`. Pair missing deterministic data with `.agents/skills/shared-api-to-service/references/mock.md`.
 
 ## Styling and fidelity
 

package/skills/shared/i-have-adhd/{SKILL.md → i-have-adhd.md}

@@ -1,13 +1,3 @@
----
-name: {{sharedSkillName}}
-description: Internal output style. Do not invoke as a task. Other shared skills apply this file to user-facing replies. Turn on with /i-have-adhd; off with stop adhd mode.
-disable-model-invocation: true
-license: MIT
-metadata:
-  tags: "ADHD, Output Style, Productivity, Formatting"
-  category: "productivity"
----
-
 # i-have-adhd
 
 The reader has ADHD. Output is not just brief. It is shaped so an ADHD brain can act on it.

package/skills/shared/publish-test/SKILL.md

@@ -60,4 +60,4 @@ The dashboard comment is `BUILD_REMARK` and contains branch, commit subject, and
 
 ## 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/review-and-submit/SKILL.md

@@ -1,11 +1,11 @@
 ---
 name: {{sharedSkillName}}
-description: User-facing. Pre-submit workflow: impact analysis, verify, then confirmation-gated commit. Use when the user wants to review, submit, or commit. Do not invoke impact/verify/commit skills separately.
+description: User-facing. Pre-submit workflow: impact analysis, verify, then confirmation-gated commit. Use when the user wants to review, submit, or commit.
 ---
 
 # Review and Submit
 
-User-facing entry for review, submit, and commit. Do not tell the user to invoke `shared-impact-analysis`, `shared-verify`, `shared-ai-review`, or `shared-commit-current-changes` separately. Read those files in order.
+User-facing entry for review, submit, and commit. Read the files under `references/` in order. Do not tell the user to invoke other review skills.
 
 This is the unified pre-submit entry and is fully shared. Do not mutate Git until the user confirms the exact reviewed scope.
 
@@ -17,7 +17,7 @@ Execute in this order.
 
 ### 1. Impact analysis
 
-Follow `.agents/skills/shared-impact-analysis/SKILL.md`. Output:
+Follow [references/impact-analysis.md](references/impact-analysis.md). Output:
 
 - Change summary
 - Direct callers and affected pages
@@ -27,7 +27,7 @@ Follow `.agents/skills/shared-impact-analysis/SKILL.md`. Output:
 
 ### 2. Verification
 
-Follow `.agents/skills/shared-verify/SKILL.md`. Output:
+Follow [references/verify.md](references/verify.md). Output:
 
 - P0/P1/P2 blockers
 - Completeness of route, permission, API, types, mock, and page states
@@ -35,11 +35,11 @@ Follow `.agents/skills/shared-verify/SKILL.md`. Output:
 - Prettier, TypeScript, lint, and build results
 - Uncovered risks
 
-If the current change introduced P0/P1 issues or validation failures, stop. Do not enter commit review.
+Also apply [references/ai-review.md](references/ai-review.md). If the current change introduced P0/P1 issues or validation failures, stop. Do not enter commit review.
 
 ### 3. Commit review
 
-Follow `.agents/skills/shared-commit-current-changes/SKILL.md`. Output:
+Follow [references/commit.md](references/commit.md). Output:
 
 - Findings sorted P0–P2
 - Optional improvements
@@ -69,16 +69,6 @@ If the user only says `确认` but the scope is unclear, do not commit; ask for
 
 If the user says `提交代码` before a review proposal exists, run the three steps above first. Do not skip review.
 
-## Related skills
-
-| Skill | Purpose |
-| --- | --- |
-| `$shared-impact-analysis` | Read-only impact analysis |
-| `$shared-verify` | Convention and command verification |
-| `$shared-commit-current-changes` | Review plus confirmation-gated commit |
-| `$shared-ai-review` | Standalone review without commit |
-| `$shared-publish-test` | Publish to the test pipeline only after a separate `确认推送流水线`. Never run it automatically after git push. |
-
 ## 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/{ai-review/SKILL.md → review-and-submit/references/ai-review.md}

@@ -1,19 +1,13 @@
----
-name: {{sharedSkillName}}
-description: Internal. Do not invoke. Standalone review checklist used by shared-review-and-submit. Do not modify files.
-disable-model-invocation: true
----
-
 # AI Code Review
 
-Not a user-facing entry. Do not invoke this skill. `shared-review-and-submit` covers review. Do not treat this as a generate or submit entry.
+Checklist used by `shared-review-and-submit`. Do not treat this file as a generate or submit entry.
 
-This skill is fully shared. Review the current diff plus relevant callers and types. Before reviewing, read:
+Review the current diff plus relevant callers and types. Before reviewing, read:
 
 1. `.agents/skills/shared-project-conventions/references/review-checklist.md`
 2. `.agents/skills/shared-project-conventions/references/quality-checklist.md`
 
-Do not require a project-local review-rules file. If `.agents/project/review-rules.md` exists, apply extra domain checks only; do not weaken shared hard rules.
+If `.agents/project/review-rules.md` exists, apply extra domain checks only; do not weaken shared hard rules.
 
 ## Required checks
 
@@ -30,7 +24,3 @@ Do not require a project-local review-rules file. If `.agents/project/review-rul
 Lead with findings ordered `[P0]`–`[P3]`, with file and line. Separate blocking issues from recommendations. Do not report style preferences as bugs.
 
 If none, write `No issues found.` Always include validation performed and gaps. Do not modify files unless the user explicitly asks for fixes.
-
-## 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/{commit-current-changes/SKILL.md → review-and-submit/references/commit.md}

@@ -1,14 +1,6 @@
----
-name: {{sharedSkillName}}
-description: Internal. Do not invoke. Step 3 of shared-review-and-submit. Confirmation-gated commit only after that entry skill has run.
-disable-model-invocation: true
----
-
 # Commit Current Changes
 
-Not a user-facing entry. Do not invoke this skill when the user says 提交 or 审查. Use `shared-review-and-submit`, which calls this file as step 3.
-
-This skill is fully shared. Review user-authorized working-tree changes, report findings and a commit proposal, and mutate Git only after explicit confirmation.
+Step 3 of `shared-review-and-submit`. Review user-authorized working-tree changes, report findings and a commit proposal, and mutate Git only after explicit confirmation.
 
 ## Write-operation gate
 
@@ -32,8 +24,9 @@ Read:
 1. `.agents/skills/shared-project-conventions/references/review-checklist.md`
 2. `.agents/skills/shared-project-conventions/references/quality-checklist.md`
 3. `.agents/skills/shared-project-conventions/references/architecture.md`
+4. [ai-review.md](ai-review.md)
 
-This skill is fully shared. If `.agents/project/review-rules.md` exists, apply extra domain checks only; do not weaken shared hard rules.
+If `.agents/project/review-rules.md` exists, apply extra domain checks only; do not weaken shared hard rules.
 
 Classify only concrete security, data-loss, runtime, contract, validation, performance, accessibility, or maintainability risks as P0–P2.
 
@@ -58,7 +51,7 @@ Lead with findings. Then present optional improvements, validation results, chan
 3. Commit without `--no-verify` unless the user explicitly authorizes it. Do not amend unless requested.
 4. Push to upstream, or `git push -u origin HEAD` when none exists. Never force-push.
 5. Report hash, subject, files, validation, and remote branch.
-6. Stop. Do not run `$shared-publish-test` or any Yunxiao pipeline script after git push.
+6. Stop. Do not run the test pipeline after git push.
 
 A confirmed commit or push does not authorize the test pipeline. If the user later says `确认推送流水线` or `发布测试环境`, follow `.agents/skills/shared-publish-test/SKILL.md`.
 
@@ -67,7 +60,3 @@ A confirmed commit or push does not authorize the test pipeline. If the user lat
 - Never expose credentials from diffs; stop if secrets are present.
 - Never use destructive Git commands to clean the working tree.
 - If push is rejected, report the reason and do not rewrite history without separate authorization.
-
-## 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/{impact-analysis/SKILL.md → review-and-submit/references/impact-analysis.md}

@@ -1,14 +1,6 @@
----
-name: {{sharedSkillName}}
-description: Internal. Do not invoke. Step 1 of shared-review-and-submit. Read-only impact tracing.
-disable-model-invocation: true
----
-
 # Impact Analysis
 
-Not a user-facing entry. Do not invoke this skill. `shared-review-and-submit` runs this as step 1.
-
-This skill does not modify files.
+Step 1 of `shared-review-and-submit`. Do not modify files.
 
 ## Workflow
 
@@ -31,7 +23,3 @@ Read `.agents/skills/shared-project-conventions/references/review-checklist.md`
 - Risks that cannot be confirmed statically, with why
 
 Use repository facts only. Do not invent backend behavior.
-
-## 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/{verify/SKILL.md → review-and-submit/references/verify.md}

@@ -1,14 +1,8 @@
----
-name: {{sharedSkillName}}
-description: Internal. Do not invoke. Step 2 of shared-review-and-submit. Not a user-facing generate or review entry.
-disable-model-invocation: true
----
-
 # Frontend Verification
 
-Not a user-facing entry. Do not invoke this skill. `shared-review-and-submit` runs this as step 2.
+Step 2 of `shared-review-and-submit`.
 
-This skill is fully shared. Read the current diff, related callers, and:
+Read the current diff, related callers, and:
 
 1. `.agents/skills/shared-project-conventions/references/review-checklist.md`
 2. `.agents/skills/shared-project-conventions/references/architecture.md`
@@ -45,7 +39,3 @@ Run the project's build script when routes, entry, or shared runtime change.
 4. Regression list: affected pages, suggested manual paths, uncovered risks.
 
 If there are no blockers, write `未发现阻断问题`. Do not report only that commands passed.
-
-## User-facing output
-
-Read and apply `.agents/skills/shared-i-have-adhd/SKILL.md` to every response this skill sends to the user.

package/examples/skills/custom-device-service/SKILL.md

@@ -1,18 +0,0 @@
----
-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。

package/skills/shared/page-recipe/SKILL.md

@@ -1,72 +0,0 @@
----
-name: {{sharedSkillName}}
-description: User-facing. Scaffold a standard management list (route, MFProTable, drawer form, confirm modal, permissions, services). Use for CRUD list pages. Do not use for dashboards or one-off layouts.
----
-
-# List Page Recipe
-
-User-facing entry for a **standard** management list. Dashboards, iframes, and one-off layouts use `shared-design-to-page`.
-
-Scaffold a standard management list. Do not use this for dashboards, iframes, or one-off visualizations. Those stay on `shared-design-to-page`.
-
-Read before editing:
-
-1. `.star-allinone.json`
-2. `.agents/skills/shared-design-to-page/references/page-conventions.md`
-3. `.agents/skills/shared-design-to-page/references/overlays.md`
-4. [references/list-page-template.md](references/list-page-template.md)
-5. `.agents/project/conventions.md` if it exists
-
-## Required inputs
-
-Collect any missing item before generating:
-
-- 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
-
-## Workflow
-
-1. Run the CLI from the business project root. Prefer this over hand-writing the skeleton:
-
-```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: columns, form fields, rowKey, permission constants, and pagination adapter (`results/count` vs `list/total`) using the nearest page of the same type.
-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. Run focused verification.
-
-## Hard rules
-
-- `MFProTable` for the list. `ProForm` inside `CustomDrawer`. Confirmations use `BaseModal` + `HocModal`.
-- Pages consume `import Service from '@/services'` only.
-- Keep columns and toolbar builders in `const.tsx`.
-- Every `await` uses `try-catch`; restore loading in `finally`.
-- Do not use `Modal.confirm` or feature-level Ant Design `Modal` / `Drawer` shells.
-- Do not overwrite existing page files. Tell the user the CLI refused, then edit in place.
-
-## Verification
-
-```bash
-pnpm exec prettier --check <changed-files>
-pnpm typecheck
-```
-
-Run `pnpm lint` when routes or shared components change.
-
-## 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/project-conventions/SKILL.md

@@ -1,37 +0,0 @@
----
-name: {{sharedSkillName}}
-description: Internal. Do not invoke. Referenced by other shared skills for architecture and hard rules. Not a user-facing task.
-disable-model-invocation: true
----
-
-# Project Conventions
-
-Not a user-facing entry. Do not invoke this skill. Other shared skills read this file for architecture and hard rules.
-
-Use this skill for every non-trivial change. Preserve existing patterns and make the smallest scoped change.
-
-Read in this order:
-
-1. `.star-allinone.json`
-2. [references/architecture.md](references/architecture.md)
-3. [references/review-checklist.md](references/review-checklist.md)
-
-Shared rules are complete for review, commit, mock, and service generation. If `.agents/project/conventions.md` exists, use it only for extra paths or domain invariants. It must not weaken the shared hard rules below.
-
-## Hard rules
-
-- Pages consume `import Service from '@/services'`. No direct axios or request-helper calls from pages.
-- DTOs live in `src/services/<Domain>/typings.d.ts`. Pages do not redefine them.
-- Reuse `MFProTable`, `ProForm`, `CustomDrawer`, `BaseModal`, `HocModal`, and existing permission wrappers.
-- Backend field names stay in service types. Convert only at an adapter boundary.
-- Async surfaces handle loading, empty, error, retry, unauthorized, and duplicate-submit.
-- No unexplained `any`, `as any`, `@ts-ignore`, or `Record<string, any>` when the contract is known.
-- No new UI/state library without approval.
-
-## Completion
-
-Report changed files, API operations used, states covered, validation commands and results, and remaining gaps.
-
-## User-facing output
-
-Read and apply `.agents/skills/shared-i-have-adhd/SKILL.md` to every response this skill sends to the user.