create-yss-spec 3.3.1 → 3.3.4

package/template/.claude/skills/yss-ui-business-page-generation/references/component-map.md

@@ -1,39 +0,0 @@
-# YSS UI 组件来源速查
-
-此文件用于业务页面生成前的组件选型。优先使用 YSS UI 已封装组件；未封装能力再从 `ant-design-vue` 导入。
-
-## 从 `@yss-ui/components` 导入
-
-| 组件 | 适用场景 | 备注 |
-| --- | --- | --- |
-| `YButton` | 操作按钮、权限按钮 | 支持 `permissionCode`、`fallback`、`modifiers`；优先替代 `a-button`。 |
-| `YCard` | 页面容器、区域容器 | 支持 `title`、`extra`、`padding`、Meta 插槽。 |
-| `YTable` | 标准列表、分页、操作列、筛选、字典翻译 | 继承 vxe-table 能力，分页用 AntDV Pagination。 |
-| `YEditTable` | 可编辑表格 | 需要底部添加按钮高度时配合 `useTableHeight(tableAreaRef, { withAddButton: true })`。 |
-| `YTree` | 左侧分类树、组织树、搜索过滤树 | 节点操作用 `getNodeActions`。 |
-| `YSplitPane` | 左树右表、可拖拽分割布局 | 左右或上下区域分割。 |
-| `YFormily` | JSON Schema 表单、新增/编辑/查看 | 默认表单方案。 |
-| `YssFormily` | 表单兼容导出 | 仅用于维护历史代码；新代码统一使用 `YFormily`。 |
-| `YConditionBuilder` | 条件构建器、规则配置 | 常用于数据质量、筛选条件配置。 |
-| `YFileImport` | 文件导入 | Formily schema 内也可用 `YFileImport`。 |
-| `YMonaco` | 代码编辑器 | SQL、JSON、脚本编辑。 |
-| `YMonacoDiff` | 代码 Diff | 变更对比场景。 |
-| `YCron` | Cron 表达式编辑 | 定时任务配置。 |
-| `YMonthCalendar` | 月度日历、节假日和连续区间 | 支持单元格、右键菜单和头部插槽。 |
-| `YEcharts` | 图表展示 | 业务图表封装。 |
-| `YSheet` | 协同/类 Excel 表格 | 复杂表格编辑。 |
-| `AuthorityDropdown` | 权限相关下拉 | 可从 `@yss-ui/components` 导入；全局安装后也注册了 `YDropdown` 组件名别名。 |
-
-## 回退到 `ant-design-vue`
-
-`@yss-ui/components` 未导出的组件不要臆造 Y 前缀，应直接从 `ant-design-vue` 导入：
-
-- `Modal`、`Drawer`、`Popconfirm`
-- `Input`、`Select`、`Switch`、`DatePicker`、`Tag`
-- `Steps`、`Tabs`、`Space`、`Tooltip`
-- `message`、`notification`
-
-## 禁止规则
-
-- 不要编造未导出的 Y 前缀组件；弹窗、抽屉、输入框等未封装能力直接从 `ant-design-vue` 导入。
-- 业务层不要从 `@formily/antdv` 导入 `FormItem`、`Input` 等 UI 适配组件。

package/template/.claude/skills/yss-ui-business-page-generation/references/hooks-map.md

