@teamix-evo/skills 0.3.0 → 0.4.0

package/manifest.json

@@ -2,7 +2,7 @@
   "$schema": "https://teamix-evo.dev/schema/skills-package/v1.json",
   "schemaVersion": 1,
   "package": "skills",
-  "version": "0.2.0",
+  "version": "0.3.0",
   "engines": {
     "teamix-evo": ">=0.1.0"
   },
@@ -10,69 +10,85 @@
     {
       "id": "teamix-evo-manage",
       "name": "teamix-evo-manage",
-      "description": "Manage the teamix-evo toolkit lifecycle inside the current project — install, initialize, update, list, or uninstall design / skills / ui / biz-ui / templates packages.\nTRIGGER when: user runs or asks about CLI commands `teamix-evo design init|update|list|list-variants|uninstall`, `teamix-evo skills add|update|list|uninstall|sync|doctor`, `teamix-evo ui init|add|list`, `teamix-evo biz-ui add|list-variants`, `teamix-evo templates add|list-variants`; phrases like \"init teamix-evo\"、\"set up the design system\"、\"装一下 teamix-evo\"、\"升级 teamix-evo\"、\"卸载 teamix-evo\"、\"看看装了哪些 teamix-evo 资源\"、\"加业务组件\"、\"加页面模板\"; user touches `.teamix-evo/config.json` or `.teamix-evo/manifest.json`.\nSKIP: any content task — generating components, pages, services, or reviewing screens; changes to `src/` files, design tokens, or business logic. Those go to teamix-evo-coding-conventions or teamix-evo-design-rules. SKIP if the user is mid-flow inside an already-initialized project asking to \"新增页面 / 加按钮 / 调接口\" — that's coding work, not lifecycle. SKIP placeholder→real UI migration (\"升级 UI\"、\"接入真组件\"、\"replace placeholders\") — that's owned by teamix-evo-ui-upgrade.\nCoordinates with: teamix-evo-ui-upgrade (hand off the placeholder migration loop after `ui add` is in place); otherwise lifecycle is the entry point and precedes content skills rather than co-triggering.",
-      "version": "0.1.0",
-      "source": "skills/teamix-evo-manage",
-      "ides": ["qoder", "claude"],
+      "description": "Single entry point for the teamix-evo lifecycle: scaffold a new project, install the AI coding system into an existing repo, run / update / inspect / remove any teamix-evo package, and drive the placeholder→real UI migration loop after `npm create teamix-evo`.\nTRIGGER when: (CLI) user runs or asks about `teamix-evo tokens ...` / `teamix-evo skills ...` / `teamix-evo ui ...` / `teamix-evo biz-ui ...` / `teamix-evo templates ...` / `teamix-evo logs ...`, or `npm create teamix-evo` / `pnpm create teamix-evo`; (模糊初始化) \"初始化一个项目\"、\"初始化一个工程\"、\"初始化一个 teamix-evo 工程\"、\"初始化一个 Teamix Evo 项目\"、\"create a teamix-evo project\"、\"set up teamix-evo from scratch\"、\"new teamix-evo app\"; (具名变体初始化) \"初始化一个 opentrek 工程 / op 工程 / OpenTrek 项目 / 探索者项目\"、\"初始化一个云管 / 云管控制台 / 云管项目 / uni-manager 工程 / 云管工程\"、\"new opentrek/uni-manager project\"; (AI coding 接入) \"给现有仓库装 teamix-evo\"、\"现有项目装一下 skills + ui\"、\"接入 AI coding 体系\"、\"装 teamix-evo 进这个项目\"、\"add teamix-evo to existing repo\"、\"install AI coding system\"、\"接入 opentrek 研发体系\"、\"接入 op 研发体系\"、\"接入 OpenTrek 研发体系\"、\"接入 opentrek 研发系统\"、\"接入 op 研发系统\"、\"接入云管研发体系\"、\"接入云管研发系统\"、\"接入 uni-manager 研发体系\"、\"接入 uni-manager 研发系统\"、\"接入统一管理研发体系\"; (更新检测) \"升级 teamix-evo\"、\"看看哪些要升级\"、\"update teamix-evo\"、\"check what needs updating\"、\"refresh installed teamix-evo packages\"; (卸载 / 清单) \"卸载 teamix-evo\"、\"看看装了哪些 teamix-evo 资源\"、\"remove the design system\"、\"list installed\"; (placeholder→real 升级) \"升级 UI\"、\"接入真组件\"、\"替换 placeholder\"、\"upgrade UI\"、\"replace placeholders\"、\"swap in real components\"、\"make the UI real\", or user opens / edits `src/components/_placeholder/**`, project contains `.teamix-evo/create/pending-ui.json`, literal `@teamix-evo:placeholder` tag in code; (状态文件) user touches `.teamix-evo/config.json`、`.teamix-evo/manifest.json`、`.teamix-evo/create/pending-ui.json`.\nSKIP: any content task — generating components, pages, services, or reviewing screens; changes to `src/` files outside the migration loop, design tokens, or business logic. Those go to teamix-evo-code-opentrek or teamix-evo-design-opentrek. SKIP if the user is mid-flow inside an already-initialized project asking to \"新增页面 / 加按钮 / 调接口\" — that's coding work, not lifecycle. SKIP pure styling / token tweaks — those go to ESLint + `tokens.overrides.css`.\nCoordinates with: teamix-evo-design-opentrek (visual side after a screen is generated)、teamix-evo-code-opentrek (file placement / reuse rules) — manage is the entry point and precedes content skills, never co-triggers.",
+      "version": "0.2.0",
+      "source": "src/teamix-evo-manage",
+      "ides": [
+        "qoder",
+        "claude"
+      ],
       "updateStrategy": "managed",
-      "managedRegions": ["core"],
+      "managedRegions": [
+        "core"
+      ],
       "template": false
     },
     {
-      "id": "teamix-evo-design-rules",
-      "name": "teamix-evo-design-rules",
-      "description": "Apply teamix-evo design system rules when AI is asked to generate or review a full UI screen / page (variant-neutral baseline).\nTRIGGER when: user asks to \"新建 / 优化 / 重构 一个页面\"、\"做一个列表页 / 详情页 / 表单页 / 仪表盘\"、\"create / review / refactor a page、screen、dashboard、template\"; intent involves layout structure, page-level information density, or multi-component composition; file write under `src/pages/**` or `src/templates/**`.\nSKIP: single-component edits like \"加个按钮\"、\"改 input 的 label\"、\"调 card 的 padding\"、\"add a tooltip\" — those go to teamix-evo-coding-conventions; pure tokens / theme override edits — those go to ESLint and `tokens.overrides.css`; pure code refactor with no visual change; teamix-evo lifecycle commands — those go to teamix-evo-manage.\nCoordinates with: teamix-evo-design-rules-<variant> (always layered when same-named variant is installed in `.teamix-evo/design/pack.lock.json`); teamix-evo-coding-conventions (run alongside when the screen also creates new files).",
-      "version": "0.6.0",
-      "source": "skills/teamix-evo-design-rules",
-      "ides": ["qoder", "claude"],
+      "id": "teamix-evo-design-opentrek",
+      "name": "teamix-evo-design-opentrek",
+      "description": "Apply OpenTrek design system rules (philosophy, patterns, page-types, brand tone/voice, visual foundations) when AI generates or reviews a full UI screen / page in an OpenTrek-variant project.\nTRIGGER when: user asks to \"新建 / 优化 / 重构 一个页面\"、\"做一个列表页 / 详情页 / 表单页 / 仪表盘\"、\"create / review / refactor a page、screen、dashboard、template\"; intent involves layout structure, page-level information density, or multi-component composition; file write under `src/pages/**` or `src/templates/**`.\nSKIP: single-component edits like \"加个按钮\"、\"改 input 的 label\"; pure tokens/theme overrides; pure code refactor with no visual change; teamix-evo lifecycle commands (defer to teamix-evo-manage).\nCoordinates with: teamix-evo-code-opentrek (run alongside when the screen also creates new files).",
+      "version": "0.2.0",
+      "source": "src/teamix-evo-design-opentrek",
+      "variant": "opentrek",
+      "ides": [
+        "qoder",
+        "claude"
+      ],
       "updateStrategy": "managed",
-      "managedRegions": ["core"],
+      "managedRegions": [
+        "core"
+      ],
       "template": false
     },
     {
-      "id": "teamix-evo-design-rules-opentrek",
-      "name": "teamix-evo-design-rules-opentrek",
-      "description": "Apply OpenTrek brand-specific design rules (tone / voice / brand color usage) on top of the variant-neutral teamix-evo-design-rules baseline.\nTRIGGER when: teamix-evo-design-rules is triggering AND the project's `.teamix-evo/design/pack.lock.json` records `variant: \"opentrek\"`; tasks where brand voice, copywriting tone, or OpenTrek-specific brand color usage is in scope; phrases like \"OpenTrek 风格\"、\"沉稳 / 克制 的文案\"、\"按 OpenTrek 调性写空态 / 标题 / 引导\".\nSKIP: project does not have OpenTrek variant installed; tasks belonging to other variants (`uni-manager` etc.); single-component edits with no copy / brand concern; pure structural / layout decisions with no brand surface.\nCoordinates with: teamix-evo-design-rules (mandatory — this is an overlay, never standalone).",
-      "version": "0.1.0",
-      "source": "skills/teamix-evo-design-rules-opentrek",
+      "id": "teamix-evo-code-opentrek",
+      "name": "teamix-evo-code-opentrek",
+      "description": "Enforce teamix-evo coding conventions in OpenTrek-variant consumer apps — reuse-first against `@teamix-evo/ui` registry, API code under `src/services/`, `src/` layering and import boundaries.\nTRIGGER when: user asks to \"新增 / 重构 / 写一个\" 组件 / 页面 / 接口 / 钩子 / 工具 / hook; phrases like \"create a CRUD page\"、\"add an API call\"、\"extract a hook\"、\"refactor this fetch\"、\"调一下接口\"、\"加个组件\"、\"加个按钮\"; file write under `src/pages/**`、`src/components/**`、`src/services/**`、`src/hooks/**`; AI is about to write any new `.tsx` / `.ts` file in a teamix-evo-installed project.\nSKIP: pure visual / layout design questions about an already-existing screen with no code change (defer to teamix-evo-design-opentrek); teamix-evo lifecycle (init / update / uninstall) — those go to teamix-evo-manage; changes only to design tokens / styles / theme — those go to ESLint and `tokens.overrides.css`.\nCoordinates with: teamix-evo-design-opentrek (run alongside when the change also creates a UI screen — design handles the visual side, this skill handles file placement and reuse).",
+      "version": "0.2.0",
+      "source": "src/teamix-evo-code-opentrek",
       "variant": "opentrek",
-      "ides": ["qoder", "claude"],
+      "ides": [
+        "qoder",
+        "claude"
+      ],
       "updateStrategy": "managed",
-      "managedRegions": ["core"],
+      "managedRegions": [
+        "core"
+      ],
       "template": false
     },
     {
-      "id": "teamix-evo-design-rules-uni-manager",
-      "name": "teamix-evo-design-rules-uni-manager",
-      "description": "Apply cloud-management-specific design rules (AI scenarios A-G, danger ops, command center / topology patterns) on top of the variant-neutral teamix-evo-design-rules baseline.\nTRIGGER when: teamix-evo-design-rules is triggering AND the project's `.teamix-evo/design/pack.lock.json` records `variant: \"uni-manager\"`; tasks involving 云资源管理 / AI 副驾驶场景 / 高危删除 / 跨区域迁移 / 流量切换 / 指挥官大屏 / 拓扑感知 / 告警诊断; phrases like \"做一个云资源列表 / 大屏 / 命令面板 / 危险操作确认\"; file paths involving `cockpit / topology / cloud-resources / alarm`.\nSKIP: project does not have uni-manager variant installed; tasks belonging to other variants (`opentrek` etc.); pure non-cloud business pages even within a uni-manager project (defer to baseline rules only); single-component edits with no danger-op or scenario surface.\nCoordinates with: teamix-evo-design-rules (mandatory — this is an overlay, never standalone).",
-      "version": "0.1.0",
-      "source": "skills/teamix-evo-design-rules-uni-manager",
+      "id": "teamix-evo-design-uni-manager",
+      "name": "teamix-evo-design-uni-manager",
+      "description": "Apply Uni-Manager design system rules (philosophy, patterns, page-types, brand tone/voice, visual foundations) when AI generates or reviews a full UI screen / page in a Uni-Manager-variant project (专有云 / 混合云 / 云管平台 / hybrid cloud console).\nTRIGGER when: user asks to \"新建 / 优化 / 重构 一个页面\"、\"做一个列表页 / 详情页 / 表单页 / 仪表盘 / 控制台首页\"、\"create / review / refactor a page、screen、dashboard、console、admin template\"; intent involves layout structure, page-level information density, or multi-component composition for hybrid-cloud / multi-tenant / multi-region scenarios; file write under `src/pages/**` or `src/templates/**`.\nSKIP: single-component edits like \"加个按钮\"、\"改 input 的 label\"; pure tokens/theme overrides; pure code refactor with no visual change; teamix-evo lifecycle commands (defer to teamix-evo-manage).\nCoordinates with: teamix-evo-code-uni-manager (run alongside when the screen also creates new files).",
+      "version": "0.2.0",
+      "source": "src/teamix-evo-design-uni-manager",
       "variant": "uni-manager",
-      "ides": ["qoder", "claude"],
-      "updateStrategy": "managed",
-      "managedRegions": ["core"],
-      "template": false
-    },
-    {
-      "id": "teamix-evo-ui-upgrade",
-      "name": "teamix-evo-ui-upgrade",
-      "description": "Replace `_placeholder/` UI components with real `@teamix-evo/ui` registry entries in projects scaffolded by `npm create teamix-evo -- --preset console`.\nTRIGGER when: user asks to \"升级 UI\"、\"接入真组件\"、\"替换 placeholder\"、\"upgrade UI\"、\"replace placeholders\"、\"swap in real components\"、\"make the UI real\"; user opens / edits a file under `src/components/_placeholder/**`; project contains `.teamix-evo/create/pending-ui.json`; literal `@teamix-evo:placeholder` tag appears in a file the user is touching.\nSKIP: project has no `.teamix-evo/create/pending-ui.json` (placeholders already cleared or never installed); user wants to add a NEW component that isn't on the pending list (defer to teamix-evo-coding-conventions); user is editing component internals, not migrating; user is initializing / updating teamix-evo itself (defer to teamix-evo-manage).\nCoordinates with: teamix-evo-coding-conventions (touch only when migrating import sites — file placement and reuse rules apply); teamix-evo-manage (uses `teamix-evo ui add` under the hood — but this skill drives the migration loop).",
-      "version": "0.1.0",
-      "source": "skills/teamix-evo-ui-upgrade",
-      "ides": ["qoder", "claude"],
+      "ides": [
+        "qoder",
+        "claude"
+      ],
       "updateStrategy": "managed",
-      "managedRegions": ["core"],
+      "managedRegions": [
+        "core"
+      ],
       "template": false
     },
     {
-      "id": "teamix-evo-coding-conventions",
-      "name": "teamix-evo-coding-conventions",
-      "description": "Enforce teamix-evo coding conventions in consumer business apps — reuse-first against `@teamix-evo/ui` registry, API code under `src/services/`, `src/` layering and import boundaries.\nTRIGGER when: user asks to \"新增 / 重构 / 写一个\" 组件 / 页面 / 接口 / 钩子 / 工具 / hook; phrases like \"create a CRUD page\"、\"add an API call\"、\"extract a hook\"、\"refactor this fetch\"、\"调一下接口\"、\"加个组件\"、\"加个按钮\"; file write under `src/pages/**`、`src/components/**`、`src/services/**`、`src/hooks/**`; AI is about to write any new `.tsx` / `.ts` file in a teamix-evo-installed project.\nSKIP: pure visual / layout design questions about an already-existing screen with no code change (defer to teamix-evo-design-rules); teamix-evo lifecycle (init / update / uninstall) — those go to teamix-evo-manage; changes only to design tokens / styles / theme — those go to ESLint and `tokens.overrides.css`.\nCoordinates with: teamix-evo-design-rules (run alongside when the change also creates a UI screen — design-rules handles the visual side, this skill handles file placement and reuse).",
-      "version": "0.1.0",
-      "source": "skills/teamix-evo-coding-conventions",
-      "ides": ["qoder", "claude"],
+      "id": "teamix-evo-code-uni-manager",
+      "name": "teamix-evo-code-uni-manager",
+      "description": "Enforce teamix-evo coding conventions in uni-manager (hybrid-cloud / multi-tenant console) consumer apps — reuse-first against `@teamix-evo/ui` registry + `biz-ui/uni-manager` (um-topbar / CloudBadge), API code under `src/services/` with tenant / region context propagation, `src/` layering and import boundaries.\nTRIGGER when: user asks to \"新增 / 重构 / 写一个\" 组件 / 页面 / 接口 / 钩子 / 工具 / hook in a hybrid-cloud / 专有云 / 多租户 / 多区域 console; phrases like \"create a CRUD page\"、\"add an API call\"、\"extract a hook\"、\"refactor this fetch\"、\"调一下接口\"、\"加个组件\"、\"加个按钮\"; file write under `src/pages/**`、`src/components/**`、`src/services/**`、`src/hooks/**`; AI is about to write any new `.tsx` / `.ts` file in a teamix-evo-installed uni-manager-variant project.\nSKIP: pure visual / layout design questions about an already-existing screen with no code change (defer to teamix-evo-design-uni-manager); teamix-evo lifecycle (init / update / uninstall) — those go to teamix-evo-manage; changes only to design tokens / styles / theme — those go to ESLint and `tokens.overrides.css`.\nCoordinates with: teamix-evo-design-uni-manager (run alongside when the change also creates a UI screen — design handles the visual side, this skill handles file placement and reuse).",
+      "version": "0.2.0",
+      "source": "src/teamix-evo-code-uni-manager",
+      "variant": "uni-manager",
+      "ides": [
+        "qoder",
+        "claude"
+      ],
       "updateStrategy": "managed",
-      "managedRegions": ["core"],
+      "managedRegions": [
+        "core"
+      ],
       "template": false
     }
   ]

