create-yss-spec 2.2.9 → 3.0.0

package/README.md

@@ -52,7 +52,7 @@ npx create-yss-spec@latest --version
 
 ## 当前版本说明
 
-当前 CLI 版本为 `2.2.9`，模板固定到 `a7f2c1be9cb96569c1f6d41890edd72719a5f2af`，新增 `DESIGN.md` 与设计预览资产的模板实例分发。
+当前 CLI 版本为 `3.0.0`，模板固定到 `ec54212e2a3c3ab2f2496dc27c3979b6f2ecba03`。该主版本将 Web 生成升级为批准的 schema v2 合同，绑定 `yss-dto` wire profile，并要求通过完整首切片验证器后才能声明 `first-slice-verified`。
 
 ## 接管已有项目
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-yss-spec",
-  "version": "2.2.9",
+  "version": "3.0.0",
   "description": "Initialize a YSS spec project template repository",
   "repository": {
     "type": "git",

package/template/.agents/mcp_config.json

@@ -0,0 +1,8 @@
+{
+  "mcpServers": {
+    "yss-ui": {
+      "command": "npx",
+      "args": ["-y", "@yss-ui/mcp"]
+    }
+  }
+}

package/template/.agents/rules/yss-ai-skills.md

@@ -8,6 +8,7 @@ trigger: always_on
 
 ## Available Skills
 
+- yss-ui-business-page-generation: .agents/skills/yss-ui-business-page-generation/SKILL.md
 - yss-page-module-development: .agents/skills/yss-page-module-development/SKILL.md
 - theme-token-usage: .agents/skills/theme-token-usage/SKILL.md
 - component-selection-imports: .agents/skills/component-selection-imports/SKILL.md
@@ -33,7 +34,7 @@ trigger: always_on
 
 ## Mandatory Workflow
 
-1. 页面/CRUD/列表/表单任务：先读 `.agents/skills/yss-page-module-development/SKILL.md`。
+1. 业务页面/CRUD/列表/表单/树表生成主入口：先读 `.agents/skills/yss-ui-business-page-generation/SKILL.md`（旧触发词读 `.agents/skills/yss-page-module-development/SKILL.md`）。
 2. 新增或修改页面、组件、Less、内联样式、TS 渲染配置、SVG 色值：必须读 `.agents/skills/theme-token-usage/SKILL.md`。
 3. 导出、报表、模板、附件、Excel、CSV、PDF、ZIP、Blob 下载任务：必须读 `.agents/skills/file-export-download/SKILL.md`。
 4. 列表或表格任务：同时读 `.agents/skills/page-list-module/SKILL.md`、`.agents/skills/ytable-usage/SKILL.md`、`.agents/skills/yss-use-table-height/SKILL.md`。
@@ -43,6 +44,7 @@ trigger: always_on
 
 ## Hard Stops
 
+- 模板已预置 yss-ui 项目级 MCP 配置；当前会话可用时，生成业务代码前必须先调用一次 `get_codegen_rules`。不确定导出时用 `list_components`，配置组件/Hook/Utils 前用 `get_component_docs`，复杂场景用 `get_demo`，不确定归属时用 `search_docs`。需要全局配置的客户端按 `docs/user-guide/yss-ui-mcp.md` 人工安装，不自动修改用户主目录。
 - 禁止使用 YTable 不存在的 `request`、`search-params` Props 和 `actionConfig.actions`；实例 `refresh()` 只刷新当前表格数据，不得当作远程重新查询。
 - 标准列表必须使用 `:data`、`:columns`、`:loading`、`pageable`、`v-model:pagination`、`@page-change`。
 - 表格主操作必须放入 `#toolbar-right`；只有确实需要列设置时才使用 `:toolbar-config="{ custom: true }"`。

package/template/.agents/skills/.yss-skills-manifest.json

@@ -1,28 +1,54 @@
 {
-  "source": "@yss/skills",
-  "mode": "copy",
+  "schema_version": 2,
+  "source": "iloveZzz/yss-ui",
+  "source_type": "github",
+  "source_root": "packages/skills",
+  "source_category": "app",
+  "excluded_categories": ["library"],
+  "excluded_skills": ["java-backend-commit"],
+  "source_revision": "c4d958f18cc947cb91cbe1bd48783fa4601cc18f",
+  "adaptation_ref": "docs/agents/yss-ui-skills-integration.md",
+  "package": {
+    "name": "@yss-ui/skills",
+    "version": "1.3.9"
+  },
   "skills": [
-    "yss-page-module-development",
-    "theme-token-usage",
-    "component-selection-imports",
-    "page-skeleton",
-    "page-list-module",
-    "page-form-module",
-    "ytable-usage",
-    "yedit-table-usage",
-    "ytree-usage",
-    "prototype-page-acceptance",
-    "yss-api-integration",
-    "file-export-download",
-    "vue3-best-practices",
-    "frontend-commit",
-    "java-backend-commit",
-    "yss-use-table-height",
-    "yss-use-tree-height",
-    "yss-formily",
-    "formily-foundation",
-    "formily-linkage-effects",
-    "formily-mode-slot-detail",
-    "formily-step-flow"
-  ]
+    { "upstream": "api-integration", "canonical": "yss-api-integration", "upstream_hash": "53d265c846f767c5dee9c92f2dc0caced341efd8888631f4b37a46eb486fbbeb" },
+    { "upstream": "component-selection-imports", "canonical": "component-selection-imports", "upstream_hash": "f89c536a23823b540749bab77248c1a09b3e2f43a1bc23e1a59c886a2be5ff94" },
+    { "upstream": "file-export-download", "canonical": "file-export-download", "upstream_hash": "3c281969780e6e6ea6e38818211d84b61655bcc242536785b0375de30d05a458" },
+    { "upstream": "formily-foundation", "canonical": "formily-foundation", "upstream_hash": "7736711494f368750d930e96f918bc8ae2d8a0c6b7fd404be165d03441546d9d" },
+    { "upstream": "formily-linkage-effects", "canonical": "formily-linkage-effects", "upstream_hash": "2b30d5755b672affdfbe1a21742be2ae4423361ca82d28fc5c1b7b55ef256b6e" },
+    { "upstream": "formily-mode-slot-detail", "canonical": "formily-mode-slot-detail", "upstream_hash": "857d4416264c7aadffc19560a6b04eeb4df72a3b1b9110f30d97b2e15de8ce2b" },
+    { "upstream": "formily-step-flow", "canonical": "formily-step-flow", "upstream_hash": "600a0a9a72f3bcb30db83d274b8d1082c036adf10c197dff616f76bec1a33d80" },
+    { "upstream": "frontend-commit", "canonical": "frontend-commit", "upstream_hash": "ffc1c7813607705c7c1158f4c5d3111aca79e73f1843e33bbc95eda9b5c726de" },
+    { "upstream": "page-form-module", "canonical": "page-form-module", "upstream_hash": "4df686c7267c6be00680ea1faa908e0cf02e59bfe01c8111bbcaa80dea63c9b8" },
+    { "upstream": "page-list-module", "canonical": "page-list-module", "upstream_hash": "303d8fc2161465ec3e81692c7b750ed814307ccf65f4fb51e0de69fe7af38d4f" },
+    { "upstream": "page-module-development", "canonical": "yss-page-module-development", "upstream_hash": "5f917ca85e522ddf2bf5a149db1c51e2e1b64b21e4fd6d7f8d3378177184244d" },
+    { "upstream": "page-skeleton", "canonical": "page-skeleton", "upstream_hash": "d82c44770054d9bb0bc17849c25675e5672f01144614b3ffb846ec575ac19dec" },
+    { "upstream": "prototype-page-acceptance", "canonical": "prototype-page-acceptance", "upstream_hash": "bc5d75925ac8d7a2cbc38a0d65383faa4e8384c64be3d98b9994a506f50d6003" },
+    { "upstream": "theme-token-usage", "canonical": "theme-token-usage", "upstream_hash": "b38acb4caf5012c9134df16a312b6be31b2b5d3fd6b976cfccee8d845f27c0ef" },
+    { "upstream": "use-table-height", "canonical": "yss-use-table-height", "upstream_hash": "8a5baa8ca6a8dd2b2ed123391838b1a13e3f5cab8196225ed3429ca5b513d43f" },
+    { "upstream": "use-tree-height", "canonical": "yss-use-tree-height", "upstream_hash": "2a9265cc997c2c20b6cfebbdc19b66b04450278fca5d5db252a5d855b2d95bed" },
+    { "upstream": "vue3-best-practices", "canonical": "vue3-best-practices", "upstream_hash": "924b3b4a6f603aa852e561b975c3e9652b9aad5e237411559c1d24f1f3ef7623" },
+    { "upstream": "yedit-table-usage", "canonical": "yedit-table-usage", "upstream_hash": "a2fa606b85783fc140dd1775f02d7cddde02d8f4fc2dc3c2a017cc2f9fe998b1" },
+    { "upstream": "yss-formily", "canonical": "yss-formily", "upstream_hash": "f30e312a632c592c9050d00c35c22f2dc032658e6d9fdd6e2b5dc4ac0ea970c8" },
+    { "upstream": "yss-ui-business-page-generation", "canonical": "yss-ui-business-page-generation", "upstream_hash": "97ef56c4b60c0281039996ac582ab01987b4d2bbb89989662594a6ce8a77c95f" },
+    { "upstream": "ytable-usage", "canonical": "ytable-usage", "upstream_hash": "7b3e8b3d761d910c5506ea17bf6cb264b2f313172748fe081b0fe5c9e9bbfff6" },
+    { "upstream": "ytree-usage", "canonical": "ytree-usage", "upstream_hash": "acf2de9d3391b93b636640445e738cbca747c3a963a7514dc70ef48dbe03801e" }
+  ],
+  "mcp": {
+    "package": "@yss-ui/mcp",
+    "version": "0.1.8",
+    "components_version": "1.5.18",
+    "server_name": "yss-ui",
+    "project_configs": [
+      { "path": ".mcp.json", "container": "mcpServers" },
+      { "path": ".agents/mcp_config.json", "container": "mcpServers" },
+      { "path": ".cursor/mcp.json", "container": "mcpServers" },
+      { "path": ".gemini/settings.json", "container": "mcpServers" },
+      { "path": ".kiro/settings/mcp.json", "container": "mcpServers" },
+      { "path": ".vscode/mcp.json", "container": "servers" }
+    ],
+    "global_install_guide": "docs/user-guide/yss-ui-mcp.md"
+  }
 }

