@teamix-evo/skills 0.12.1 → 0.13.0

package/src/teamix-evo-code-opentrek/file-structure.md

@@ -10,13 +10,13 @@
 
 ```
 src/
+├── features/         # 业务领域(每个子目录聚合 api/hooks/types/mocks/schema)
 ├── pages/            # 路由页面(每个目录对应一条路由)
 ├── components/       # 跨页面复用的业务组件
-├── services/         # 后端通信(纯函数,见 api-layering.md)
-├── hooks/            # 自定义 Hook(包含数据 hook、UI hook)
+├── hooks/            # 跨领域共享的通用 Hook(极少数,如 useDebounce)
 ├── contexts/         # React Context(跨子树共享、低频更新的全局态)
 ├── stores/           # 高频全局态(zustand / jotai / redux,首次需要时引入,只用一种)
-├── types/            # Domain / API 类型声明(.ts 仅类型,无运行时)
+├── types/            # 跨领域通用类型(ApiResponse<T>、Pagination<T>)
 ├── utils/            # 纯函数工具(无 React、无副作用)
 ├── lib/              # 三方 SDK 包装、http 实例、环境配置、monitor
 ├── routes/           # 路由配置 + 守卫(若用 react-router 集中式声明)
@@ -29,7 +29,7 @@ src/
 └── App.tsx           # 根组件
 ```
 
-> 没列出的目录按需补,但**不要**新增同义层(如同时有 `utils/` 和 `helpers/`、`api/` 和 `services/`、`views/` 和 `pages/`)。`*.test.ts(x)` 文件**就近**放在被测文件同目录,**不要**集中堆到顶层 `tests/`(见 [`testing.md`](testing.md))。
+> 没列出的目录按需补,但**不要**新增同义层(如同时有 `utils/` 和 `helpers/`、`services/` 和 `features/`、`views/` 和 `pages/`)。`*.test.ts(x)` 文件**就近**放在被测文件同目录,**不要**集中堆到顶层 `tests/`(见 [`testing.md`](testing.md))。
 
 ---
 
@@ -56,7 +56,7 @@ src/pages/
 
 - 页面组件**默认 default export**,与文件名一致
 - `_components/` `_hooks/` 用下划线前缀标记**私有**,**禁止跨页面 import**
-- 跨页面用得到的组件/hook → 升到 `src/components/` `src/hooks/`
+- 跨页面用得到的组件 → 升到 `src/components/`；领域 hook → 放 `src/features/<domain>/hooks.ts`
 
 ### `src/components/`
 
@@ -78,27 +78,46 @@ src/components/
 - **不要**重复 `@teamix-evo/ui` 已经提供的能力(见 [reuse-first.md](reuse-first.md))
 - **不要**写"小工具组件"如 `Wrapper`、`Container` —— 用 div + tailwind 即可
 
-### `src/services/`
+### `src/features/`
 
-**职责**:后端通信纯函数。详见 [`api-layering.md`](api-layering.md)。
+**职责**:业务领域代码。每个子目录聚合一个领域的全部代码。详见 [`api-layering.md`](api-layering.md)。
+
+```
+src/features/
+├── order/
+│   ├── api.ts          # 请求纯函数(listOrders, createOrder, ...)
+│   ├── hooks.ts        # react-query 封装(useOrderList, useCreateOrder, ...)
+│   ├── types.ts        # 领域类型(Order, OrderStatus, ...)
+│   ├── mocks.ts        # 本地 mock 数据(开发阶段)
+│   └── schema.ts       # zod schema(CreateOrderInputSchema, ...)
+├── user/
+│   └── ...
+└── tenant/
+    └── ...
+```
+
+约束:
+
+- 一个领域 = 一个子目录,**不按技术类型拆**
+- api.ts 是纯函数层,**不依赖 React**
+- hooks.ts 调同目录 api.ts,**禁止**直接 fetch
+- types.ts 仅类型,无运行时代码
+- 同领域内用相对路径 `./types`、`./api`
 
 ### `src/hooks/`
 