package/package.json

@@ -1,12 +1,12 @@
 {
   "name": "@teamix-evo/skills",
-  "version": "0.3.0",
+  "version": "0.4.0",
   "description": "Skills (AI IDE capabilities) for Teamix Evo",
   "type": "module",
   "files": [
     "manifest.json",
     "_data.json",
-    "skills",
+    "src",
     "_template"
   ],
   "devDependencies": {

package/{skills/teamix-evo-coding-conventions → src/teamix-evo-code-opentrek}/SKILL.md

@@ -1,15 +1,15 @@
 ---
-name: teamix-evo-coding-conventions
+name: teamix-evo-code-opentrek
 description: |
-  Enforce teamix-evo coding conventions in consumer business apps — reuse-first against `@teamix-evo/ui` registry, API code under `src/services/`, `src/` layering and import boundaries.
+  Enforce teamix-evo coding conventions in OpenTrek-variant consumer apps — reuse-first against `@teamix-evo/ui` registry, API code under `src/services/`, `src/` layering and import boundaries.
   TRIGGER when: user asks to "新增 / 重构 / 写一个" 组件 / 页面 / 接口 / 钩子 / 工具 / hook; phrases like "create a CRUD page"、"add an API call"、"extract a hook"、"refactor this fetch"、"调一下接口"、"加个组件"、"加个按钮"; file write under `src/pages/**`、`src/components/**`、`src/services/**`、`src/hooks/**`; AI is about to write any new `.tsx` / `.ts` file in a teamix-evo-installed project.
-  SKIP: pure visual / layout design questions about an already-existing screen with no code change (defer to teamix-evo-design-rules); teamix-evo lifecycle (init / update / uninstall) — those go to teamix-evo-manage; changes only to design tokens / styles / theme — those go to ESLint and `tokens.overrides.css`.
-  Coordinates with: teamix-evo-design-rules (run alongside when the change also creates a UI screen — design-rules handles the visual side, this skill handles file placement and reuse).
+  SKIP: pure visual / layout design questions about an already-existing screen with no code change (defer to teamix-evo-design-opentrek); teamix-evo lifecycle (init / update / uninstall) — those go to teamix-evo-manage; changes only to design tokens / styles / theme — those go to ESLint and `tokens.overrides.css`.
+  Coordinates with: teamix-evo-design-opentrek (run alongside when the change also creates a UI screen — design handles the visual side, this skill handles file placement and reuse).
 ---
 
-# teamix-evo-coding-conventions
+# teamix-evo-code-opentrek
 
-This skill bundles the **AI-readable engineering conventions** for consumer business apps that consume `@teamix-evo/*` packages. It complements [`teamix-evo-design-rules`](../teamix-evo-design-rules/SKILL.md) — design-rules tells AI *what a screen should look like*; this skill tells AI *where the code should live and what to reuse before writing new code*.
+This skill bundles the **AI-readable engineering conventions** for OpenTrek-variant consumer business apps that consume `@teamix-evo/*` packages. It complements [`teamix-evo-design-opentrek`](../teamix-evo-design-opentrek/SKILL.md) — design tells AI _what a screen should look like_; this skill tells AI _where the code should live and what to reuse before writing new code_.
 
 <!-- teamix-evo:managed:start id="core" -->
 
@@ -25,7 +25,7 @@ Activate this skill whenever AI is about to **write or refactor code** inside a
 - "add an API call to fetch users"
 - Any time AI is about to create a new file under `src/pages/`、`src/components/`、`src/services/`、`src/hooks/`
 
-If the task is purely about *visual design* of a screen (layout / colors / spacing), use [`teamix-evo-design-rules`](../teamix-evo-design-rules/SKILL.md) instead — or run both in tandem.
+If the task is purely about _visual design_ of a screen (layout / colors / spacing), use [`teamix-evo-design`](../teamix-evo-design/SKILL.md) instead — or run both in tandem.
 
 ## What this skill does
 
@@ -67,20 +67,20 @@ Before AI writes or commits code, it performs an **8-step gated flow**. Steps 1-
 
 ## Files in this skill
 
-| File | Purpose |
-| --- | --- |
-| [`reuse-first.md`](reuse-first.md) | Decision flow for reusing existing components / utilities before writing new ones |
-| [`file-structure.md`](file-structure.md) | Top-level `src/` folder layout、ownership、import boundaries、naming、global-state tier (useState → Context → store) |
-| [`api-layering.md`](api-layering.md) | Where API code lives (`src/services/`)、how data flows from service → hook → component |
-| [`forms-and-validation.md`](forms-and-validation.md) | `react-hook-form` + `zod` patterns、schema location、submit/error wiring |
-| [`error-and-loading.md`](error-and-loading.md) | Global / page ErrorBoundary、react-query three-state、Suspense、toast、reportError |
-| [`routing-and-codesplit.md`](routing-and-codesplit.md) | `React.lazy` per page、guards、404/403/500 fallback、search-params state、Suspense placement |
-| [`testing.md`](testing.md) | `vitest` + RTL + msw、co-located tests、what is mandatory vs recommended |
-| [`checklist.md`](checklist.md) | Multi-section self-review before declaring done |
+| File                                                   | Purpose                                                                                                              |
+| ------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------- |
+| [`reuse-first.md`](reuse-first.md)                     | Decision flow for reusing existing components / utilities before writing new ones                                    |
+| [`file-structure.md`](file-structure.md)               | Top-level `src/` folder layout、ownership、import boundaries、naming、global-state tier (useState → Context → store) |
+| [`api-layering.md`](api-layering.md)                   | Where API code lives (`src/services/`)、how data flows from service → hook → component                               |
+| [`forms-and-validation.md`](forms-and-validation.md)   | `react-hook-form` + `zod` patterns、schema location、submit/error wiring                                             |
+| [`error-and-loading.md`](error-and-loading.md)         | Global / page ErrorBoundary、react-query three-state、Suspense、toast、reportError                                   |
+| [`routing-and-codesplit.md`](routing-and-codesplit.md) | `React.lazy` per page、guards、404/403/500 fallback、search-params state、Suspense placement                         |
+| [`testing.md`](testing.md)                             | `vitest` + RTL + msw、co-located tests、what is mandatory vs recommended                                             |
+| [`checklist.md`](checklist.md)                         | Multi-section self-review before declaring done                                                                      |
 
 ## Relationship to other skills
 
-- [`teamix-evo-design-rules`](../teamix-evo-design-rules/SKILL.md) — visual / interaction rules for screen generation. Run **alongside** this skill when the task includes UI; this skill never overrides design-rules on visual concerns.
+- [`teamix-evo-design-opentrek`](../teamix-evo-design-opentrek/SKILL.md) — visual / interaction rules for screen generation. Run **alongside** this skill when the task includes UI; this skill never overrides design on visual concerns.
 - [`teamix-evo-manage`](../teamix-evo-manage/SKILL.md) — lifecycle (`init` / `update` / `uninstall` / `skills add`). Out of scope here.
 
 ## Why these conventions

package/{skills/teamix-evo-coding-conventions → src/teamix-evo-code-opentrek}/checklist.md

@@ -124,7 +124,7 @@
 
 (若改动包含 UI)
 
-- [ ] 视觉部分按 [`teamix-evo-design-rules`](../teamix-evo-design-rules/SKILL.md) 自检过 token / 间距 / 圆角 / 动效
+- [ ] 视觉部分按 [`teamix-evo-design-opentrek`](../teamix-evo-design-opentrek/SKILL.md) 自检过 token / 间距 / 圆角 / 动效
 - [ ] 没有硬编码颜色 / 间距 / 字号(交给 ui 包 + design token)
 
 ---
@@ -159,7 +159,7 @@
 - 数据层: ✅ services/order.ts 纯函数;✅ hooks/useOrderList.ts 包 react-query;✅ 组件未 fetch
 - 目录: ✅ 页面在 pages/orders/;✅ 跨页面组件在 components/
 - 命名: ✅ kebab 目录 / Pascal 组件 / camel hook
-- 边界: ✅ 全部走 @/*;✅ 无反向依赖
+- 边界: ✅ 全部走 @/\*;✅ 无反向依赖
 - 类型: ✅ types/order.ts 集中声明
 - 表单(若涉及): ✅ useForm + zodResolver;✅ schema 在 services/order.schema.ts
 - 错误/加载(若涉及): ✅ 三态全处理;✅ ErrorBoundary 已在 App 根;✅ mutation toast

package/{skills/teamix-evo-coding-conventions → src/teamix-evo-code-opentrek}/reuse-first.md

@@ -13,8 +13,8 @@
 │   ├── 是 → 走 §1（查 @teamix-evo/ui 注册表）
 │   └── 否 → 跳 Step 2
 │
-├── Step 2: 这是业务组件 / 页面模板吗?
-│   ├── 是 → 走 §2（查 @teamix-evo/biz-ui 与 @teamix-evo/templates）
+├── Step 2: 这是业务组件 / 页面骨架吗?
+│   ├── 是 → 走 §2（查 @teamix-evo/biz-ui；页面骨架走 design skill 的 patterns/）
 │   └── 否 → 跳 Step 3
 │
 ├── Step 3: 这是工具函数 / Hook 吗?
@@ -39,12 +39,12 @@
 
 ### 命中后的处理
 
-| 情况 | 处理 |
-| --- | --- |
-| 注册表里有,本项目已装 | 直接 `import` 复用,**不要复制源码** |
-| 注册表里有,本项目未装 | 提示用户跑 `teamix-evo ui add <id>`,装机后再用 |
+| 情况                            | 处理                                           |
+| ------------------------------- | ---------------------------------------------- |
+| 注册表里有,本项目已装           | 直接 `import` 复用,**不要复制源码**            |
+| 注册表里有,本项目未装           | 提示用户跑 `teamix-evo ui add <id>`,装机后再用 |
 | 注册表里有近义但 props 不完全够 | **优先组合**(包一层 wrapper),不要 fork ui 源码 |
-| 注册表里完全没有 | 进 §4 |
+| 注册表里完全没有                | 进 §4                                          |
 
 ### 反模式(禁止)
 
@@ -54,20 +54,28 @@
 
 ---
 
-## §2 · 业务组件 / 页面模板:查 `biz-ui` 与 `templates`
+## §2 · 业务组件:查 `biz-ui`(页面骨架走 design skill 的 patterns/)
 
-| 包 | 用途 | 查询入口 |
-| --- | --- | --- |
+| 包                   | 用途                                   | 查询入口                                               |
+| -------------------- | -------------------------------------- | ------------------------------------------------------ |
 | `@teamix-evo/biz-ui` | 业务化的复合组件(变体感知 + slot 边界) | 本项目 `node_modules/@teamix-evo/biz-ui/manifest.json` |
-| `@teamix-evo/templates` | 页面模板(slot-based) | 同上 |
+
+### 页面骨架来源(列表 / 详情 / 表单 / 仪表盘)
+
+> ⚠️ **AI 默认不调用 `@teamix-evo/templates` 包**(见 [ADR 0031](../../../docs/adr/0031-skill-templates-decoupling.md))。页面骨架按下列优先级生成:
+
+1. **首选** —— 读 `teamix-evo-design-opentrek` skill 的 [`patterns/{list|detail|form|dashboard}-page.md`](../teamix-evo-design-opentrek/patterns/),按 Zone Map 与决策树用 ui 原子件 + biz-ui 业务件**直接拼装**到 `src/pages/<id>/`
+2. **patterns/ 未覆盖时** —— 按业界流行的中后台页面架构(antd Pro / shadcn Examples 等)与用户描述自由实现,**不要回退到 templates 包**
+3. **`@teamix-evo/templates` 包与 CLI 命令仍保留**,但仅在用户**显式**要求(如"用 templates 包的 frozen 骨架")时才走 `teamix-evo templates add`
 
 ### 决策表
 
-| 场景 | 选择 |
-| --- | --- |
-| 列表页 / 详情页 / 表单页骨架 | 优先 `templates` |
-| "带筛选的用户表格"、"带审批流的卡片" | 优先 `biz-ui` |
-| 一次性的、强领域绑定的组合 | 写在 `src/components/<domain>/` 里,**不要污染 biz-ui** |
+| 场景                                  | 选择                                                      |
+| ------------------------------------- | --------------------------------------------------------- |
+| 列表页 / 详情页 / 表单页 / 仪表盘骨架 | 读 design skill `patterns/*.md` → ui + biz-ui 拼装        |
+| "带筛选的用户表格"、"带审批流的卡片"  | 优先 `biz-ui`                                             |
+| 一次性的、强领域绑定的组合            | 写在 `src/components/<domain>/` 里,**不要污染 biz-ui**    |
+| patterns/ 未覆盖的特殊页面            | 按业界流行架构 + 用户描述自由实现,**不调用 templates 包** |
 
 ---
 
@@ -102,7 +110,7 @@
 1. **命名要能让下次复用查得到** —— 起 `OrderStatusBadge` 而不是 `MyBadge`;`useOrderList` 而不是 `useList`。
 2. **抽象层级别低于一次性页面** —— 跨页面会用的才放 `src/components/`,只在一个页面用的写在 `src/pages/<id>/_components/`。
 3. **暴露面尽量窄** —— 默认只 `export` 这次需要的 API,别一次性 `export *`。
-4. **写完登记** —— 在 PR 描述里明确"新增 `<path>`,因为 ui / biz-ui / templates / 本项目均未提供 X 能力"。
+4. **写完登记** —— 在 PR 描述里明确"新增 `<path>`,因为 ui / biz-ui / patterns / 本项目均未提供 X 能力"(注:不再以 `templates` 包作为兜底依据,见 [ADR 0031](../../../docs/adr/0031-skill-templates-decoupling.md))。
 
 ---
 

package/src/teamix-evo-code-uni-manager/SKILL.md

@@ -0,0 +1,95 @@
+---
+name: teamix-evo-code-uni-manager
+description: |
+  Enforce teamix-evo coding conventions in uni-manager (hybrid-cloud / multi-tenant console) consumer apps — reuse-first against `@teamix-evo/ui` registry + `biz-ui/uni-manager` (um-topbar / CloudBadge), API code under `src/services/` with tenant / region context propagation, `src/` layering and import boundaries.
+  TRIGGER when: user asks to "新增 / 重构 / 写一个" 组件 / 页面 / 接口 / 钩子 / 工具 / hook in a hybrid-cloud / 专有云 / 多租户 / 多区域 console; phrases like "create a CRUD page"、"add an API call"、"extract a hook"、"refactor this fetch"、"调一下接口"、"加个组件"、"加个按钮"; file write under `src/pages/**`、`src/components/**`、`src/services/**`、`src/hooks/**`; AI is about to write any new `.tsx` / `.ts` file in a teamix-evo-installed uni-manager-variant project.
+  SKIP: pure visual / layout design questions about an already-existing screen with no code change (defer to teamix-evo-design-uni-manager); teamix-evo lifecycle (init / update / uninstall) — those go to teamix-evo-manage; changes only to design tokens / styles / theme — those go to ESLint and `tokens.overrides.css`.
+  Coordinates with: teamix-evo-design-uni-manager (run alongside when the change also creates a UI screen — design handles the visual side, this skill handles file placement and reuse).
+---
+
+# teamix-evo-code-uni-manager
+
+This skill bundles the **AI-readable engineering conventions** for **uni-manager-variant** consumer business apps — products that target hybrid-cloud / 专有云 / 多租户 / 多区域 management consoles. It complements [`teamix-evo-design-uni-manager`](../teamix-evo-design-uni-manager/SKILL.md) — design tells AI _what a screen should look like_; this skill tells AI _where the code should live, what to reuse before writing new code, and how to thread tenant / region / cloud-provider context through the layers_.
+
+<!-- teamix-evo:managed:start id="core" -->
+
+## When to use
+
+Activate this skill whenever AI is about to **write or refactor code** inside a uni-manager-variant consumer app. Common signals:
+
+- "新增一个 xxx 页面 / 列表页 / 详情页（控制台 / 工作台 / 多云资源）"
+- "加一个 xxx 接口 / 调用 xxx API（多租户 / 跨云 / 跨账号）"
+- "写一个 xxx 组件"
+- "把这段重构一下"
+- "create a CRUD page for 多云实例"
+- "add an API call to list instances across regions"
+- Any time AI is about to create a new file under `src/pages/`、`src/components/`、`src/services/`、`src/hooks/` in a hybrid-cloud console
+
+If the task is purely about _visual design_ of a screen, use [`teamix-evo-design-uni-manager`](../teamix-evo-design-uni-manager/SKILL.md) instead — or run both in tandem.
+
+## What this skill does
+
+Before AI writes or commits code, it performs an **8-step gated flow**. Steps 1-4 are baseline (always run); steps 5-7 are topic gates (run when the task touches that topic); step 8 is the final self-review.
+
+1. **Reuse-first check** — read [`reuse-first.md`](reuse-first.md). Before creating any new component, query the `@teamix-evo/ui` registry (via MCP `list_components` / `find_components`), the **biz-ui/uni-manager** layer (um-topbar / CloudBadge / ContextSwitcher placeholders), and grep the local project. Only write new code when no reuse path exists. **组件兜底铁律**：找不到时优先 ui 原子件组合，**禁止**自撸基础件。
+2. **Layering check** — read [`api-layering.md`](api-layering.md). Any code that talks to a backend goes under `src/services/<domain>.ts`; multi-tenant / multi-region / multi-cloud context (tenantId / regionId / cloudProvider) is **propagated through `lib/http.ts` interceptors**, not as ad-hoc params per call. Components never call `fetch` / `axios` directly. Data hooks live in `src/hooks/` and consume services.
+3. **Directory check** — read [`file-structure.md`](file-structure.md). Place the new file under the right top-level folder; uni-manager-specific shells (TenantContext / RegionContext / CloudBadge) have conventional locations.
+4. **Forms gate** — if the task involves a form, read [`forms-and-validation.md`](forms-and-validation.md). `react-hook-form` + `zod`; schema lives at `src/services/<domain>.schema.ts`. Dangerous operations (delete / release / destroy) **must** route through `useDangerConfirm` (input resource name).
+5. **Error/loading gate** — if the task adds a page or data hook, read [`error-and-loading.md`](error-and-loading.md). Ensure global ErrorBoundary, page-level fallback, and three-state handling (`isPending` / `isError` / data) are in place; mutations report success/error via `toast`. Cross-cloud resource-not-found has a dedicated fallback.
+6. **Routing gate** — if the task adds a route or page-entry, read [`routing-and-codesplit.md`](routing-and-codesplit.md). Pages use `React.lazy`; auth/role guards live in `src/routes/guards.tsx`; **list-page filters MUST sync `tenantId` / `regionId` / `cloudProvider` into URL search params**; um-topbar context switch rewrites the current URL.
+7. **Testing gate** — read [`testing.md`](testing.md). Pure functions and zod schemas are **mandatory** to test; tenant-context-aware http handlers must be covered by msw.
+8. **Self-review** — run [`checklist.md`](checklist.md). Every item must pass before declaring the change done.
+
+## Inputs the user provides
+
+- Intent: "add a page", "add a service call", "refactor X", "extract a hook", etc.
+- Optional: domain entity (`instance`、`database`、`tenant`、`workorder`、`audit-log`)
+- Optional: existing file the change should land near
+- Optional: cloud-provider scope（only-aliyun / multi-cloud / private-only）
+
+## Outputs
+
+- Code placed under the conventional path
+- Reuse decisions explicitly logged ("reused `Button` from `@teamix-evo/ui`" / "reused `um-topbar` from `biz-ui/uni-manager`" / "no match found, wrote a new `OrderCard`")
+- Tenant / region / cloud context propagation logged
+- Pass / fail status against [`checklist.md`](checklist.md)
+
+## How to invoke (typical flow)
+
+1. Parse user intent → identify which artifact is being created (page / component / service / hook / util / form / route)
+2. Read [`reuse-first.md`](reuse-first.md) and run the reuse query (MCP first, then biz-ui/uni-manager, then local grep)
+3. Read [`file-structure.md`](file-structure.md) to pick the destination directory
+4. If the change touches network / backend, read [`api-layering.md`](api-layering.md) — confirm tenant / region / cloud headers are injected via interceptor
+5. If the change involves a form, read [`forms-and-validation.md`](forms-and-validation.md) — for dangerous operations, plug `useDangerConfirm`
+6. If the change adds a page / data hook, read [`error-and-loading.md`](error-and-loading.md) for fallback / Skeleton / toast wiring
+7. If the change adds a route or page entry, read [`routing-and-codesplit.md`](routing-and-codesplit.md) — confirm tenant / region URL sync
+8. Decide test coverage per [`testing.md`](testing.md); write `*.test.ts(x)` next to source
+9. Write the code; cite each reuse / new-write decision in the response
+10. Run through [`checklist.md`](checklist.md); list pass / fail explicitly
+
+## Files in this skill
+
+| File                                                   | Purpose                                                                                              |
+| ------------------------------------------------------ | ---------------------------------------------------------------------------------------------------- |
+| [`reuse-first.md`](reuse-first.md)                     | 复用决策流（ui 原子件 + biz-ui/uni-manager + 本项目）；组件兜底铁律                                  |
+| [`file-structure.md`](file-structure.md)               | 顶层 `src/` 目录骨架、归属、import 边界、命名、全局态分级（含 TenantContext / RegionContext）        |
+| [`api-layering.md`](api-layering.md)                   | API 三层结构 + 多租户 / 多区域 / 跨云上下文注入                                                      |
+| [`forms-and-validation.md`](forms-and-validation.md)   | `react-hook-form` + `zod`；危险操作走 `useDangerConfirm`（输入资源名称确认）                         |
+| [`error-and-loading.md`](error-and-loading.md)         | 全局 / 页面 ErrorBoundary、三态、Suspense、toast、跨云资源专属 fallback                              |
+| [`routing-and-codesplit.md`](routing-and-codesplit.md) | `React.lazy`、guards、404/403/500、tenant/region/cloud 进 URL search params、um-topbar 切换 URL 改写 |
+| [`testing.md`](testing.md)                             | `vitest` + RTL + msw、就近 test、tenant-context handler 覆盖                                         |
+| [`checklist.md`](checklist.md)                         | 多段自检，含 uni-manager 红线（自建 topbar / 不带租户上下文 / 危险操作未输入名称）                   |
+
+## Relationship to other skills
+
+- [`teamix-evo-design-uni-manager`](../teamix-evo-design-uni-manager/SKILL.md) — visual / interaction rules for uni-manager screen generation. Run **alongside** this skill when the task includes UI; this skill never overrides design on visual concerns.
+- [`teamix-evo-code-opentrek`](../teamix-evo-code-opentrek/SKILL.md) — sister code skill for OpenTrek variant. The two skills share 80% of conventions (file structure / layering / forms / testing); uni-manager-specific deltas are in this skill's SKILL/reuse-first/api-layering/routing/checklist.
+- [`teamix-evo-manage`](../teamix-evo-manage/SKILL.md) — lifecycle (`init` / `update` / `uninstall` / `skills add`). Out of scope here.
+
+## Why these conventions（uni-manager 视角）
+
+- **Single source for UI** — `@teamix-evo/ui` 89 原子件 + `biz-ui/uni-manager`（当前 1 实物 um-topbar，其余如 CloudBadge / ContextSwitcher 是概念占位）。Re-implementing 顶部 topbar / 基础件会破坏一致性三件套（UM1/UM2/UM3）。
+- **Stable seams for change** — tenant / region / cloud 上下文集中在 `lib/http.ts` interceptor 与 `contexts/TenantContext.tsx`，新增云厂商或区域不需要改 89 处 service 调用。
+- **Predictable file location** — 所有 uni-manager 项目目录形状一致；新接手的人 5 分钟内能找到「租户切换在哪管」「跨云列表怎么写」「危险操作怎么二次确认」。
+
+<!-- teamix-evo:managed:end -->