package/template/.agents/skills/ask-matt/SKILL.md

@@ -84,7 +84,7 @@ Off the main flow entirely.
 - **`/grilling`** — the interview primitive itself: rounds, the frontier, facts are the agent's job and decisions are yours. `/grill-me` and `/grill-with-docs` are the two named ways in, and `/triage`, `/wayfinder` and `/improve-codebase-architecture` all run it internally. Reach for it directly only when you want the interview with no wrapper around it.
 - **`/resolving-merge-conflicts`** — work an in-progress merge or rebase conflict hunk by hunk, resolving by **intent** traced to each side's primary source rather than by picking lines, then finish the operation. It never runs `--abort`. Standalone and off every flow: reach for it when you are already mid-conflict.
 - **`/prototype`** — a small, throwaway program that answers one design question: does this state model feel right, or what should this UI look like. Throwaway is a constraint on how the code is written, not a promise to destroy it: the answer folds into the real code, and the prototype itself is kept as a **primary source** on a `prototype/<name>` branch out of main, pointed at from the implementation issue. It's the detour in step 2 of the main flow, but reach for it any time a design question is hard to settle on paper.
-- **`/research`** — delegate reading legwork to a **background agent**: it investigates a question against **primary sources**, then leaves a cited Markdown file in the repo. Keep working while it reads. The file it produces is something to take *into* the main flow at `/grill-with-docs` — research feeds the thinking, it doesn't replace it.
+- **`/yss-research`** — investigate technical or strategy evidence using `technical-evidence` / `strategy-evidence` and `quick` / `evidence-audited` modes. Use a background agent when the runtime supports it and parallel reading is useful; delegation is not a trust guarantee. The old `/research` name is a deprecated alias. Research feeds `/grill-with-docs` and lifecycle decisions; it does not approve them.
 - **`/to-questionnaire`** — when the thing blocking you isn't in your head or the codebase but in **someone else's**, this writes them a questionnaire to fill in. It's the inverse of `/grill-me`: instead of interviewing you about the subject, it interviews you about the **send** — who it's going to, what you need back — and aims the questions at the gap. What comes back is material for `/grill-with-docs` or `/to-spec`.
 - **`/wait-what`** — the corrective for a message that didn't land. Use it mid-conversation, inside any other skill, and the agent re-pitches what it just said with the context you were missing, in plain English, using the `CONTEXT.md` vocabulary. It works after the fact; `/grill-with-docs` is the upfront cure, because a shared language agreed early is what stops the jargon arriving at all.
 - **`/teach`** — learn a concept over multiple sessions, using the current directory as a stateful workspace.

