@teamix-evo/skills 0.3.0 → 0.4.0

package/skills/teamix-evo-design-rules-uni-manager/danger-ops.md

@@ -1,87 +0,0 @@
-# 高危操作模式（uni-manager）
-
-> 中性基线 `boundaries.md` 已规定"危险操作必须二次确认"。本文件追加云资源管理领域的高危操作分级与具体 UI 模式。
-
----
-
-## 1. 高危操作分级
-
-| 级别 | 类型示例 | 必备 UI |
-|------|---------|---------|
-| **L1 普通破坏** | 停止实例、解绑 SLB、撤销变更 | AlertDialog 默认 variant + 列出资源 ID |
-| **L2 不可恢复** | 释放实例、删除快照、删除数据库 | AlertDialog `variant="destructive"` + 影响范围列表 + 5+ 关联资源展示 |
-| **L3 跨域影响** | 跨区迁移、流量切换、批量释放 ≥ 10 项 | L2 全部 + **输入资源名校验** + 操作前 dry-run 预演 |
-
----
-
-## 2. AlertDialog 模式
-
-### 标题（陈述句，明确动作 + 资源标识）
-
-- ✅ "永久删除实例 i-abc123"
-- ✅ "将 SLB lb-xyz001 的流量从主可用区切换到备可用区"
-- ❌ "确定要删除吗？"（缺资源标识）
-- ❌ "确认操作"（含糊）
-
-### 正文（必须列出影响）
-
-```
-该操作将：
-- 永久释放实例 i-abc123（ecs.g7.large）
-- 解除 1 个 SLB 关联（lb-xyz001）
-- 删除关联的数据盘 2 个（共 200 GiB）
-- 该操作不可恢复
-```
-
-### 主操作按钮（明确措辞 + 资源 ID）
-
-- ✅ "确认释放 i-abc123"（destructive variant）
-- ❌ "确定"（措辞含糊）
-- ❌ "OK"（不足以警示）
-
-### L3 必须：资源名校验输入
-
-```
-请输入资源名称 "i-abc123" 以确认：
-[                            ]
-[取消]                [我已确认，继续]  ← 输入正确前置灰
-```
-
----
-
-## 3. 批量高危操作
-
-| 项数 | 处理 |
-|------|------|
-| ≤ 5 项 | AlertDialog 全部列出 |
-| 6 ~ 100 项 | AlertDialog 列出前 5 项 + "及其他 N 项" + 可展开查看全部 |
-| > 100 项 | **拒绝单次执行**；引导用户拆分批次或在 ListPage 加筛选条件 |
-
-执行过程中：
-
-- 显示进度（"正在处理 23/100"）
-- 实时更新成功 / 失败计数
-- 用户可中止剩余批次（已完成的不回滚）
-- 部分失败时，失败项展开"重试" / "跳过"按钮
-
----
-
-## 4. AI 副驾驶场景的高危操作
-
-当 AI 通过场景 A（对话）/ 场景 C（告警诊断）建议高危操作时：
-
-- AI **不得**直接执行 — 必须生成场景 D 的"操作确认卡"
-- 卡片样式：`slide-up` + `gradient-border` + `pulse border (红)` 2s 循环（参见 `motion-scenarios.md` 场景 D）
-- 卡片必须列出：资源 ID / 操作类型 / 影响范围 / 关联资源 / 取消按钮
-- 单次对话 AI 触发的高危操作影响范围 > 10 资源 → 拒绝执行，引导走 CloudListPage
-
----
-
-## 5. 红线（绝对禁止）
-
-- ❌ destructive 操作的默认按钮选中状态（焦点应留在"取消"）
-- ❌ 仅靠红色按钮表达"危险"（必须 + 图标 + 文字）
-- ❌ 在 Toast / Tooltip 内执行写操作
-- ❌ 在命令面板（场景 B）内放删除 / 释放
-- ❌ AI 跳过 D 场景直接执行写操作
-- ❌ AlertDialog 关闭后不留操作日志（必须留痕）

package/skills/teamix-evo-manage/SKILL.md

