create-yss-spec 3.0.0 → 3.0.1

package/template/yss-public-skills.json

@@ -29,9 +29,9 @@
     "yss-prototype-stage",
     "yss-repository",
     "yss-resilience4j",
-    "yss-router",
+    "yss-implementation-contract-compiler",
     "yss-security-algorithm",
-    "yss-source-index",
+    "yss-skill-source-index-refresh",
     "yss-ui",
     "yss-ui-business-page-generation",
     "yss-up-springboot3",
@@ -48,8 +48,8 @@
       "skills": [
         "yss-microapp-commit",
         "yss-product-lifecycle",
-        "yss-router",
-        "yss-source-index"
+        "yss-implementation-contract-compiler",
+        "yss-skill-source-index-refresh"
       ]
     },
     {

package/template.manifest.json

@@ -4,9 +4,6 @@
     ".claude",
     ".codex",
     ".cursor",
-    ".gemini",
-    ".hermes",
-    ".kiro",
     ".pi",
     ".qoder",
     ".trae",

package/template.snapshot.json

@@ -3,15 +3,15 @@
   "templateName": "yss-spec-project-template",
   "templateSource": "github:iloveZzz/yss-spec-project-template",
   "templateRepository": "https://github.com/iloveZzz/yss-spec-project-template.git",
-  "requestedRef": "ec54212e2a3c3ab2f2496dc27c3979b6f2ecba03",
-  "templateCommit": "ec54212e2a3c3ab2f2496dc27c3979b6f2ecba03",
-  "manifestHash": "1efcdfb92db0c48fcb951a0d87e7c4a7c8b1f14161d8c5f8eb441e70b2440537",
+  "requestedRef": "f454f08950cad6acc6cba2e413e62a3e942677fe",
+  "templateCommit": "f454f08950cad6acc6cba2e413e62a3e942677fe",
+  "manifestHash": "3c72c098a0f70a8f7c80e8888c67ab76ad9023b5fc5e1019c084d1f15950db17",
   "encodedPaths": {
     ".codex/skills/data-analytics/.gitignore": ".codex/skills/data-analytics/__yss_dotfile__.gitignore",
     ".codex/skills/product-design/.npmignore": ".codex/skills/product-design/__yss_dotfile__.npmignore",
     ".codex/skills/product-design/templates/prototype/.npmrc": ".codex/skills/product-design/templates/prototype/__yss_dotfile__.npmrc",
     ".gitignore": "__yss_dotfile__.gitignore"
   },
-  "snapshotHash": "b230de7c4f709cfe9b3f5139de9a83878c443774ff9f23d34c8faa872672812f",
-  "generatedAt": "2026-09-03T16:56:40.983Z"
+  "snapshotHash": "f1d56221e14ad517e42cc07eb77507e2c7394c31ed941d06cceed38d0a237319",
+  "generatedAt": "2026-09-04T08:02:46.462Z"
 }

package/template/.agents/skills/yss-router/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "YSS Router"
-  short_description: "Route YSS tasks to the right skills"
-  default_prompt: "Use yss-router to choose the minimal YSS skills for this task."

package/template/.agents/skills/yss-router/references/boundaries.md