@@ -1,70 +0,0 @@
-# YSS UI Hooks 速查
-
-业务页面生成时优先从 `@yss-ui/hooks` 复用以下 hooks。
-
-## useTableHeight
-
-```ts
-const tableAreaRef = ref<HTMLDivElement>();
-const { tableHeight, isReady, recalculateHeight } = useTableHeight(tableAreaRef, {
-  withPagination: true,
-  withToolbar: true,
-  withAddButton: false,
-  extraOffset: 16,
-});
-```
-
-- 必须传入表格父容器 `ref`。
-- 返回值是 `recalculateHeight`，不要使用旧的错误返回名。
-- 可选项：`boundaryRef`、`minHeight`、`defaultHeight`、`extraOffset`、`withPagination`、`withToolbar`、`withAddButton`、`paginationHeight`、`toolbarHeight`、`addButtonHeight`。
-
-## useTreeHeight
-
-```ts
-const treeAreaRef = ref<HTMLDivElement>();
-const { treeHeight, recalculateHeight } = useTreeHeight(treeAreaRef, {
-  extraOffset: YTREE_SEARCH_HEIGHT + 16,
-});
-```
-
-- 必须传入树区域父容器 `ref`。
-- 搜索树可引入 `YTREE_SEARCH_HEIGHT`。
-
-## useLoading
-
-```ts
-const { loading, withLoading, setLoading, toggleLoading } = useLoading();
-
-await withLoading(fetchData);
-```
-
-- 默认捕获错误，避免未处理 Promise rejection。
-- 需要外层捕获时设置 `rethrowError: true`。
-- Orval API 的业务错误和 HTTP/网络错误已由 mutator 提示，禁止在 `onError` 重复 `message.error`。
-- `onError` 只用于更新局部错误状态、上报或处理非 mutator 任务；如要自定义 API 错误交互，必须先显式传入 `skipBusinessError`/`skipErrorHandler`。
-
-## usePollingTask
-
-```ts
-const { start, stop, restart, runNow, isActive, isRunning } = usePollingTask(
-  async ({ signal, isCurrent }) => {
-    const res = await fetch('/api/list', { signal });
-    if (!isCurrent()) return;
-    return res.json();
-  },
-  { interval: 3000, pauseWhenHidden: true }
-);
-```
-
-- 只负责轮询调度，不接管业务 `loading/data/error`。
-- 适合页面级静默刷新、任务状态轮询。
-
-## useUrlState
-
-- 用于把查询条件、分页、Tab 等状态同步到 URL。
-- 适合列表页返回恢复、分享链接保留筛选条件。
-
-## useFullscreen
-
-- 用于容器全屏、图表全屏、编辑器全屏。
-- 传入目标元素或目标 getter，按需配置退出提示。

package/template/.claude/skills/yss-ui-business-page-generation/references/utils-map.md

@@ -1,51 +0,0 @@
-# YSS UI Utils 速查
-
-业务页面生成时优先从 `@yss-ui/utils` 复用工具函数，避免重复实现。
-
-## 权限
-
-- `getAuthBtns(): AuthBtn[]`：读取当前按钮权限列表。
-- `hasAuth(code?: string): boolean`：判断权限码是否可用。
-- `getBtnInfo(code?: string): AuthBtn | null`：获取权限按钮信息。
-- `clearAuthInfo(): void`：清理权限信息。
-
-## 复制
-
-```ts
-const ok = await copyToClipboard(text);
-```
-
-- `copyToClipboard(text): Promise<boolean>`：复制文本到剪贴板。
-
-## 下载
-
-- `downloadFileStream(stream, fileName)`：下载 Blob/二进制流。
-- `getFileNameFromContentDisposition(contentDisposition?)`：从响应头解析 `filename*` 或 `filename`。
-- `handleBlobResponse(data, headers)`：处理 Blob 下载响应并根据 `Content-Disposition` 自动命名；第三个参数已弃用。
-- `downloadFileFromUrl(url, fileName?)`：按 URL 触发下载。
-
-接口导出下载必须读取 `../../file-export-download/SKILL.md`，优先调用 `handleBlobResponse(res.data, res.headers)`，禁止在业务层重复解析文件名和创建下载链接。
-
-当前微应用模板会统一解析 HTTP 4xx/5xx 的 Blob JSON 错误，但不会自动检测 HTTP 200 Blob 内的 `success === false`；发现后者时先修正后端状态码或 mutator，不在页面 Hook 重复解析与提示。
-
-## 格式化
-
-- `formatMoney(amount, precision?, separator?)`：金额格式化。
-- `formatDate(date, format?)`：日期格式化，默认 `YYYY-MM-DD HH:mm:ss`。
-- `formatFileSize(bytes, precision?)`：文件大小格式化。
-- `formatDateRelative(date)`：相对时间格式化。
-
-## 存储
-
-- `localStorage`：封装本地存储读写。
-- `sessionStorage`：封装会话存储读写。
-
-## 主题
-
-- `applyYssTheme(options)`：应用 YSS 主题变量。
-- `lightenColor(hex, factor?)`：颜色变亮。
-- `darkenColor(hex, factor?)`：颜色变暗。
-
-## URL
-
-- `getUrlData(url?, excludeKeys?)`：解析 URL 查询参数。

package/template/.claude/skills/yss-up-springboot3/SKILL.md