-**职责**:跨页面复用的自定义 Hook。
+**职责**:跨领域共享的通用 Hook（极少数）。
 
 ```
 src/hooks/
-├── useOrderList.ts          # 数据 hook(包 react-query)
-├── useCreateOrder.ts
-├── useDebounce.ts           # UI hook
+├── useDebounce.ts           # 通用 UI hook
 └── useMediaQuery.ts
 ```
 
 约束:
 
-- 命名必须 `use` 开头
-- 单 hook = 单文件
-- 数据 hook 调 `src/services/`,**禁止**直接 fetch
+- 领域数据 hook **不放这里**,放 `src/features/<domain>/hooks.ts`
+- 只放与业务领域无关的通用 hook
 
 ### 全局态选型决策
 
@@ -133,13 +152,13 @@ Context 文件位置:
 
 ### `src/types/`
 
-**职责**:类型声明。
+**职责**:跨领域通用类型声明。
 
 约束:
 
 - 只放 `.ts` 类型文件,**不导出运行时代码**
-- 按 domain 拆:`order.ts`、`user.ts`
-- 通用类型放 `api.ts`、`common.ts`
+- Domain 类型放 `src/features/<domain>/types.ts`,**不放这里**
+- 仅放跨领域通用类型:`api.ts`（ApiResponse<T>、Pagination<T>）、`common.ts`
 
 ### `src/utils/`
 
@@ -147,7 +166,7 @@ Context 文件位置:
 
 约束:
 
-- **不依赖 React**(用了 React 应该是 hook,放 `src/hooks/`)
+- **不依赖 React**(用了 React 应该是 hook,放 `src/features/<domain>/hooks.ts` 或 `src/hooks/`)
 - **不依赖 DOM**(用了 DOM 应该是 lib 层包装)
 - **不发请求**(发请求是 service)
 - 一个文件一个主题:`format.ts`、`validate.ts`、`array.ts`
@@ -205,7 +224,7 @@ src/routes/
 ```ts
 // ✅
 import { Button } from '@teamix-evo/ui';
-import { listOrders } from '@/services/order';
+import { listOrders } from '@/features/order/api';
 import { OrderStatusBadge } from '@/components/OrderStatusBadge';
 
 // ❌
@@ -217,21 +236,21 @@ import { listOrders } from '../../../services/order';
 ## Import 边界(单向依赖)
 
 ```
-pages   ──▶ components, hooks, services, types, utils, lib, stores
-components ──▶ hooks, services, types, utils, lib (NOT pages)
-hooks   ──▶ services, types, utils, lib, stores (NOT components, NOT pages)
-services ──▶ types, lib (NOT hooks, NOT components, NOT pages)
-stores  ──▶ types, utils, lib (NOT services, NOT hooks)
-types   ──▶ (no runtime imports)
-utils   ──▶ types only
-lib     ──▶ types only
+pages      ──▶ components, features, hooks, types, utils, lib, stores
+components ──▶ features, hooks, types, utils, lib (NOT pages)
+features/* ──▶ lib, types (内部 api→types, hooks→api+types; NOT components, NOT pages)
+hooks      ──▶ types, utils, lib (NOT features, NOT components, NOT pages)
+stores     ──▶ types, utils, lib (NOT features, NOT hooks)
+types      ──▶ (no runtime imports)
+utils      ──▶ types only
+lib        ──▶ types only
 ```
 
 要点:
 
-- **services 不依赖 React** —— 它是纯函数层
+- **features/*/api.ts 不依赖 React** —— 它是纯函数层
 - **types / utils / lib 是叶子层** —— 不依赖业务层,谁都能引
-- **反向依赖直接否决**(component 不能 import page,service 不能 import hook)
+- **反向依赖直接否决**(component 不能 import page,api 不能 import hook)
 
 ---
 
@@ -240,10 +259,10 @@ lib     ──▶ types only
 | 反模式                                            | 为什么禁                         | 应该怎么做                                                                                   |
 | ------------------------------------------------- | -------------------------------- | -------------------------------------------------------------------------------------------- |
 | `src/views/`、`src/screens/` 与 `src/pages/` 并存 | 同义层,认知爆炸                  | 二选一,统一叫 `pages/`                                                                       |