@@ -1,50 +0,0 @@
-# YSS Skill Boundaries
-
-Use this reference when multiple YSS skills seem applicable.
-
-中文说明：当多个 YSS 技能看起来都能用时，先看这个边界说明，选择最小技能组合。
-
-## Frontend Boundaries
-
-- `yss-page-module-development`: Page/module workflow. Use for creating or reorganizing a page folder, deciding structure, and assembling page, hooks, schemas, and blocks.
-- `yss-components`: Component layout and visual/page composition rules. Use for YTable/YTree/YssFormily/YSplitPane usage details.
-- `yss-hook`: Request, pagination, parameter, tree-selection, and response-mapping logic in `views/**/hooks/useXxx.ts`.
-- `yss-api-integration`: Orval-generated API client imports, request/response mapping, `useRequest` calling patterns, submit/list/detail flows.
-- `yss-formily`: Hand-written YssFormily schema implementation and form behavior.
-- `yss-formily-schema-generator`: Generate YssFormily schema from requirements, screenshots, mockups, Figma, or natural-language field descriptions.
-- `yss-use-table-height`: Only table available-height calculation and required container/pagination/toolbar wiring.
-- `yss-use-tree-height`: Only tree available-height calculation, search offset, and virtual scrolling wiring.
-
-Default for a new page: first verify the approved product design, state matrix, Ant Design v6 theme/visual-standard high-fidelity HTML prototype, schema v2 semantic mapping/browser/accessibility evidence, and user confirmation; then use the implementation lockfile to map into YSS UI + Ant Design Vue 4.x, start with `yss-page-module-development`, and add the narrow skills that match the page controls.
-
-中文说明：新建页面默认从页面模块技能开始，只有遇到具体组件、Hook、API、Formily 细节时再加载专项技能。
-
-## Backend Boundaries
-
-- `yss-ddd-scaffold-generator`: Create a whole multi-module backend skeleton.
-- `yss-domain`: Domain modeling, domain gateway contracts, and domain-layer conventions.
-- `yss-application`: Application use cases, transaction boundaries, and cross-aggregate orchestration.
-- `yss-repository`: Persistence implementation, PO, Repository, Convertor, GatewayImpl.
-- `yss-web-controller`: REST adapter layer, request/response DTOs, VO, web convertor.
-- `yss-mybatis`: Framework behavior for MyBatis/MyBatis-Plus, BaseRepository, pagination, mapper scanning, batch, datasource issues.
-- `yss-dto`: Result/PageQuery/CommandDTO/QueryDTO and unified API contract objects.
-
-Default for end-to-end backend CRUD: include Domain, Application, Infrastructure, and Web skills plus `mapstruct`, `lombok`, and `alibaba-java-code-style`; add `yss-mybatis` when persistence framework details matter. The executable closure in `router-contract.yaml` is authoritative.
-
-中文说明：后端 CRUD 按领域、DTO、持久层、Controller 分层处理；只有涉及 MyBatis 机制、分页、扫描、多数据源时才加 `yss-mybatis`。
-
-## Component Boundaries
-
-- `yss-cache`: Query/update/clear cache annotations, Redis/Caffeine/JetCache wiring, cache invalidation.
-- `yss-audit-log`: Audit annotations, SpEL summaries, async publication, subscribers.
-- `yss-excel-mvc`: Spring MVC Excel import/export annotations and handlers.
-- `yss-distributed-id`: ID strategies, AutoIdInterceptor, Leaf/CosId/Snowflake, batch ID injection.
-- `yss-resilience4j`: Circuit breaker, fallback, and gateway resilience integration.
-- `yss-validation`: Validation engine and JSR-303 integration.
-- `yss-security-algorithm`: RSA/AES/SM/JWT/JWK/password-encoding compatibility and production key-management safety gates.
-- `yss-userinfo`: Current-user info propagation and starter integration.
-- `yss-exception`: Exception component and unified exception handling.
-
-Component skills should inspect generated `references/source-index.md` before changing code when the task depends on exact class or config names.
-
-中文说明：组件类技能不要凭记忆猜类名，先用源码索引找真实位置。

package/template/.agents/skills/yss-source-index/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "YSS Source Index"
-  short_description: "Refresh YSS skill source indexes"
-  default_prompt: "Refresh YSS skill indexes from yss-cloud-microservice and YSS UI docs."

package/template/.claude/skills/yss-router/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "YSS Router"
-  short_description: "Route YSS tasks to the right skills"
-  default_prompt: "Use yss-router to choose the minimal YSS skills for this task."

package/template/.claude/skills/yss-router/references/boundaries.md