@@ -1,40 +0,0 @@
----
-name: yss-up-springboot3
-description: Use when YSS Spring Boot 3 / Spring Cloud 升级辅助技能。Use when auditing or migrating YSS backend services/components from Spring Boot 2.x or Spring Cloud 2021-era dependencies toward Spring Boot 3, Jakarta namespace, newer Spring Security, MyBatis, OpenFeign, gateway, validation, and related compatibility changes.
----
-
-# yss-up-springboot3
-
-Use this skill for YSS backend upgrade analysis and migration tasks around Spring Boot 3 / Spring Cloud compatibility.
-
-中文说明：这个技能是升级核查入口，不替代具体组件技能。遇到缓存、审计、MyBatis、DTO、Excel、JDBC 等组件细节时，应同时读取对应专项技能和源码索引。
-
-## When To Use
-
-- The user asks to upgrade YSS backend code to Spring Boot 3 or newer Spring Cloud baselines.
-- The task mentions `javax.*` to `jakarta.*`, Spring Security migration, validation changes, Servlet API changes, Gateway/OpenFeign compatibility, or dependency BOM changes.
-- The task involves checking whether a YSS component can run on Spring Boot 3.
-
-## Workflow
-
-1. Identify affected modules and current dependency versions from the local repository.
-2. Check for Jakarta namespace changes (`javax.servlet`, `javax.validation`, `javax.annotation`, JPA APIs, and related imports).
-3. Check Spring Security configuration style, deprecated adapters, authorization server dependencies, and filter registration behavior.
-4. Check component-specific integration by loading specialist skills such as `yss-mybatis`, `yss-dto`, `yss-cache`, `yss-audit-log`, `yss-excel-mvc`, or `yss-jdbc`.
-5. Prefer source-backed evidence from the local workspace or a source root resolved via `yss-skill-source-index-refresh/references/source-location.md` before recommending code changes.
-6. Produce an upgrade checklist or patch with explicit compatibility risks and verification commands.
-
-## Common Checks
-
-- Maven BOM and plugin versions are aligned before changing code.
-- `javax.*` imports are migrated only where the target framework expects Jakarta APIs.
-- Spring Security configuration no longer depends on removed `WebSecurityConfigurerAdapter` patterns.
-- Validation annotations and exception handlers still map to the expected DTO/Result contract.
-- MyBatis interceptors, auto configurations, and starter metadata are compatible with Spring Boot 3 auto-configuration loading.
-- Tests or sample modules are updated together with framework code.
-
-## Do Not
-
-- Do not blindly rewrite all `javax.*` imports without checking whether the dependency still uses the old namespace.
-- Do not mix unrelated business refactors into migration patches.
-- Do not assume component compatibility from memory; inspect source and specialist skill indexes.

package/template/.claude/skills/yss-up-springboot3/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "YSS Spring Boot 3 Upgrade"
-  short_description: "YSS 后端 Spring Boot 3 升级核查"
-  default_prompt: "Use $yss-up-springboot3 to audit a YSS backend module for Spring Boot 3 compatibility."

package/template/.claude/skills/yss-use-table-height/SKILL.md