-| `src/api/` 与 `src/services/` 并存                | 同义层                           | 统一叫 `services/`                                                                           |
+| `src/services/` 与 `src/features/` 并存            | 同义层                           | 统一用 `features/`                                                                           |
 | `src/utils/` 与 `src/helpers/` 并存               | 同义层                           | 统一叫 `utils/`                                                                              |
 | 在 `src/components/` 里写 page-only 组件          | 抽象层级别错位                   | 放 `src/pages/<id>/_components/`                                                             |
-| 在 `src/utils/` 里写 React Hook                   | 边界错位                         | 放 `src/hooks/`                                                                              |
+| 在 `src/utils/` 里写 React Hook                   | 边界错位                         | 领域 hook → `features/<domain>/hooks.ts`；通用 hook → `src/hooks/`                           |
 | 一个文件 export 5 个不相关的工具                  | 命名失焦                         | 拆成多文件,一个主题一个文件                                                                  |
 | `index.ts` 大量 `export *` 当 barrel              | 影响 tree-shaking、循环依赖      | 显式 named export 需要的几个                                                                 |
 | 为消除一处 props drilling 直接引 zustand          | 升级过度,徒增心智                | 用 React `Context`                                                                           |
@@ -264,15 +283,15 @@ lib     ──▶ types only
 | 新增订单列表页                            | `src/pages/orders/index.tsx`                                                                  |
 | 新增订单状态徽章(跨页面用)                | `src/components/OrderStatusBadge.tsx`                                                         |
 | 新增订单状态徽章(只在订单页用)            | `src/pages/orders/_components/OrderStatusBadge.tsx`                                           |
-| 新增"取消订单"接口调用                    | `src/services/order.ts` 加 `cancelOrder`                                                      |
-| 新增"取消订单"的 mutation hook            | `src/hooks/useCancelOrder.ts`                                                                 |
+| 新增"取消订单"接口调用                    | `src/features/order/api.ts` 加 `cancelOrder`                                                  |
+| 新增"取消订单"的 mutation hook            | `src/features/order/hooks.ts` 加 `useCancelOrder`                                             |
 | 新增日期格式化函数                        | `src/utils/format.ts`(先 grep 是否已存在)                                                     |
 | 新增鉴权拦截器                            | `src/lib/http.ts` 加 interceptor                                                              |
-| 新增订单 domain 类型                      | `src/types/order.ts`                                                                          |
+| 新增订单 domain 类型                      | `src/features/order/types.ts`                                                                 |
 | 跨少量组件分享当前用户 / 主题             | `src/contexts/UserContext.tsx`(用 React Context)                                              |
 | 跨域高频全局态(首次需要)                  | `src/stores/useXxxStore.ts`(按需引 zustand,固定后只用一种)                                    |
-| 列表 / 详情等服务端数据                   | `src/hooks/useXxx.ts` 包 `react-query`,**不进** store / Context                               |
-| 新增"下单表单"(react-hook-form + zod)     | `src/pages/orders/new/_components/CreateOrderForm.tsx` + `src/services/order.schema.ts`       |
+| 列表 / 详情等服务端数据                   | `src/features/<domain>/hooks.ts` 包 `react-query`,**不进** store / Context                    |
+| 新增"下单表单"(react-hook-form + zod)     | `src/pages/orders/new/_components/CreateOrderForm.tsx` + `src/features/order/schema.ts`       |
 | 跨页面复用表单(地址 / 客户搜索)           | `src/components/forms/<Name>Form.tsx` + 对应 schema                                           |
 | 新增路由 / 页面入口                       | `src/routes/index.tsx` 注册 + `src/pages/<id>/index.tsx`(default export,被 `React.lazy` 引入) |
 | 新增鉴权 / 角色守卫                       | `src/routes/guards.tsx`                                                                       |

package/src/teamix-evo-code-opentrek/forms-and-validation.md

@@ -22,22 +22,24 @@
 ## Schema 落点
 
 ```
-src/services/
-├── order.ts                # 请求函数:listOrders、createOrder
-└── order.schema.ts         # zod schema:CreateOrderInput、UpdateOrderInput
+src/features/order/
+├── api.ts              # 请求函数:listOrders、createOrder
+├── schema.ts           # zod schema:CreateOrderInput、UpdateOrderInput
+├── hooks.ts            # react-query 封装
+└── types.ts            # 领域类型
 ```
 
 约定:
 