@@ -1,50 +0,0 @@
-# YSS Skill Boundaries
-
-Use this reference when multiple YSS skills seem applicable.
-
-中文说明：当多个 YSS 技能看起来都能用时，先看这个边界说明，选择最小技能组合。
-
-## Frontend Boundaries
-
-- `yss-page-module-development`: Page/module workflow. Use for creating or reorganizing a page folder, deciding structure, and assembling page, hooks, schemas, and blocks.
-- `yss-components`: Component layout and visual/page composition rules. Use for YTable/YTree/YssFormily/YSplitPane usage details.
-- `yss-hook`: Request, pagination, parameter, tree-selection, and response-mapping logic in `views/**/hooks/useXxx.ts`.
-- `yss-api-integration`: Orval-generated API client imports, request/response mapping, `useRequest` calling patterns, submit/list/detail flows.
-- `yss-formily`: Hand-written YssFormily schema implementation and form behavior.
-- `yss-formily-schema-generator`: Generate YssFormily schema from requirements, screenshots, mockups, Figma, or natural-language field descriptions.
-- `yss-use-table-height`: Only table available-height calculation and required container/pagination/toolbar wiring.
-- `yss-use-tree-height`: Only tree available-height calculation, search offset, and virtual scrolling wiring.
-
-Default for a new page: first verify the approved product design, state matrix, Ant Design v6 theme/visual-standard high-fidelity HTML prototype, schema v2 semantic mapping/browser/accessibility evidence, and user confirmation; then use the implementation lockfile to map into YSS UI + Ant Design Vue 4.x, start with `yss-page-module-development`, and add the narrow skills that match the page controls.
-
-中文说明：新建页面默认从页面模块技能开始，只有遇到具体组件、Hook、API、Formily 细节时再加载专项技能。
-
-## Backend Boundaries
-
-- `yss-ddd-scaffold-generator`: Create a whole multi-module backend skeleton.
-- `yss-domain`: Domain modeling, domain gateway contracts, and domain-layer conventions.
-- `yss-application`: Application use cases, transaction boundaries, and cross-aggregate orchestration.
-- `yss-repository`: Persistence implementation, PO, Repository, Convertor, GatewayImpl.
-- `yss-web-controller`: REST adapter layer, request/response DTOs, VO, web convertor.
-- `yss-mybatis`: Framework behavior for MyBatis/MyBatis-Plus, BaseRepository, pagination, mapper scanning, batch, datasource issues.
-- `yss-dto`: Result/PageQuery/CommandDTO/QueryDTO and unified API contract objects.
-
-Default for end-to-end backend CRUD: include Domain, Application, Infrastructure, and Web skills plus `mapstruct`, `lombok`, and `alibaba-java-code-style`; add `yss-mybatis` when persistence framework details matter. The executable closure in `router-contract.yaml` is authoritative.
-
-中文说明：后端 CRUD 按领域、DTO、持久层、Controller 分层处理；只有涉及 MyBatis 机制、分页、扫描、多数据源时才加 `yss-mybatis`。
-
-## Component Boundaries
-
-- `yss-cache`: Query/update/clear cache annotations, Redis/Caffeine/JetCache wiring, cache invalidation.
-- `yss-audit-log`: Audit annotations, SpEL summaries, async publication, subscribers.
-- `yss-excel-mvc`: Spring MVC Excel import/export annotations and handlers.
-- `yss-distributed-id`: ID strategies, AutoIdInterceptor, Leaf/CosId/Snowflake, batch ID injection.
-- `yss-resilience4j`: Circuit breaker, fallback, and gateway resilience integration.
-- `yss-validation`: Validation engine and JSR-303 integration.
-- `yss-security-algorithm`: RSA/AES/SM/JWT/JWK/password-encoding compatibility and production key-management safety gates.
-- `yss-userinfo`: Current-user info propagation and starter integration.
-- `yss-exception`: Exception component and unified exception handling.
-
-Component skills should inspect generated `references/source-index.md` before changing code when the task depends on exact class or config names.
-
-中文说明：组件类技能不要凭记忆猜类名，先用源码索引找真实位置。

package/template/.claude/skills/yss-source-index/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "YSS Source Index"
-  short_description: "Refresh YSS skill source indexes"
-  default_prompt: "Refresh YSS skill indexes from yss-cloud-microservice and YSS UI docs."

package/template/.codex/skills/yss-router/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "YSS Router"
-  short_description: "Route YSS tasks to the right skills"
-  default_prompt: "Use yss-router to choose the minimal YSS skills for this task."

package/template/.codex/skills/yss-router/references/boundaries.md