@@ -1,130 +0,0 @@
----
-name: yss-use-table-height
-description: 指导 YTable、YEditTable、左树右表、分页列表、工具栏表格和弹窗/抽屉内表格使用 @yss-ui/hooks 的 useTableHeight 实现稳定自适应高度；当需要避免双滚动条、底部空白、容器撑开闪烁，或需要计入分页、工具栏、添加按钮偏移时使用。
----
-
-# useTableHeight 使用
-
-## 触发条件
-
-- YTable/YEditTable 需要自适应滚动高度，或页面出现双滚动条、底部空白和容器撑开闪烁。
-- 表格内含分页、工具栏、添加按钮，或位于弹窗/抽屉/shrink-wrap 容器内。
-
-## 不适用场景
-
-- 纯短表且页面不需要独立滚动区。
-- 当前布局组件已完整托管表格高度，且没有内部偏移需要扣减。
-
-## 实施流程
-
-1. MCP 可用时，先用 `get_component_docs` 精确查询 `useTableHeight`，需要示例时再调用 `get_demo`；不要仅凭 Skill 中的静态签名推断当前 API。
-2. 精确查询无结果时，先用 `search_docs` 校正名称；仅在 MCP 不可用、调用失败或仍无结果时，回退读取最新 `llms-full.txt`。文档版本与当前依赖不一致时，再核对 Hook 源码、CodeGraph 和真实导出。
-3. 先确认容器是稳定 flex 区域还是被表格内容撑开的 shrink-wrap 区域。
-4. 盘点表格内部实际开启的分页、工具栏、YEditTable 添加按钮和额外 padding。
-5. 把受约束的容器 `ref` 传给 Hook，将 `tableHeight` 绑定到表格 `height`。
-6. 在弹窗/抽屉动画结束或布局切换后视情况调用 `recalculateHeight()` 验证最终高度。
-
-## 硬约束（禁止/必须）
-
-- 使用真实签名 `useTableHeight(tableAreaRef, options)` 和真实返回值 `tableHeight/isReady/recalculateHeight`。
-- `tableAreaRef` 支持原生 DOM 或 Vue 组件实例（如 `YCard`）。绑定 DOM 时使用表格的直接父容器；绑定 Card 时 Hook 会尝试获取 `.ant-card-body`。
-- 稳定布局使用“外层可计算高度 + flex column，表格区 `flex: 1; min-height: 0; overflow: hidden`”。禁止用大常量高度替代 Hook。
-- YTable 开启 `pageable` 时设置 `withPagination: true`；开启 `toolbarConfig.custom` 或工具栏插槽时设置 `withToolbar: true`；YEditTable 显示 `addable` 按钮时设置 `withAddButton: true`。
-- 默认偏移常量分别是分页 48px、工具栏 48px、添加按钮 40px；只在实际样式不同时使用 `paginationHeight/toolbarHeight/addButtonHeight` 覆盖。
-- 把结果绑定到 `YTable/YEditTable` 的 `:height="tableHeight"`，不只设置 `max-height`。
-- 直属容器由表格内容撑开时，不要观察该容器形成“子元素改变父高度、父高度又改变子元素”循环；传入更外层稳定容器 `boundaryRef`，并用 `extraOffset` 扣除边界内其他区域。
-- Hook 已用 `ResizeObserver` 监听容器尺寸。不强制为每个弹窗/抽屉写 watch；只在动画或隐藏初始化导致高度不准时，于可见后 `nextTick(recalculateHeight)`。
-
-## 标准代码骨架
-
-```vue
-<script setup lang="ts">
-import { ref } from 'vue';
-import { YTable, type YTableColumn } from '@yss-ui/components';
-import { useTableHeight } from '@yss-ui/hooks';
-
-const tableAreaRef = ref<HTMLDivElement>();
-const dataList = ref<Array<{ id: string; name: string }>>([]);
-const columns: YTableColumn[] = [
-  { type: 'seq', title: '序号', width: 70 },
-  { field: 'name', title: '名称', minWidth: 180 },
-];
-const { tableHeight, isReady, recalculateHeight } = useTableHeight(tableAreaRef, {
-  withPagination: true,
-  withToolbar: true,
-});
-</script>
-
-<template>
-  <div class="page">
-    <div ref="tableAreaRef" class="table-area">
-      <YTable
-        v-if="isReady"
-        :height="tableHeight"
-        :data="dataList"
-        :columns="columns"
-        :toolbar-config="{ custom: true }"
-        pageable
-      />
-    </div>
-  </div>
-</template>
-
-<style scoped lang="less">
-@import './style.less';
-</style>
-```
-
-```less
-/* style.less */
-.page {
-  height: 100%;
-  display: flex;
-  flex-direction: column;
-}
-
-.table-area {
-  flex: 1;
-  min-height: 0;
-  overflow: hidden;
-}
-```
-
-## shrink-wrap 容器
-
-```typescript
-const tableAreaRef = ref<HTMLDivElement>();
-const boundaryRef = ref<HTMLDivElement>();
-
-const { tableHeight } = useTableHeight(tableAreaRef, {
-  boundaryRef,
-});
-```
-
-`extraOffset` 必须来自可说明的实际布局占位；如果区域高度会变，优先改成稳定 flex 布局，不固定一个近似大数。
-
-## 弹层可见后补算
-
-```typescript
-import { nextTick } from 'vue';
-
-/** 弹层完全展开后重算表格高度。 */
-const handleAfterOpenChange = async (open: boolean) => {
-  if (!open) return;
-  await nextTick();
-  recalculateHeight();
-};
-```
-
-## 交付检查清单
-
-- [ ] 观察容器具有稳定高度，需要时已使用 `boundaryRef`。
-- [ ] 分页、工具栏、添加按钮的偏移与实际开关一致，未重复扣减。
-- [ ] 表格绑定 `height`，容器有 `min-height: 0`，无双滚动条和底部大空白。
-- [ ] 只在实际出现隐藏态/动画时机问题时手动调用 `recalculateHeight()`。
-
-## 失败兜底策略
-
-- 高度持续闪烁时，检查被观察容器是否由表格内容撑开；是则使用稳定 `boundaryRef` 或改为 flex 布局。
-- 底部空白或内容被遮挡时，逐项核对 `withPagination/withToolbar/withAddButton` 与实际开关，不反复调大 `extraOffset`。
-- 弹层首次打开高度不准时，在可见或动画结束后 `nextTick(recalculateHeight)`；正常 ResizeObserver 已生效时不增加重复 watch。