-- **每个 domain 一个 `<domain>.schema.ts`**,与 service 同目录
+- **每个 domain 一个 `schema.ts`**,与 api / hooks / types 同目录
 - 从 schema 派生类型:`export type CreateOrderInput = z.infer<typeof CreateOrderInputSchema>`
-- service 的入参 / 返回类型**优先用** schema 推导,而不是手写 interface
+- api 的入参 / 返回类型**优先用** schema 推导,而不是手写 interface
 - **不要**把 schema 写在页面 / 组件文件里 —— schema 是 domain 资产,跨页面复用
 
 ### 示例
 
 ```ts
-// src/services/order.schema.ts
+// src/features/order/schema.ts
 import { z } from 'zod';
 
 export const CreateOrderInputSchema = z.object({
@@ -57,13 +59,12 @@ export type CreateOrderInput = z.infer<typeof CreateOrderInputSchema>;
 ```
 
 ```ts
-// src/services/order.ts
+// src/features/order/api.ts
 import { http } from '@/lib/http';
-import type { CreateOrderInput } from './order.schema';
-import type { Order } from '@/types/order';
+import type { CreateOrderInput } from './schema';
+import type { Order } from './types';
 
 export async function createOrder(input: CreateOrderInput): Promise<Order> {
-  // 服务端层也可在这里再 parse 一次防御
   const { data } = await http.post('/api/orders', input);
   return data;
 }
@@ -100,11 +101,11 @@ src/components/forms/
 // src/pages/orders/new/_components/CreateOrderForm.tsx
 import { useForm } from 'react-hook-form';
 import { zodResolver } from '@hookform/resolvers/zod';
-import { useCreateOrder } from '@/hooks/useCreateOrder';
+import { useCreateOrder } from '@/features/order/hooks';
 import {
   CreateOrderInputSchema,
   type CreateOrderInput,
-} from '@/services/order.schema';
+} from '@/features/order/schema';
 import { Button, Input, Form, FormField, FormItem } from '@/components/ui';
 
 export function CreateOrderForm() {
@@ -155,7 +156,7 @@ export function CreateOrderForm() {
 - ❌ 在 `onChange` 里手写 `if (value.length > 20) setError(...)`
 - ❌ 校验报错信息硬编码在组件里("请输入正确的手机号") —— 写在 schema 里,UI 只读
 - ❌ 表单状态用 `useState`,然后再加 `useEffect` 同步校验 —— 直接用 `useForm`
-- ❌ schema 在组件文件里就地定义 —— 抽到 `<domain>.schema.ts`
+- ❌ schema 在组件文件里就地定义 —— 抽到 `features/<domain>/schema.ts`
 - ❌ 提交逻辑写在 `<form onSubmit>` 里直接 fetch —— 走 mutation hook
 
 ---
@@ -215,8 +216,8 @@ pnpm add react-hook-form zod @hookform/resolvers
 ```
 ## 表单改动
 
-- src/services/order.schema.ts: 新增 CreateOrderInputSchema(zod)、派生类型
-- src/services/order.ts: createOrder 入参用派生类型
+- src/features/order/schema.ts: 新增 CreateOrderInputSchema(zod)、派生类型
+- src/features/order/api.ts: createOrder 入参用派生类型
 - src/pages/orders/new/_components/CreateOrderForm.tsx: useForm + zodResolver