@@ -1,50 +0,0 @@
-# YSS Skill Boundaries
-
-Use this reference when multiple YSS skills seem applicable.
-
-中文说明：当多个 YSS 技能看起来都能用时，先看这个边界说明，选择最小技能组合。
-
-## Frontend Boundaries
-
-- `yss-page-module-development`: Page/module workflow. Use for creating or reorganizing a page folder, deciding structure, and assembling page, hooks, schemas, and blocks.
-- `yss-components`: Component layout and visual/page composition rules. Use for YTable/YTree/YssFormily/YSplitPane usage details.
-- `yss-hook`: Request, pagination, parameter, tree-selection, and response-mapping logic in `views/**/hooks/useXxx.ts`.
-- `yss-api-integration`: Orval-generated API client imports, request/response mapping, `useRequest` calling patterns, submit/list/detail flows.
-- `yss-formily`: Hand-written YssFormily schema implementation and form behavior.
-- `yss-formily-schema-generator`: Generate YssFormily schema from requirements, screenshots, mockups, Figma, or natural-language field descriptions.
-- `yss-use-table-height`: Only table available-height calculation and required container/pagination/toolbar wiring.
-- `yss-use-tree-height`: Only tree available-height calculation, search offset, and virtual scrolling wiring.
-
-Default for a new page: first verify the approved product design, state matrix, Ant Design v6 theme/visual-standard high-fidelity HTML prototype, schema v2 semantic mapping/browser/accessibility evidence, and user confirmation; then use the implementation lockfile to map into YSS UI + Ant Design Vue 4.x, start with `yss-page-module-development`, and add the narrow skills that match the page controls.
-
-中文说明：新建页面默认从页面模块技能开始，只有遇到具体组件、Hook、API、Formily 细节时再加载专项技能。
-
-## Backend Boundaries
-
-- `yss-ddd-scaffold-generator`: Create a whole multi-module backend skeleton.
-- `yss-domain`: Domain modeling, domain gateway contracts, and domain-layer conventions.
-- `yss-application`: Application use cases, transaction boundaries, and cross-aggregate orchestration.
-- `yss-repository`: Persistence implementation, PO, Repository, Convertor, GatewayImpl.
-- `yss-web-controller`: REST adapter layer, request/response DTOs, VO, web convertor.
-- `yss-mybatis`: Framework behavior for MyBatis/MyBatis-Plus, BaseRepository, pagination, mapper scanning, batch, datasource issues.
-- `yss-dto`: Result/PageQuery/CommandDTO/QueryDTO and unified API contract objects.
-
-Default for end-to-end backend CRUD: include Domain, Application, Infrastructure, and Web skills plus `mapstruct`, `lombok`, and `alibaba-java-code-style`; add `yss-mybatis` when persistence framework details matter. The executable closure in `router-contract.yaml` is authoritative.
-
-中文说明：后端 CRUD 按领域、DTO、持久层、Controller 分层处理；只有涉及 MyBatis 机制、分页、扫描、多数据源时才加 `yss-mybatis`。
-
-## Component Boundaries
-
-- `yss-cache`: Query/update/clear cache annotations, Redis/Caffeine/JetCache wiring, cache invalidation.
-- `yss-audit-log`: Audit annotations, SpEL summaries, async publication, subscribers.
-- `yss-excel-mvc`: Spring MVC Excel import/export annotations and handlers.
-- `yss-distributed-id`: ID strategies, AutoIdInterceptor, Leaf/CosId/Snowflake, batch ID injection.
-- `yss-resilience4j`: Circuit breaker, fallback, and gateway resilience integration.
-- `yss-validation`: Validation engine and JSR-303 integration.
-- `yss-security-algorithm`: RSA/AES/SM/JWT/JWK/password-encoding compatibility and production key-management safety gates.
-- `yss-userinfo`: Current-user info propagation and starter integration.
-- `yss-exception`: Exception component and unified exception handling.
-
-Component skills should inspect generated `references/source-index.md` before changing code when the task depends on exact class or config names.
-
-中文说明：组件类技能不要凭记忆猜类名，先用源码索引找真实位置。

package/template/.codex/skills/yss-source-index/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "YSS Source Index"
-  short_description: "Refresh YSS skill source indexes"
-  default_prompt: "Refresh YSS skill indexes from yss-cloud-microservice and YSS UI docs."

package/template/.cursor/skills/yss-router/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "YSS Router"
-  short_description: "Route YSS tasks to the right skills"
-  default_prompt: "Use yss-router to choose the minimal YSS skills for this task."

package/template/.cursor/skills/yss-router/references/boundaries.md