package/template/.agents/skills/code-review/references/yss-review-standards.md

@@ -12,10 +12,10 @@
 2. Slice Implementation Contract 的 `required_skills`：对每个技能读取 `.agents/skills/<id>/SKILL.md` 及该 skill 指明的 references。
 3. 影响面专项检查输入（与合同并集，不得互相替代）：
    - 后端：`alibaba-java-code-style`、`yss-domain`、`yss-application`、`yss-repository`、`yss-web-controller`、`yss-dto`、`mapstruct`、`lombok`
-   - UI：`yss-ui`、`yss-design-system`、`yss-page-module-development`
+   - UI：`yss-ui`、`yss-design-system`、`yss-ui-business-page-generation`、`yss-page-module-development`
 4. 报告模板中的后端 / 前端门禁表。空着的适用行视为 `missing_evidence`。
 
-YSS 页面模块约定（YTable、YssFormily、页面骨架等）走 Standards，不并入 UI fidelity。UI fidelity 只核原型与状态矩阵。
+YSS 页面模块约定（YTable、YFormily、页面骨架等）走 Standards，不并入 UI fidelity。UI fidelity 只核原型与状态矩阵。
 
 审查者只读这些 skill，不得用它们写实现路径。`role.test-engineer` 任务包禁止 `implement` 与脚手架生成器。
 