-- src/hooks/useCreateOrder.ts: useMutation 包 createOrder,onError 区分字段级 / 通用
+- src/features/order/hooks.ts: useCreateOrder — useMutation 包 createOrder,onError 区分字段级 / 通用
 ```

package/src/teamix-evo-code-opentrek/reuse-first.md

@@ -34,8 +34,8 @@
 
 ### 查询顺序(从快到慢)
 
-1. **MCP `list_components`** —— 一次列全部,扫描是否有同名 / 近义。
-2. **MCP `find_components` query=<关键词>** —— 子串匹配 id / name / description。
+1. **读 `.teamix-evo/meta/ui/manifest.json`** —— 一次列全部,扫描是否有同名 / 近义。
+2. **`grep <关键词> .teamix-evo/meta/ui/manifest.json`** —— 子串匹配 id / name / description;需要详细 Props/示例时读 `.teamix-evo/meta/ui/<id>.md`。
 3. **本项目 grep** —— `grep -r "from '@/components/ui'" src/` 看哪些已经装机。
 4. **本项目 `.teamix-evo/ui/manifest.lock.json`** —— 已装机的 ui entry 清单。
 
@@ -64,11 +64,8 @@
 
 ### 页面骨架来源(列表 / 详情 / 表单 / 仪表盘)
 
-> ⚠️ **AI 默认不调用 `@teamix-evo/templates` 包**（见 ADR 0031 skill-templates-decoupling）。页面骨架按下列优先级生成：
-
 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`
+2. **patterns/ 未覆盖时** —— 按业界流行的中后台页面架构(antd Pro / shadcn Examples 等)与用户描述自由实现
 
 ### 决策表
 
@@ -77,7 +74,7 @@
 | 列表页 / 详情页 / 表单页 / 仪表盘骨架 | 读 design skill `patterns/*.md` → ui + biz-ui 拼装        |
 | "带筛选的用户表格"、"带审批流的卡片"  | 优先 `biz-ui`                                             |
 | 一次性的、强领域绑定的组合            | 写在 `src/components/<domain>/` 里,**不要污染 biz-ui**    |
-| patterns/ 未覆盖的特殊页面            | 按业界流行架构 + 用户描述自由实现,**不调用 templates 包** |
+| patterns/ 未覆盖的特殊页面            | 按业界流行架构 + 用户描述自由实现                         |
 
 ---
 
@@ -87,7 +84,7 @@
 
 1. **本项目 grep**:
    ```bash
-   grep -rn "function <近义名>" src/utils/ src/lib/ src/hooks/
+   grep -rn "function <近义名>" src/utils/ src/lib/ src/features/
    ```
 2. **`@teamix-evo/*` 是否提供**(少数情况,如格式化、token 工具)
 3. **依赖里的成熟库** —— 例如:
@@ -112,7 +109,7 @@
 1. **命名要能让下次复用查得到** —— 起 `OrderStatusBadge` 而不是 `MyBadge`;`useOrderList` 而不是 `useList`。
 2. **抽象层级别低于一次性页面** —— 跨页面会用的才放 `src/components/`,只在一个页面用的写在 `src/pages/<id>/_components/`。
 3. **暴露面尽量窄** —— 默认只 `export` 这次需要的 API,别一次性 `export *`。
-4. **写完登记** —— 在 PR 描述里明确“新增 `<path>`，因为 ui / biz-ui / patterns / 本项目均未提供 X 能力”（注：不再以 `templates` 包作为兑底依据，见 ADR 0031 skill-templates-decoupling）。
+4. **写完登记** —— 在 PR 描述里明确”新增 `<path>`，因为 ui / biz-ui / patterns / 本项目均未提供 X 能力”。
 
 ---
 

package/src/teamix-evo-code-opentrek/testing.md

@@ -29,12 +29,12 @@ src/
 ├── utils/
 │   ├── format.ts
 │   └── format.test.ts                    # ← 紧邻
-├── services/
-│   ├── order.ts
-│   └── order.test.ts
-├── hooks/
-│   ├── useOrderList.ts
-│   └── useOrderList.test.ts
+├── features/
+│   └── order/
+│       ├── api.ts
+│       ├── api.test.ts                   # ← 紧邻
+│       ├── hooks.ts
+│       └── hooks.test.tsx
 └── components/
     ├── OrderStatusBadge.tsx
     └── OrderStatusBadge.test.tsx
@@ -61,7 +61,7 @@ src/test/
 
 | 优先级 | 类型                                  | 例子                                | 必测?          |
 | ------ | ------------------------------------- | ----------------------------------- | -------------- |