@@ -1,50 +0,0 @@
-# YSS Skill Boundaries
-
-Use this reference when multiple YSS skills seem applicable.
-
-中文说明：当多个 YSS 技能看起来都能用时，先看这个边界说明，选择最小技能组合。
-
-## Frontend Boundaries
-
-- `yss-page-module-development`: Page/module workflow. Use for creating or reorganizing a page folder, deciding structure, and assembling page, hooks, schemas, and blocks.
-- `yss-components`: Component layout and visual/page composition rules. Use for YTable/YTree/YssFormily/YSplitPane usage details.
-- `yss-hook`: Request, pagination, parameter, tree-selection, and response-mapping logic in `views/**/hooks/useXxx.ts`.
-- `yss-api-integration`: Orval-generated API client imports, request/response mapping, `useRequest` calling patterns, submit/list/detail flows.
-- `yss-formily`: Hand-written YssFormily schema implementation and form behavior.
-- `yss-formily-schema-generator`: Generate YssFormily schema from requirements, screenshots, mockups, Figma, or natural-language field descriptions.
-- `yss-use-table-height`: Only table available-height calculation and required container/pagination/toolbar wiring.
-- `yss-use-tree-height`: Only tree available-height calculation, search offset, and virtual scrolling wiring.
-
-Default for a new page: first verify the approved product design, state matrix, Ant Design v6 theme/visual-standard high-fidelity HTML prototype, schema v2 semantic mapping/browser/accessibility evidence, and user confirmation; then use the implementation lockfile to map into YSS UI + Ant Design Vue 4.x, start with `yss-page-module-development`, and add the narrow skills that match the page controls.
-
-中文说明：新建页面默认从页面模块技能开始，只有遇到具体组件、Hook、API、Formily 细节时再加载专项技能。
-
-## Backend Boundaries
-
-- `yss-ddd-scaffold-generator`: Create a whole multi-module backend skeleton.
-- `yss-domain`: Domain modeling, domain gateway contracts, and domain-layer conventions.
-- `yss-application`: Application use cases, transaction boundaries, and cross-aggregate orchestration.
-- `yss-repository`: Persistence implementation, PO, Repository, Convertor, GatewayImpl.
-- `yss-web-controller`: REST adapter layer, request/response DTOs, VO, web convertor.
-- `yss-mybatis`: Framework behavior for MyBatis/MyBatis-Plus, BaseRepository, pagination, mapper scanning, batch, datasource issues.
-- `yss-dto`: Result/PageQuery/CommandDTO/QueryDTO and unified API contract objects.
-
-Default for end-to-end backend CRUD: include Domain, Application, Infrastructure, and Web skills plus `mapstruct`, `lombok`, and `alibaba-java-code-style`; add `yss-mybatis` when persistence framework details matter. The executable closure in `router-contract.yaml` is authoritative.
-
-中文说明：后端 CRUD 按领域、DTO、持久层、Controller 分层处理；只有涉及 MyBatis 机制、分页、扫描、多数据源时才加 `yss-mybatis`。
-
-## Component Boundaries
-
-- `yss-cache`: Query/update/clear cache annotations, Redis/Caffeine/JetCache wiring, cache invalidation.
-- `yss-audit-log`: Audit annotations, SpEL summaries, async publication, subscribers.
-- `yss-excel-mvc`: Spring MVC Excel import/export annotations and handlers.
-- `yss-distributed-id`: ID strategies, AutoIdInterceptor, Leaf/CosId/Snowflake, batch ID injection.
-- `yss-resilience4j`: Circuit breaker, fallback, and gateway resilience integration.
-- `yss-validation`: Validation engine and JSR-303 integration.
-- `yss-security-algorithm`: RSA/AES/SM/JWT/JWK/password-encoding compatibility and production key-management safety gates.
-- `yss-userinfo`: Current-user info propagation and starter integration.
-- `yss-exception`: Exception component and unified exception handling.
-
-Component skills should inspect generated `references/source-index.md` before changing code when the task depends on exact class or config names.
-
-中文说明：组件类技能不要凭记忆猜类名，先用源码索引找真实位置。

package/template/.cursor/skills/yss-source-index/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "YSS Source Index"
-  short_description: "Refresh YSS skill source indexes"
-  default_prompt: "Refresh YSS skill indexes from yss-cloud-microservice and YSS UI docs."

package/template/.gemini/settings.json

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

package/template/.hermes/skills/alibaba-java-code-style/SKILL.md