@@ -1,178 +0,0 @@
----
-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.
-  TRIGGER 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`.
-  SKIP: 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.
-  Coordinates 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.
----
-
-# teamix-evo-manage
-
-This skill helps the user manage the **teamix-evo** toolkit lifecycle inside their project.
-
-<!-- teamix-evo:managed:start id="core" -->
-
-## When to use
-
-Activate when the user wants to **install / update / inspect / remove** any
-teamix-evo package — typically the design system (`@teamix-evo/design`) or the
-skills package (`@teamix-evo/skills`). Common signals:
-
-- "帮我初始化 teamix-evo 设计体系" / "set up @teamix-evo/design"
-- "升级 teamix-evo" / "update teamix-evo skills"
-- "卸载 teamix-evo" / "remove the design system"
-- "看看装了哪些 teamix-evo 资源"
-
-## What you can do for the user
-
-The CLI binary is `teamix-evo` (bin name), backed by the npm package also
-called `teamix-evo`. All operations are split into **package families**:
-
-### Design system (`@teamix-evo/design`)
-
-| Goal              | Command                                                  |
-| ----------------- | -------------------------------------------------------- |
-| Initialize        | `npx teamix-evo design init <variant>`                   |
-| List variants     | `npx teamix-evo design list-variants`                    |
-| List installed    | `npx teamix-evo design list`                             |
-| Update resources  | `npx teamix-evo design update` *(stub — see ADR 0019)*   |
-| Uninstall         | `npx teamix-evo design uninstall [-y] [--keep-files]`    |
-
-- **`<variant>` is required.** No default — you MUST ask the user which
-  business variant (e.g. `opentrek`, `uni-manager`) before running init.
-  Run `npx teamix-evo design list-variants` to enumerate available variants.
-- `design update` is currently a stub; the documented escape hatch is to
-  clean `.teamix-evo/design/` and re-run `design init <variant>` (full
-  semantic upgrade flow scheduled for v0.7 per ADR 0019).
-- Tailwind: v4 only (v3 retired in v0.7).
-- Resources marked `frozen` / `regenerable` are physical files; `managed`
-  files use embedded regions (`<!-- teamix-evo:managed:start id="..." -->`)
-  so the user's custom edits survive updates.
-
-### Skills (`@teamix-evo/skills`)
-
-| Goal           | Command                                   |
-| -------------- | ----------------------------------------- |
-| Add (all)      | `npx teamix-evo skills add`               |
-| Add (one+)     | `npx teamix-evo skills add <name...>`     |
-| List (all)     | `npx teamix-evo skills list` (alias `ls`) |
-| List installed | `npx teamix-evo skills list --installed`  |
-| Update         | `npx teamix-evo skills update`            |
-| Uninstall      | `npx teamix-evo skills uninstall [-y]`    |
-
-`skills add` modes:
-
-- **Bulk** (no positional args): installs every skill declared in the
-  manifest. On a project that already has a skills package installed, returns
-  `already-added`.
-- **Incremental** (one or more skill ids): only installs the listed skills.
-  Skills already present are skipped (use `skills update` to refresh). When the
-  project already has a skills config, `--ide` / `--scope` may be omitted —
-  they default to the previously chosen values.
-
-`skills add` is interactive (only when no prior config and no flags):
-
-1. Multi-select target IDE(s): **Qoder** and/or **Claude Code** (default both,
-   at least one required). Non-interactive equivalent: `--ide qoder,claude`.
-2. Scope: **project** (default; `.qoder/.claude` in cwd) or **global**
-   (`~/.qoder/~/.claude`). Non-interactive: `--scope project|global`.
-
-Skills are installed as `SKILL.md` (Anthropic-compatible frontmatter, also
-recognized by Qoder) under `<base>/skills/<name>/SKILL.md`. Update strategy is
-`managed`, so the user's edits inside SKILL.md outside of the marked regions
-are preserved on `update`.
-
-The source-mirror model (ADR 0013) keeps a canonical copy under
-`.teamix-evo/skills/` and writes IDE-specific mirrors to `.qoder/skills/` and
-`.claude/skills/`. Two diagnostic commands ride on top:
-
-- `npx teamix-evo skills doctor` — detect drift between source and mirrors.
-- `npx teamix-evo skills sync [name...]` — re-mirror the source to all
-  configured IDEs (drift recovery, no version bump).
-
-### UI components (`@teamix-evo/ui`)
-
-| Goal           | Command                                  |
-| -------------- | ---------------------------------------- |
-| Initialize     | `npx teamix-evo ui init [-y]`            |
-| Add entries    | `npx teamix-evo ui add <id...>`          |
-| List entries   | `npx teamix-evo ui list [--installed]`   |
-
-- `ui init` is interactive by default (aliases / iconLibrary / tsx / rsc).
-  Pass `-y` to accept defaults.
-- `ui add` auto-resolves `registryDependencies` and writes component
-  source under `src/components/ui/<id>.tsx` (frozen). Reports the npm
-  packages that still need `pnpm add`.
-- There is **no `ui upgrade` subcommand** — the placeholder→real component
-  migration is owned by the `teamix-evo-ui-upgrade` skill (it drives the
-  loop and calls `ui add` under the hood).
-
-### Variant-aware business UI (`@teamix-evo/biz-ui`)
-
-| Goal           | Command                                                       |
-| -------------- | ------------------------------------------------------------- |
-| List variants  | `npx teamix-evo biz-ui list-variants`                         |
-| Add entries    | `npx teamix-evo biz-ui add <id...> --variant <name>`          |
-
-- **`--variant <name>` is required** for `biz-ui add` (no auto-detect from
-  `design init` yet). Run `list-variants` first to enumerate.
-- Per ADR 0014, `design` / `biz-ui` / `templates` **share one variant-name
-  space**: the variant you picked at `design init` time is the one to pass
-  here (e.g. `opentrek`).
-
-### Variant-aware page templates (`@teamix-evo/templates`)
-
-| Goal           | Command                                                          |
-| -------------- | ---------------------------------------------------------------- |
-| List variants  | `npx teamix-evo templates list-variants`                         |
-| Add entries    | `npx teamix-evo templates add <id...> --variant <name>`          |
-
-- Same `--variant` rule as `biz-ui` (ADR 0014 — shared variant-name space).
-- Writes page-template source under `src/templates/<id>.tsx` (frozen).
-
-## Workflow you should follow
-
-1. **Detect intent.** Confirm which package family the user wants to touch
-   (design / skills / ui / biz-ui / templates — or several).
-2. **Check current state.** Suggest running `npx teamix-evo design list`,
-   `npx teamix-evo skills list`, and `npx teamix-evo ui list` to see what's
-   already installed before changing anything.
-3. **Run the smallest correct command.** Prefer the dedicated lifecycle
-   subcommand. Avoid hand-crafted file edits inside `.qoder/`, `.claude/`, or
-   `.teamix-evo/` — let the CLI write through.
-4. **Report and verify.** After running, summarize what changed (files
-   touched, version, IDE, scope, variant) and re-run `list` if useful.
-
-## Configuration files (informational)
-
-- `<projectRoot>/.teamix-evo/config.json` — declares which packages are
-  installed, their versions, IDE selection and scope.
-- `<projectRoot>/.teamix-evo/manifest.json` — installed-resource ledger;
-  CLI uses it for diffing and uninstalling.
-
-Both are **owned by the CLI**. Don't edit by hand unless the user explicitly
-asks; recommend the CLI subcommand instead.
-
-## Common pitfalls
-
-- The CLI must be run from the project root (where `.teamix-evo/` lives or
-  will be created).
-- For `design uninstall`, `managed` files are kept by default to protect user
-  edits. Use `--keep-files` to keep everything (only updates the ledger).
-- A skill's `description` is the AI trigger contract — keep it specific and
-  scenario-rich when editing.
-
-## Placeholder → real UI upgrade
-
-Projects scaffolded by `npm create teamix-evo` (the default — and currently
-only — preset is `console`) ship with `_placeholder/` components and a
-`.teamix-evo/create/pending-ui.json` file. The migration loop is owned by the
-[`teamix-evo-ui-upgrade`](../teamix-evo-ui-upgrade/SKILL.md) skill — defer to
-it when the user asks to "升级 UI"、"接入真组件"、"replace placeholders".
-
-<!-- teamix-evo:managed:end id="core" -->
-
-## Notes for the user
-
-> 这部分内容由你自由编辑。CLI 升级时只会替换 `id="core"` 区段，不会动这里的笔记。

package/skills/teamix-evo-ui-upgrade/SKILL.md

@@ -1,75 +0,0 @@
----
-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`.
-  TRIGGER 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.
-  SKIP: 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).
-  Coordinates 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).
----
-
-# teamix-evo-ui-upgrade
-
-This skill drives the **placeholder → real component** migration for projects scaffolded by `npm create teamix-evo -- --preset console`. The console preset ships intentionally minimal `_placeholder/` components so the project compiles before any real `@teamix-evo/ui` install. This skill replaces them one by one.
-
-<!-- teamix-evo:managed:start id="core" -->
-
-## When to use
-
-Activate when the user wants to **swap in real UI components** for the placeholders shipped by the console preset. Common signals:
-
-- "升级 UI"、"接入真组件"、"替换 placeholder"
-- "upgrade UI" / "replace placeholders" / "swap in real components"
-- The user opens a file under `src/components/_placeholder/` and asks to evolve it.
-- The grep `@teamix-evo:placeholder` returns hits in code the user is editing.
-- `.teamix-evo/create/pending-ui.json` exists with non-empty `pendingComponents`.
-
-## What this skill does
-
-A 5-step loop, repeated for each pending component:
-
-1. **Read** [`.teamix-evo/create/pending-ui.json`](.teamix-evo/create/pending-ui.json) to get the `pendingComponents` list. Each entry names the component id (e.g. `card`, `input`, `form`, `table`) and its current placeholder file path.
-2. **Install the real component** via the CLI: `npx teamix-evo ui add <id>`. This writes the canonical implementation to `src/components/ui/<id>.tsx`. Per [ADR 0006](../../../docs/adr/0006-ui-upgrade-no-baseline.md), no baseline diff is performed — the real component overrides verbatim.
-3. **Migrate import sites.** Replace `@/components/_placeholder/<Name>` with `@/components/ui/<id>`. The real component's API surface may differ from the placeholder (different prop names, new required props, slot shape changes); adjust each call site to match. Do NOT silence type errors — the prop API is intentional, not noise.
-4. **Delete the placeholder file** once all references migrated. Verify by grepping for the old path returns zero hits.
-5. **Update** `.teamix-evo/create/pending-ui.json`: remove the migrated entry. If `pendingComponents` becomes empty, delete the file entirely.
-
-Repeat until no `pending-ui.json` remains. Then grep for the literal tag `@teamix-evo:placeholder` once more — any remaining hit is a stray placeholder that should also be migrated or deleted.
-
-## Inputs the user provides
-
-- Optional: a specific component id to start with (`card`, `input`, ...). When unspecified, default to processing in the order `pending-ui.json` records.
-- Optional: opt-out — if the user explicitly wants to keep a placeholder, mark it in the user-owned area below and skip on subsequent runs.
-
-## Outputs
-
-- Real `@teamix-evo/ui` components installed under `src/components/ui/`.
-- Old placeholder files removed.
-- Import sites updated (no `_placeholder/` references remain).
-- `pending-ui.json` shrunk or deleted.
-- Per-component migration note in your response: which API surface diverged, which call sites changed.
-
-## Cautions
-
-- The placeholder file ships with **`@teamix-evo:placeholder`** at the top — never leave that tag in production code, it is a literal canary.
-- Real components may bring new dependencies; the CLI handles npm installs. Re-run typecheck after each component migration; fix the migration before moving to the next.
-- Form / Table / DataTable components may require Provider wiring (e.g. `FormProvider`, `useReactTable`). Fix the wiring at the consumer site rather than wrapping it back into `_placeholder/`.
-
-## Files in this skill
-
-| File | Purpose |
-| --- | --- |
-| _(none — this skill is fully procedural; no sub-files)_ | |
-
-## Relationship to other skills
-
-- [`teamix-evo-coding-conventions`](../teamix-evo-coding-conventions/SKILL.md) — when a migration creates new files (provider, hook, type), apply file-placement and reuse-first rules from there.
-- [`teamix-evo-manage`](../teamix-evo-manage/SKILL.md) — the CLI verbs (`ui add`, `update`) come from there; this skill is the orchestration loop.
-- `teamix-evo-design-rules` — only relevant when the migration also reshapes the page layout (e.g. swapping a placeholder Table forces a list-page redesign).
-
-<!-- teamix-evo:managed:end id="core" -->
-
-## Project notes
-
-> Free-form notes the user can add — CLI update will not overwrite below this section.
-
-(empty)