@@ -51,4 +51,4 @@ YSS 页面模块约定（YTable、YssFormily、页面骨架等）走 Standards
 | `violation`、机器检查失败、适用行空白、`missing_evidence` | 实现者在**原合同允许路径**内修复；任何修复使候选失效，必须重新捕获并重跑 Standards、Spec、UI fidelity（若命中）和 fresh verification |
 | `drift`、`new_impacts`、`required_skills` 与真实影响不一致 | 合同标 `stale`，回 Router 或更早生命周期阶段；禁止在旧合同上继续编码 |
 
-`not-applicable` 仅当影响面未命中。命中后的 mandatory 不得豁免；只允许修复，或写完整 `seam-deferred`（风险、责任人、后续 Ticket、验证计划、目标版本或发布日期）。禁止为日常 Alibaba / YSS 新增生物人豁免门禁；安全 / 公共 API 仍走既有 `TODO-HUMAN-REVIEW` 与生物人门禁。
+`not-applicable` 仅当影响面未命中。命中后的 mandatory 不得豁免；只允许修复，或写完整 `seam-deferred`（风险、责任人、后续 Ticket、验证计划、目标版本或发布日期）。禁止为日常 Alibaba / YSS 新增生物人豁免门禁；安全 / 公共 API 仍走既有 `TODO-HUMAN-REVIEW` 与生物人门禁。

package/template/.agents/skills/component-selection-imports/SKILL.md

@@ -19,8 +19,8 @@ description: 指导 YSS UI 业务页面、CRUD、列表页、表单页和组件
 
 1. 当前会话可用 yss-ui MCP 时，先用 `list_components` 确认组件、Hook 或 Utils 是否真实存在，再用 `get_component_docs` 确认名称、导出包、Props、Events 和 Slots，不只看 demo 标签名。
 2. `get_component_docs` 未命中时，先用 `search_docs` 和 `list_components` 校正别名与归属，不得立即判定为未封装。
-3. MCP 工具不可用、调用失败或校正后仍无结果时，读取当前上下文中的最新 `llms-full.txt`；上下文没有时读取 `http://192.168.164.27:3200/llms-full.txt`。
-4. 必要时读取 `../yss-page-module-development/references/component-map.md`、`hooks-map.md`、`utils-map.md` 快速缩小范围；文档与当前项目依赖版本不一致时，最终以当前源码和可编译导出为准。
+3. MCP 工具不可用、调用失败或校正后仍无结果时，读取当前上下文或文档站的最新 `llms-full.txt`。
+4. 必要时读取 `../yss-ui-business-page-generation/references/component-map.md`、`hooks-map.md`、`utils-map.md` 快速缩小范围；文档与当前项目依赖版本不一致时，最终以当前源码和可编译导出为准。
 5. 已导出的 YSS 能力优先从 `@yss-ui/components`、`@yss-ui/hooks`、`@yss-ui/utils` 导入；确认未封装后才从 `ant-design-vue` 导入原组件。
 6. 若文档与导出源码不一致，记录差异并按当前仓库可编译的导出处理，不猜测 API。
 