@@ -1,51 +0,0 @@
----
-name: alibaba-java-code-style
-description: Apply Alibaba Java Development Manual conventions when implementing, refactoring, or reviewing Java/JVM code, Spring-style services, MyBatis/ORM mappings, SQL, Maven dependencies, unit tests, exception/logging behavior, security checks, and design documentation. Use when the user asks for Java code规范, 阿里规范, P3C-style review, Java code style, or compliance with Alibaba Java coding guidelines.
----
-
-# Alibaba Java Code Style
-
-This skill distills the provided `阿里巴巴 Java 开发手册` 1.4.0 PDF into execution rules for Codex. Treat rules marked mandatory as review blockers unless the repository's own `AGENTS.md`, security constraints, or existing framework conventions explicitly require a different pattern.
-
-## Workflow
-
-1. Identify the touched surface:
-   - Java source, naming, constants, OOP, collections, concurrency, control flow, comments: read `references/java-programming.md`.
-   - Exceptions, logging, unit tests, or security: read `references/reliability-test-security.md`.
-   - MySQL, ORM/MyBatis, Maven dependencies, layering, server/JVM settings, or design artifacts: read `references/database-engineering-design.md`.
-2. Apply mandatory rules first, then use recommended rules to improve maintainability, performance, and readability.
-3. When reviewing, report mandatory violations as findings. Mention recommended violations when they create real risk or are already in the changed area.
-4. When implementing, prefer the repository's existing framework helpers and code generation skills over inventing new local infrastructure.
-5. If a rule touches a project safety boundary such as auth, payment, encryption, raw SQL, database migration scripts, or public base library API changes, produce a draft or `TODO-HUMAN-REVIEW` rather than silently finalizing risky code.
-
-## Core Priorities
-
-- Keep names readable, English, and consistent with Java layer conventions.
-- Avoid null, equality, wrapper comparison, collection, and concurrency traps that compile cleanly but fail at runtime.
-- Make logs useful without wasting CPU, disk, or alert budget.
-- Keep unit tests automatic, independent, repeatable, and close to public behavior.
-- Bind SQL parameters, define explicit ORM mappings, and never rely on string-concatenated SQL.
-- Preserve layering: web/controller code validates and adapts; service/manager code owns business orchestration; DAO/repository code owns persistence.
-
-## Review Checklist
-
-- Naming and formatting are consistent: camel case, constants, package names, braces, spacing, line length, UTF-8/Unix line endings.
-- POJO, DTO, DO, VO, Query, enum, interface, implementation, and test names follow the expected suffixes and boolean naming rules.
-- `equals`, `hashCode`, wrapper comparisons, `toString`, `serialVersionUID`, constructors, access modifiers, and getters/setters avoid known pitfalls.
-- Collection code avoids unsafe `subList`, `Arrays.asList`, raw `toArray`, foreach removal, null-unsafe maps, and invalid comparators.
-- Thread code uses named thread pools, avoids `Executors` factories in production code, and handles locking order, date formatting, and scheduled tasks safely.
-- Exceptions are handled at the right layer, logged once with context and stack, and never swallowed or used for normal control flow.
-- Tests use assertions, avoid external dependence, live under `src/test/java`, and cover boundaries, correct cases, design cases, and error cases.
-- Security-sensitive inputs are validated, authorized, escaped, CSRF-protected, rate-limited, and never concatenated into SQL.
-- MySQL DDL/SQL/ORM code uses explicit fields, mappings, indexes, timestamps, `#{}`
-  parameter binding, and avoids dangerous cascades, stored procedures, `select *`, and uncontrolled pagination.
-
-## Source
-
-Based on the user-provided PDF: `阿里巴巴 Java 开发手册` version 1.4.0, Alibaba Group technical team, update date 2018-05-20.
-
-## 阶段 7 执行结果
-
-- 消费当前合同版本、changed files 和 verification results，只审查合同允许范围。
-- 必须把 mandatory violation 返回为 `violation`，并提供文件/位置/规则证据；高风险项保留 `TODO-HUMAN-REVIEW`。
-- 按统一 `YSS Skill Execution Result` 返回审查证据、偏离和新增安全/SQL/公共 API 影响，不得仅输出“符合规范”。

package/template/.hermes/skills/alibaba-java-code-style/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "Alibaba Java Code Style"
-  short_description: "Apply Alibaba Java development guidelines"
-  default_prompt: "Use $alibaba-java-code-style to implement or review Java code against Alibaba Java development conventions."

package/template/.hermes/skills/alibaba-java-code-style/references/database-engineering-design.md