package/template/.claude/skills/yss-use-table-height/agents/openai.yaml

@@ -1,5 +0,0 @@
-version: 1
-interface:
-  display_name: "YSS Table Height"
-  short_description: "YTable 自适应高度计算、分页偏移与布局处理规范"
-  default_prompt: "Use $yss-use-table-height to wire a responsive table height calculation for a YSS page."

package/template/.claude/skills/yss-use-table-height/references/frontend-docs.md

@@ -1,9 +0,0 @@
-# yss-use-table-height Frontend Documentation
-
-Generated: 2026-08-17T12:03:37.436Z
-
-Use these YSS UI documentation entry points as authoritative references when local repo examples are insufficient.
-
-- hooks: http://192.168.164.27:3200/hooks
-
-When documentation and local code differ, inspect the current project code before editing and prefer established local usage.

package/template/.claude/skills/yss-use-tree-height/SKILL.md

@@ -1,98 +0,0 @@
----
-name: yss-use-tree-height
-description: 指导 YTree、左树右表、组织树、分类树、树搜索和 Tab/抽屉内树区域使用 @yss-ui/hooks 的 useTreeHeight 实现自适应高度；当树区域需要独立滚动、容器切换后高度不正确或需要扣除 YTree 内置搜索高度时使用。
----
-
-# useTreeHeight 使用
-
-## 触发条件
-
-- YTree 或左树右表需要独立滚动区和自适应高度。
-- 树区域含内置搜索，或在 Tab/抽屉/折叠面板切换后高度不正确。
-
-## 不适用场景
-
-- 树节点很少、无需独立滚动，且父级布局已托管高度。
-- 主要问题是树节点与右侧数据联动，而非布局高度。
-
-## 文档检索
-
-1. MCP 可用时，先用 `get_component_docs` 精确查询 `useTreeHeight`，需要示例时再调用 `get_demo`；不要仅凭 Skill 中的静态签名推断当前 API。
-2. 精确查询无结果时，先用 `search_docs` 校正名称；仅在 MCP 不可用、调用失败或仍无结果时，回退读取最新 `llms-full.txt`。文档版本与当前依赖不一致时，再核对 Hook 源码、CodeGraph 和真实导出。
-
-## 硬约束（禁止/必须）
-
-- 把树区域的直接父容器 `ref` 传给 `useTreeHeight(treeAreaRef, options)`，并使用真实返回值 `treeHeight/recalculateHeight`。
-- 最外层必须有可计算高度；树区域使用 `flex: 1; min-height: 0; overflow: hidden;`。
-- 计算结果绑定到 `YTree` 的 `:height="treeHeight"`，不用固定魔法高度替代 Hook，也不为了触发虚拟滚动默认添加 `:virtual="true"`。
-- 使用 YTree 内置搜索时配置 `extraOffset: YTREE_SEARCH_HEIGHT`；搜索区已放在 `treeAreaRef` 外部时不再扣除。
-- `extraOffset` 只用于树区域内部实际占位的搜索、padding 或边框，禁止无依据叠加 `+16` 等偏移。
-- Hook 仅在挂载时为当时存在的 `treeAreaRef` 建立 `ResizeObserver`。优先保持树区域外层容器挂载（如使用 `v-show`）；Tab/抽屉可见后在 `nextTick` 调用 `recalculateHeight()`。
-- 隐藏态容器可能得到 `minHeight` 而不是真实可用高度；不把该值当成最终布局结果。
-
-## 标准代码骨架
-
-```vue
-<script setup lang="ts">
-import { ref } from 'vue';
-import { YTree } from '@yss-ui/components';
-import { useTreeHeight, YTREE_SEARCH_HEIGHT } from '@yss-ui/hooks';
-
-const treeAreaRef = ref<HTMLDivElement>();
-const treeData = ref([]);
-const { treeHeight, recalculateHeight } = useTreeHeight(treeAreaRef, {
-  extraOffset: YTREE_SEARCH_HEIGHT,
-});
-</script>
-
-<template>
-  <div ref="treeAreaRef" class="tree-area">
-    <YTree :height="treeHeight" :tree-data="treeData" filterable />
-  </div>
-</template>
-
-<style scoped lang="less">
-@import './style.less';
-</style>
-```
-
-```less
-/* style.less */
-.tree-layout {
-  height: 100%;
-  display: flex;
-  flex-direction: column;
-}
-
-.tree-area {
-  flex: 1;
-  min-height: 0;
-  overflow: hidden;
-}
-```
-
-## 容器切换时机
-
-```typescript
-import { nextTick } from 'vue';
-
-/** 容器显示后补充一次高度计算。 */
-const handleVisibleChange = async (visible: boolean) => {
-  if (!visible) return;
-  await nextTick();
-  recalculateHeight();
-};
-```
-
-## 交付检查清单
-
-- [ ] `treeAreaRef` 在 Hook 挂载时可用，父级高度可计算。
-- [ ] 内置搜索开关与 `YTREE_SEARCH_HEIGHT` 偏移一致，没有重复扣减。
-- [ ] Tab/抽屉切换后使用真实的 `recalculateHeight()` 重算。
-- [ ] 节点较少时未裁剪 DOM 被识别为正常虚拟滚动阈值行为。
-
-## 失败兜底策略
-
-- 树高度显示为 `minHeight` 且与容器不符时，检查是否在隐藏态完成首次计算，并在可见后重算。
-- `treeAreaRef` 由 `v-if` 延迟创建且尺寸不再自动更新时，保持外层容器挂载后重新初始化 Hook，或使用 `v-show + recalculateHeight()`。
-- 节点较少未触发 DOM 裁剪时，核对虚拟滚动阈值，不加 `virtual=true` 伪装修复。