package/template/.agents/skills/frontend-commit/SKILL.md

@@ -14,7 +14,7 @@ description: 分析并提交 Vue、React、TypeScript、JavaScript、Vite、微
 
 ## 不适用场景
 
-- yss-ui 组件库仓库自身的提交与发版：使用 `../commit-linting/SKILL.md`。
+- yss-ui 组件库仓库自身的提交与发版：回到 yss-ui 源仓库使用其 `categories.library` 提交流程；该类 skill 不随业务模板分发。
 - Java、Spring Boot、Maven、Gradle 后端仓库：使用 `../java-backend-commit/SKILL.md`。
 - 仅请求代码实现，不涉及提交信息或 `git commit` 操作。
 - 无代码改动，或改动内容与提交请求不匹配。

package/template/.agents/skills/wayfinder/SKILL.md

@@ -74,7 +74,7 @@ The answer isn't part of the body — it's recorded on resolution (see [Work thr
 
 Every ticket is either **HITL** — human in the loop, worked _with_ a human who speaks for themselves — or **AFK**, driven by the agent alone. A HITL ticket only resolves through that live exchange; the agent never stands in for the human's side of it (a grilling agent that answers its own questions has broken this).
 
-- **Research** (AFK): Reading documentation, third-party APIs, or local resources like knowledge bases to surface a fact a decision waits on. Resolved by a `/research` **subagent**. Use when knowledge outside the current working directory is required.
+- **Research** (AFK): Reading documentation, third-party APIs, or local resources like knowledge bases to surface a fact a decision waits on. Resolved by a `/yss-research` **subagent** (`/research` is a deprecated alias). Use when knowledge outside the current working directory is required.
 - **Prototype** (HITL): Raise the fidelity of the discussion by making a cheap, rough, concrete artifact to react to — an outline, a rough take, a stub, or UI/logic code via the /prototype skill. Links the prototype as an asset. Use when "how should it look" or "how should it behave" is the key question.
 - **Grilling** (HITL): Conversation. The default case. Always invoke the /grilling and /domain-modeling skills.
 - **Task** (HITL or AFK): Manual work that must happen before a _decision_ can be made — nothing to decide, prototype, or research, but the discussion is blocked until it's done. Signing up for a service so its API can be judged, provisioning access, moving data so its shape can be seen. This is the one type that _does_ rather than decides — and it earns its place by unblocking a decision, not by delivering the destination. The agent drives it alone where it can (AFK); otherwise it hands the human a precise checklist (HITL). Resolved when the work is done; the answer records what was done and any resulting facts (credentials location, new URLs, row counts) later tickets depend on.
@@ -112,7 +112,7 @@ User invokes with a loose idea.
 2. **Map the frontier.** Grill again, **breadth-first** this time: fan out across the whole space rather than deep on any one thread, surfacing the open decisions and the first steps takeable now. **If this surfaces no fog** — the way to the destination is already clear, the whole journey small enough for one session — you don't need a map. Stop and ask the user how they'd like to proceed.
 3. **Create the map** (label `wayfinder:map`): Destination and Notes filled in, Decisions-so-far empty, the fog sketched into **Not yet specified**.
 4. **Create the tickets you can specify now** as child issues of the map — then wire blocking edges in a **second pass** (issues need ids before they can reference each other). Wiring sorts them into the frontier and the blocked; everything you can't yet specify stays in the fog — the **Not yet specified** section.
-5. **Fire the research subagents.** For each `research` ticket you just created, spin up a `/research` subagent to resolve it in parallel, capturing its findings on a throwaway `research/<name>` branch with a context pointer from the ticket.
+5. **Fire the research subagents.** For each `research` ticket you just created, spin up a `/yss-research` subagent to resolve it in parallel, capturing its findings on a throwaway `research/<name>` branch with a context pointer from the ticket. `/research` remains only as a deprecated compatibility alias.
 6. Stop — charting is one session's work; it hand-resolves nothing.
 
 ### Work through the map