-| P0     | 纯函数(`src/utils/`、`src/services/`) | `formatMoney`、`isValidOrder`       | ✅ **必测**    |
+| P0     | 纯函数(`src/utils/`、`features/*/api.ts`) | `formatMoney`、`isValidOrder`       | ✅ **必测**    |
 | P0     | zod schema                            | `CreateOrderInputSchema.parse(...)` | ✅ **必测**    |
 | P0     | 关键业务路径(下单 / 支付 / 鉴权)      | E2E-style 组件测                    | ✅ **必测**    |
 | P1     | Hook(数据 hook + 自定义 UI hook)      | `useOrderList`、`useDebounce`       | 推荐           |
@@ -133,9 +133,9 @@ afterAll(() => server.close());
 ```
 
 ```ts
-// src/services/order.test.ts
+// src/features/order/api.test.ts
 import { describe, it, expect } from 'vitest';
-import { listOrders } from './order';
+import { listOrders } from './api';
 
 describe('listOrders', () => {
   it('返回订单列表', async () => {
@@ -149,10 +149,10 @@ describe('listOrders', () => {
 ### Hook
 
 ```tsx
-// src/hooks/useOrderList.test.tsx
+// src/features/order/hooks.test.tsx
 import { renderHook, waitFor } from '@testing-library/react';
 import { QueryClient, QueryClientProvider } from '@tanstack/react-query';
-import { useOrderList } from './useOrderList';
+import { useOrderList } from './hooks';
 
 function wrapper({ children }: { children: React.ReactNode }) {
   const qc = new QueryClient({ defaultOptions: { queries: { retry: false } } });
@@ -247,7 +247,7 @@ renderWithProviders(<OrderListPage />, { route: '/orders?status=pending' });
 | 测 `setState` 是否被调用                 | 测了实现,重构即崩            | 测渲染结果 / 用户行为                           |
 | `getByTestId` 当默认查询                 | data-testid 跟可访问性绑不上 | `getByRole` / `getByLabelText` 优先             |
 | 一个 it 里 expect 10 次无关断言          | 失败定位难                   | 拆多个 it                                       |
-| mock 整个 hook(`vi.mock('@/hooks/...')`) | 失去集成价值                 | msw mock 后端,hook 真跑                         |
+| mock 整个 hook(`vi.mock('@/features/...')`) | 失去集成价值                 | msw mock 后端,hook 真跑                         |
 | 自己 mock fetch / axios                  | 与生产代码路径不一致         | 用 msw                                          |
 | 测试里写 `setTimeout(..., 1000)` 等异步  | 慢且不稳定                   | `await waitFor` / `findBy*`                     |
 | 全局 mock console.error 静默             | 错过真实告警                 | 让测试输出 console.error,但 setup 里 fail on it |
@@ -308,8 +308,8 @@ pnpm exec msw init public/ --save  # 浏览器 worker
 ## 测试覆盖
 
 - 新增 src/utils/calcDiscount.ts → 同目录 calcDiscount.test.ts(5 个 case)
-- 新增 src/services/order.ts:createOrder → order.test.ts(成功 / 422 字段错 / 500)
-- 新增 src/hooks/useCreateOrder.ts → useCreateOrder.test.tsx(success / error)
+- 新增 src/features/order/api.ts:createOrder → api.test.ts(成功 / 422 字段错 / 500)
+- 新增 src/features/order/hooks.ts:useCreateOrder → hooks.test.tsx(success / error)
 - 复用 src/components/OrderStatusBadge.tsx → 已有 test 覆盖,无需补
 - 跳过测: src/pages/orders/new/index.tsx(纯组合,关键逻辑已在 hook / form 层测)
 ```

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

@@ -1,10 +1,10 @@
 ---
 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).
+  Enforce teamix-evo coding conventions in uni-manager apps — reuse-first, tenant/region context propagation, `src/` layering.
+  TRIGGER when: user asks to 新增/重构/写 组件/页面/接口/hook in a 云管/专有云/多租户 console; phrases like "create a CRUD page" / "add an API call" / "调接口"; file write under `src/pages/**`, `src/components/**`, `src/features/**`.
+  SKIP: pure visual/layout design with no code change (→ design-uni-manager); lifecycle commands (→ manage); token/style-only changes (→ ESLint).
+  Coordinates with: teamix-evo-design-uni-manager (design handles visual side, this skill handles file placement and reuse).
 ---
 
 # teamix-evo-code-uni-manager
@@ -23,7 +23,7 @@ Activate this skill whenever AI is about to **write or refactor code** inside a
 - "把这段重构一下"
 - "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
+- Any time AI is about to create a new file under `src/pages/`、`src/components/`、`src/features/` 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.
 
@@ -31,10 +31,10 @@ If the task is purely about _visual design_ of a screen, use [`teamix-evo-design
 
 Before AI writes or commits code, it performs an **8-step gated flow**. Steps 1-4 are baseline (**必须执行，不得跳过**); steps 5-7 are topic gates (run when the task touches that topic); step 8 is the final self-review (**必须执行，不得跳过**).
 
-1. **🚧 Reuse-first check** — **MUST 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** — **MUST 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** — **MUST 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, **MUST 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).
+1. **🚧 Reuse-first check** — **MUST READ** [`reuse-first.md`](reuse-first.md). Before creating any new component, query the `@teamix-evo/ui` registry (via `.teamix-evo/meta/ui/manifest.json` + `<id>.md`), 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** — **MUST READ** [`api-layering.md`](api-layering.md). Any code that talks to a backend goes under `src/features/<domain>/api.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/features/<domain>/hooks.ts` and consume api functions.
+3. **🚧 Directory check** — **MUST READ** [`file-structure.md`](file-structure.md). Place the new file under the right top-level folder (pages / components / features / utils / lib / stores / contexts); uni-manager-specific shells (TenantContext / RegionContext / CloudBadge) have conventional locations.
+4. **🚧 Forms gate** — if the task involves a form, **MUST READ** [`forms-and-validation.md`](forms-and-validation.md). `react-hook-form` + `zod`; schema lives at `src/features/<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, **MUST 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, **MUST 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** — **MUST READ** [`testing.md`](testing.md). Pure functions and zod schemas are **mandatory** to test; tenant-context-aware http handlers must be covered by msw.
@@ -51,17 +51,17 @@ Before AI writes or commits code, it performs an **8-step gated flow**. Steps 1-
 
 ## 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`")
+- Code placed under the conventional path (`src/pages/<id>/`、`src/features/<domain>/api.ts`、…)
+- Reuse decisions explicitly logged ("reused `Button` from `@teamix-evo/ui`" / "reused `um-topbar` from `biz-ui/uni-manager`" / "no match found, wrote a new `InstanceCard` under `src/components/`")
 - 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)
+2. Read [`reuse-first.md`](reuse-first.md) and run the reuse query (读 `.teamix-evo/meta/` 本地文件, 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
+4. If the change touches network / backend, read [`api-layering.md`](api-layering.md) — confirm tenant / region / cloud headers are injected via interceptor; place api in `src/features/<domain>/api.ts`
 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
@@ -75,7 +75,7 @@ Before AI writes or commits code, it performs an **8-step gated flow**. Steps 1-
 | ------------------------------------------------------ | ---------------------------------------------------------------------------------------------------- |
 | [`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 三层结构 + 多租户 / 多区域 / 跨云上下文注入                                                      |
+| [`api-layering.md`](api-layering.md)                   | Feature-based 三层结构（`features/<domain>/`）+ 多租户 / 多区域 / 跨云上下文注入                     |
 | [`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 改写 |
@@ -91,7 +91,7 @@ Before AI writes or commits code, it performs an **8-step gated flow**. Steps 1-
 ## 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 调用。
+- **Stable seams for change** — tenant / region / cloud 上下文集中在 `lib/http.ts` interceptor 与 `contexts/TenantContext.tsx`，新增云厂商或区域不需要改 89 处 api 调用。keeping API calls in `src/features/<domain>/api.ts` means a backend rename only edits one file; keeping components free of fetch logic means they stay easy to test and reuse.
 - **Predictable file location** — 所有 uni-manager 项目目录形状一致；新接手的人 5 分钟内能找到「租户切换在哪管」「跨云列表怎么写」「危险操作怎么二次确认」。
 
 <!-- teamix-evo:managed:end -->