package/template/.claude/skills/yss-use-tree-height/agents/openai.yaml

@@ -1,5 +0,0 @@
-version: 1
-interface:
-  display_name: "YSS Tree Height"
-  short_description: "YTree 自适应高度计算、搜索偏移与布局处理规范"
-  default_prompt: "Use $yss-use-tree-height to wire a responsive tree height calculation for a YSS page."

package/template/.claude/skills/yss-use-tree-height/references/frontend-docs.md

@@ -1,9 +0,0 @@
-# yss-use-tree-height Frontend Documentation
-
-Generated: 2026-08-17T12:03:37.436Z
-
-Use these YSS UI documentation entry points as authoritative references when local repo examples are insufficient.
-
-- hooks: http://192.168.164.27:3200/hooks
-
-When documentation and local code differ, inspect the current project code before editing and prefer established local usage.

package/template/.claude/skills/yss-userinfo/SKILL.md

@@ -1,49 +0,0 @@
----
-name: yss-userinfo
-description: Use when YSS current-user context, `AuthUserInfoUtil`, propagated user headers, JWT user payloads, Redis user cache, or background-user fallback is involved.
----
-
-# yss-userinfo
-
-Use this skill for YSS 用户信息组件. Keep implementation grounded in the local project and resolvable YSS backend component source.
-
-中文说明：本技能用于 YSS 用户信息组件。执行时优先读取源码索引，避免凭记忆猜类名、配置项或接入方式。
-
-## Source Index First
-
-- Backend source location is environment-specific; resolve it with `yss-skill-source-index-refresh/references/source-location.md`.
-- Generated index: `references/source-index.md`
-- Component path hints: `yss-microservice-components/yss-component-userinfo-starter`
-
-Read `references/source-index.md` as a path-hint index whenever the task depends on exact modules, annotations, auto configuration, properties, controllers, clients, repositories, DTOs, handlers, or troubleshooting.
-
-## Workflow
-
-1. Identify whether the task is current-user lookup, request header propagation, JWT parsing, Redis user cache lookup, or non-REST/background fallback behavior.
-2. Read `references/source-index.md`, then inspect `AuthUserInfoUtil`, `DmUser`, and `DmUserDetails`.
-3. Prefer `AuthUserInfoUtil.userInfo()`, `userName()`, `userCode()`, or `currentUserJson()` over manually parsing headers in business code, but treat the result as propagated context, not as JWT signature verification.
-4. Check lookup order before debugging: `X-Username`/`X-Usercode`/`X-LoginDisplayName` headers, Bearer JWT payload, then Redis cache via `CacheManagerCompose`.
-5. For scheduled/background tasks, expect fallback behavior such as default `system` user unless the caller explicitly provides context.
-
-## Source-Backed Notes
-
-- Header names include `X-Username`, `X-Usercode`, and `X-LoginDisplayName`.
-- Bearer token parsing reads payload fields such as `sub`, `loginDisplayName`, `email`, and `userCode` without verifying signature/issuer/audience/expiry in this utility. Authentication decisions must use a verified security context.
-- The current source has a known reversed `userCode` header assignment condition; do not claim that header path is reliable until fixed and tested.
-- Redis cache lookup uses the JWT user-info cache key path; load `yss-cache` if changing cache behavior.
-
-## Checklist
-
-- Required dependency or starter module is present.
-- Request context exists before relying on servlet headers.
-- Gateway/auth service forwards expected user headers or Authorization token.
-- Cache fallback is checked when headers exist but detailed user info is incomplete.
-- Business code does not duplicate JWT parsing logic.
-- Header/JWT/cache/background precedence and overwrite behavior are covered by tests; `system` fallback is distinguished from an authenticated system user.
-- User info propagation is tested for REST calls and async/background execution separately.
-
-## Do Not
-
-- Do not invent class names or configuration keys without checking the source index.
-- Do not replace component extension points with business-local framework code.
-- Do not broaden the task into unrelated YSS components unless the user asks.

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