@@ -1,147 +0,0 @@
-# Database, Engineering, And Design Rules
-
-Use this reference for MySQL DDL/SQL, ORM mappings, Maven/library dependency rules, application layering, server/JVM settings, and design artifacts.
-
-## MySQL Table Design
-
-Mandatory:
-
-- Boolean database fields must be named `is_xxx` and use `unsigned tinyint`, where `1` means yes and `0` means no. POJO boolean fields must not use `is` prefix, so define explicit ORM mappings.
-- Table and field names must be lowercase letters or digits. Do not start with digits, use uppercase, or use patterns such as `level_3_name`.
-- Table names must be singular.
-- Do not use MySQL reserved words such as `desc`, `range`, `match`, or `delayed`.
-- Index names: primary key `pk_字段名`, unique index `uk_字段名`, normal index `idx_字段名`.
-- Use `decimal` for decimals. Do not use `float` or `double` for precise stored values.
-- Use `char` for nearly fixed-length strings.
-- `varchar` length must not exceed 5000. For longer content, use `text` in a separate table keyed by the primary key to avoid hurting other index efficiency.
-- Every table must include `id`, `gmt_create`, and `gmt_modified`. `id` is `bigint unsigned` primary key with auto-increment step 1 for single tables; timestamps are `datetime`.
-
-Recommended/reference:
-
-- Prefer table names like `业务名称_表作用`.
-- Keep database name aligned with application name where possible.
-- Update field comments when field meaning or status values change.
-- Redundant fields are allowed for performance only when consistency is considered, the value is not frequently changed, and the field is not long `varchar` or `text`.
-- Consider sharding only when a single table exceeds about 5 million rows or 2 GB, or when projections clearly require it.
-- Choose compact unsigned integer types where domain ranges allow.
-
-## Indexes
-
-Mandatory:
-
-- Business-unique fields must have unique indexes, even when uniqueness is also checked in application code.
-- Do not join more than 3 tables. Join column types must be exactly consistent and associated columns must have indexes.
-- When indexing `varchar`, specify an index length based on real selectivity instead of indexing the whole field.
-- Page search must not use left fuzzy or full fuzzy queries such as `%keyword` or `%keyword%`; use a search engine when needed.
-
-Recommended/reference:
-
-- For `order by`, align the ordered field with the last part of the composite index where possible, such as `where a=? and b=? order by c` with index `a_b_c`.
-- Use covering indexes to avoid table lookups where suitable.
-- For deep pagination, use delayed join/subquery techniques to locate IDs first, or cap total pages.
-- SQL optimization target: at least `range`, preferably `ref`, best `const`.
-- Put the most selective equality column on the left side of composite indexes. When mixed with range conditions, place equality conditions first.
-- Avoid implicit type conversion, which can invalidate indexes.
-- Avoid both extremes: indexing every query and resisting necessary indexes such as unique indexes.
-
-## SQL And ORM
-
-Mandatory:
-
-- Use `count(*)` for row counts, not `count(column)` or `count(constant)`.
-- Know `count(distinct col)` ignores nulls; `sum(col)` over all-null rows returns null, so guard against NPE.
-- Use `ISNULL()` or the project-standard equivalent to test nulls; direct equality comparisons with null do not behave as true/false.
-- In pagination code, return immediately when count is 0 instead of running the page query.
-- Do not use foreign keys or cascades; model those relationships in application logic for distributed/high-concurrency systems.
-- Do not use stored procedures in application code.
-- For data correction, especially delete/update, select first and confirm before mutating.
-- In queries, never use `*`; explicitly list required fields.
-- POJO boolean fields must not use `is` prefix, while database fields must use `is_`; define explicit result mappings.
-- Do not rely on `resultClass` for ORM returns. Define `resultMap` or equivalent explicit mappings.
-- MyBatis/iBATIS XML parameters must use `#{}`. Do not use `${}` for user-controlled values because it risks SQL injection.
-- Do not return raw `HashMap`/`Hashtable` as query results; use typed objects.
-- Every update to a table record must update `gmt_modified` to the current time.
-
-Recommended/reference:
-
-- Avoid large `IN` lists; keep them under about 1000 items if unavoidable.
-- For internationalized storage, use UTF-8; use `utf8mb4` when storing emoji.
-- Avoid `TRUNCATE TABLE` in application code; it has no transaction and does not trigger delete behavior.
-- Do not create a large all-fields update API. Update only changed target fields to reduce mistakes, binlog size, and work.
-- Do not overuse `@Transactional`; consider database QPS and rollback/compensation for cache, search, messages, and statistics.
-
-## Application Layering
-
-Recommended/reference:
-
-- Follow downward dependencies:
-  - Open API layer: exposes service methods as RPC/HTTP, handles gateway security and traffic controls.
-  - Terminal display layer: templates, JavaScript rendering, JSP, or mobile display.
-  - Web layer: forwarding, access control, basic parameter validation, and simple non-reused business handling.
-  - Service layer: concrete business logic.
-  - Manager layer: common business handling, third-party platform adaptation, service common capability extraction, cache/middleware handling, and DAO composition.
-  - DAO layer: persistence interaction with MySQL, Oracle, HBase, etc.
-  - External interfaces: other departments' RPC APIs, base platforms, or third-party HTTP APIs.
-- Exception handling by layer:
-  - DAO catches broad persistence exceptions and wraps them as `DAOException`; do not log again if the upper layer will log.
-  - Service logs exceptions with parameters and context.
-  - Manager follows DAO behavior when deployed with Service, or Service behavior when independently deployed.
-  - Web should not keep throwing to users; render friendly errors when the page cannot proceed.
-  - Open API converts exceptions to error code and message.
-- Domain model meanings:
-  - `DO`: database table object, passed upward by DAO.
-  - `DTO`: transfer object from Service/Manager outward.
-  - `BO`: business object output by Service.
-  - `AO`: application object between Web and Service, close to display and not highly reusable.
-  - `VO`: view object for Web/template rendering.
-  - `Query`: query request object. If a query has more than 2 parameters, wrap them; do not pass `Map`.
-
-## Maven And Library Dependencies
-
-Mandatory:
-
-- Use GAV conventions where applicable: `GroupId` as `com.{company/BU}.business[.subBusiness]`, `ArtifactId` as `product-module`, version as `major.minor.patch`.
-- Version meaning: major for direction/large incompatibility/architecture changes, minor for mostly compatible major features, patch for compatible bugfixes/minor features. Initial formal release should be `1.0.0`.
-- Online applications must not depend on `SNAPSHOT` versions except explicitly allowed security packages.
-- Adding/upgrading a library must preserve dependency mediation outside the intended functional change. Compare `dependency:resolve`/`dependency:tree` and exclude accidental differences.
-- Library APIs may define enum types and accept enum parameters, but should not return enum values or POJOs containing enum values across external library boundaries.
-- Define one version variable for a group of related libraries to avoid version drift.
-- Do not declare the same `GroupId` and `ArtifactId` with different versions across subprojects.
-
-Recommended/reference:
-
-- Put dependency declarations under `<dependencies>` and version mediation under `<dependencyManagement>`.
-- Avoid adding configuration items to reusable libraries unless truly necessary.
-- Library publishers should keep APIs/dependencies minimal and behavior stable/traceable.
-
-## Server And JVM
-
-Recommended/reference:
-
-- For high-concurrency servers, reduce TCP `time_wait` timeout where operations policy allows.
-- Increase maximum file descriptors for high concurrent connection counts.
-- Set `-XX:+HeapDumpOnOutOfMemoryError` so OOM events produce diagnostic dumps.
-- In production, set JVM `Xms` and `Xmx` to the same size to avoid heap resizing pressure after GC.
-- Use `forward` for internal redirects. Generate external redirect URLs through URL builder utilities to avoid inconsistent maintenance and potential security risk.
-
-## Design Rules
-
-Mandatory:
-
-- Storage schemes and base data structures must pass review and be documented before production execution. Data structure changes such as adding fields also need review.
-- If more than one user type interacts with the system and related use cases exceed 5, use a use-case diagram.
-- If a business object's states exceed 3, use a state diagram and define trigger conditions for state transitions.
-- If a feature call chain involves more than 3 objects, use a sequence diagram and define inputs/outputs at each call.
-- If model classes exceed 5 and dependencies are complex, use a class diagram.
-- If more than 2 objects collaborate and the process is complex, use an activity diagram with swimlanes where useful.
-
-Recommended/reference:
-
-- Consider exception flows and business boundaries during requirements analysis and system design.
-- Classes should follow single responsibility.
-- Prefer composition/aggregation over inheritance. If inheritance is necessary, obey Liskov substitution.
-- Depend on abstractions and interfaces where it improves extension and maintenance.
-- Design for extension and closed modification in stable business domains.
-- Extract common business behavior or public behavior into shared modules, config, classes, or methods to avoid duplicated code/config.
-- Do not treat agile as only stories plus coding plus release; keep necessary design and documentation for key decisions.
-- Design identifies hard parts, variation points, boundaries, module relations, evolution principles, and nonfunctional requirements such as security, availability, and extensibility.