@@ -1,4 +0,0 @@
-interface:
-  display_name: "yss-userinfo"
-  short_description: "YSS component skill for yss-userinfo"
-  default_prompt: "Use yss-userinfo for this YSS backend component task."

package/template/.claude/skills/yss-userinfo/references/source-index.md

@@ -1,34 +0,0 @@
-# yss-userinfo Source Index
-
-Generated: 2026-08-17T12:03:37.436Z
-Source commit: `38b556a5081e6c66c0c538cbc1ef839b19996ed3`
-Source worktree: `dirty`
-Indexed source root: resolved at refresh time; set `YSS_SOURCE_ROOT` to reproduce or refresh.
-
-This file is generated by `yss-skill-source-index-refresh/scripts/refresh-yss-skill-index.mjs`. Do not hand-edit generated sections.
-
-Paths below are source path hints captured at refresh time. If they do not exist in the current workspace, locate sources using `YSS_SOURCE_ROOT`, CodeGraph, package/class names, Maven artifact names, or repository search before assuming the source is unavailable.
-
-## Component Path Hints
-
-- `yss-microservice-components/yss-component-userinfo-starter` (existed when indexed)
-
-## Documentation Files
-
-- No component documentation files found.
-
-## Maven Modules
-
-- `yss-microservice-components/yss-component-userinfo-starter`
-
-## Key Java Entry Points
-
-- `yss-microservice-components/yss-component-userinfo-starter/src/main/java/com/yss/cloud/domain/DmUser.java`
-- `yss-microservice-components/yss-component-userinfo-starter/src/main/java/com/yss/cloud/domain/DmUserDetails.java`
-- `yss-microservice-components/yss-component-userinfo-starter/src/main/java/com/yss/cloud/user/AuthUserInfoUtil.java`
-
-## Recommended Next Reads
-
-- Start with the documentation files above when learning component usage.
-- Search the key Java entry points for annotations, auto configuration, properties, aspects, interceptors, handlers, and result objects before changing application code.
-- Prefer existing component extension points over rewriting framework logic in business modules.

package/template/.claude/skills/yss-validation/SKILL.md

@@ -1,57 +0,0 @@
----
-name: yss-validation
-description: Use when YSS Bean Validation/JSR-303 dependencies, validation messages, LiteFlow EL parsing, `ExpressParserFactory`, parser registration, or validation-error mapping is involved.
----
-
-# yss-validation
-
-Use this skill for YSS 校验组件. Keep implementation grounded in the local project and resolvable YSS backend component source.
-
-中文说明：本技能用于 YSS 校验组件。执行时优先读取源码索引，避免凭记忆猜类名、配置项或接入方式。
-
-## Source Index First
-
-- Backend source location is environment-specific; resolve it with `yss-skill-source-index-refresh/references/source-location.md`.
-- Generated index: `references/source-index.md`
-- Component path hints: `yss-microservice-components/yss-component-validation-engine-parent`, `yss-microservice-components/yss-component-validation-jsr303`
-
-Read `references/source-index.md` as a path-hint index whenever the task depends on exact modules, annotations, auto configuration, properties, controllers, clients, repositories, DTOs, handlers, or troubleshooting.
-
-## Workflow
-
-1. Identify whether the task is JSR-303 annotation validation, validation engine expression parsing, LiteFlow EL parsing, or parser extension.
-2. Read `references/source-index.md`; for JSR-303 behavior, read `yss-component-validation-jsr303/readme.md` first.
-3. For expression parsing, inspect `ExpressParserFactory` and concrete `ExpressParser` implementations before adding syntax.
-4. Register new parsers as Spring beans; `ExpressParserFactory` auto-registers available parser beans by `parserType().getType()`.
-5. Keep validation failures mapped to the service/API error contract used by the local project.
-6. 消费工程基线选择 javax/jakarta，不自行升级 Java/Boot。MVC 输入校验放在 server/client，业务不变量由 service/core 验证；不生成 DDD Domain。HTTP 失败形态由 server 的合同测试验证。
-
-## Capability Split
-
-- `validation-jsr303`: currently a dependency/message-resource aggregation module; it has no local Validator, Advice, or auto-configuration Java implementation.
-- `validation-el-parser`: LiteFlow/EL expression parser infrastructure.
-- `ExpressParserFactory`: central parser registry backed by a concurrent map.
-- Parser extension point: implement/provide `ExpressParser` with a non-null parser type and register it as a bean.
-
-## Troubleshooting Notes
-
-- If a parser is not found, confirm it is a Spring bean and `parserType()` is non-null.
-- If validation annotations do not fire, check controller/service validation annotations and Spring validation starter wiring before editing parser code.
-- The component README is empty; use the POM, message resources, Controller annotations, and `GlobalExceptionAdvice` as current evidence.
-- Duplicate parser type keys are silently overwritten by `PARSER_MAP.put`; require collision and round-trip tests for extensions.
-- If behavior differs between expression validation and DTO validation, route the problem to the correct submodule first.
-
-## Checklist
-
-- Required dependency or starter module is present.
-- JSR-303 and expression validation concerns are not mixed in the same fix.
-- New parser implementations have deterministic parser type keys.
-- Parser registration is verified through `ExpressParserFactory.PARSER_MAP`.
-- Validation errors preserve readable messages for Chinese business users.
-- Existing project conventions are reused before adding new wrappers.
-
-## Do Not
-
-- Do not invent class names or configuration keys without checking the source index.
-- Do not replace component extension points with business-local framework code.
-- Do not broaden the task into unrelated YSS components unless the user asks.

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

@@ -1,4 +0,0 @@
-interface:
-  display_name: "yss-validation"
-  short_description: "YSS component skill for yss-validation"
-  default_prompt: "Use yss-validation for this YSS backend component task."

package/template/.claude/skills/yss-validation/references/source-index.md

@@ -1,33 +0,0 @@
-# yss-validation Source Index
-
-Generated: 2026-08-17T12:03:37.436Z
-Source commit: `38b556a5081e6c66c0c538cbc1ef839b19996ed3`
-Source worktree: `dirty`
-Indexed source root: resolved at refresh time; set `YSS_SOURCE_ROOT` to reproduce or refresh.
-
-This file is generated by `yss-skill-source-index-refresh/scripts/refresh-yss-skill-index.mjs`. Do not hand-edit generated sections.
-
-Paths below are source path hints captured at refresh time. If they do not exist in the current workspace, locate sources using `YSS_SOURCE_ROOT`, CodeGraph, package/class names, Maven artifact names, or repository search before assuming the source is unavailable.
-
-## Component Path Hints
-
-- `yss-microservice-components/yss-component-validation-engine-parent` (missing when indexed)
-- `yss-microservice-components/yss-component-validation-jsr303` (existed when indexed)
-
-## Documentation Files
-
-- `yss-microservice-components/yss-component-validation-jsr303/readme.md`
-
-## Maven Modules
-
-- `yss-microservice-components/yss-component-validation-jsr303`
-
-## Key Java Entry Points
-
-- No key Java entry points matched the configured name patterns.
-
-## Recommended Next Reads
-
-- Start with the documentation files above when learning component usage.
-- Search the key Java entry points for annotations, auto configuration, properties, aspects, interceptors, handlers, and result objects before changing application code.
-- Prefer existing component extension points over rewriting framework logic in business modules.