@bovinphang/frontend-craft 2.5.0 → 2.6.0

package/.claude-plugin/marketplace.json

@@ -12,9 +12,13 @@
     "plugins": [
         {
             "name": "frontend-craft",
-            "source": "./",
-            "description": "Enterprise frontend team Claude Code plugin — 13 agents, 40 skills, 8 commands, shared rule templates, and production-ready hooks for code review, TypeScript review, type-safety modeling, state management, Tailwind design systems, responsive layout, dependency upgrades, security review, testing strategy, E2E, component testing, route protection, API integration, interaction motion, performance optimization, scaffolding, design-to-code (Figma/Sketch/MasterGo/Pixso/墨刀/摹客), UI design and polish, Vite standards, legacy-to-modern migration, React/Vue/Next.js/Nuxt/monorepo standards, PWA, Web Workers, Canvas/Three.js, SVG animation, CI/CD, architecture planning, and UI debugging with multi-design-tool MCP integration. All reports auto-saved as Markdown files to reports/ directory.",
-            "version": "2.5.0",
+            "source": {
+                "source": "npm",
+                "package": "@bovinphang/frontend-craft",
+                "version": "2.6.0"
+            },
+            "description": "Enterprise frontend team Claude Code plugin — 13 agents, 41 skills, 8 commands, shared rule templates, and production-ready hooks for code review, TypeScript review, type-safety modeling, state management, Tailwind design systems, responsive layout, dependency upgrades, security review, testing strategy, E2E, component testing, route protection, API integration, interaction motion, performance optimization, scaffolding, design-to-code (Figma/Sketch/MasterGo/Pixso/墨刀/摹客), UI design and polish, Vite standards, legacy-to-modern migration, React/Vue/Next.js/Nuxt/monorepo standards, PWA, Web Workers, Canvas/Three.js, SVG animation, CI/CD, architecture planning, project absorption, and UI debugging with multi-design-tool MCP integration. All reports auto-saved as Markdown files to reports/ directory.",
+            "version": "2.6.0",
             "author": {
                 "name": "Bovin Phang",
                 "email": "pengbaowen@msn.com"

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
     "name": "frontend-craft",
-    "version": "2.5.0",
+    "version": "2.6.0",
     "description": "Shared Claude Code plugin for frontend teams, including frontend skills, subagents, hooks, and MCP integration for Figma/Sketch/MasterGo/Pixso/墨刀/摹客. All reports auto-saved as Markdown files.",
     "author": {
         "name": "Bovin Phang",

package/CHANGELOG.md

@@ -10,6 +10,45 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 Project-facing release notes are maintained in English from 2.0.0 onward. Historical entries may preserve their original language.
 
 
+## [2.6.0] - 2026-06-07
+
+### Added
+
+- **`fec-alchemy` skill:** new project absorption workflow that extracts useful ideas from reference systems and redesigns them into original, project-native improvements; ships with `SKILL.md`, intake / absorption-plan templates, and reference docs covering methodology, originality, and licensing.
+- **`fec setup all` subcommand:** installs frontend-craft for every supported runtime in one shot, defaulting to the current project unless `--global` is passed; help text now distinguishes the terminal `fec setup` command from the in-assistant `/fec-init` slash command.
+- **`fec-debug-framework` in README skill tables:** the skill was already shipped in `skills/` but is now surfaced in every README locale and marketplace metadata.
+- **`scripts/sync-version.ts`:** propagates `package.json` version to `.claude-plugin/plugin.json`, `.claude-plugin/marketplace.json` (including the npm source pin), `openclaw.plugin.json`, and per-skill entries in `skills/metadata.json`. Run via `npm run sync:version`; wired into the `version` lifecycle script.
+- **Skill-pack script minification:** `pack-skills.ts` and `skill-packaging.ts` are now minified with esbuild during build, producing smaller standalone skill packages in `skill-packages/`.
+- **Reference docs for key skills:** added dedicated reference documents for `fec-debug-framework`, `fec-performance-optimization`, `fec-refactor-clean`, and `fec-validation-fix`, linked from the localized "详细参考" section of each `SKILL.md`.
+
+### Changed
+
+- **`fec-doc-sync` scope expansion:** the doc-sync workflow and skill descriptions now cover env notes, scripts, API/route notes, and deploy facts in addition to user-facing docs; example prompts, the `/fec-doc-sync` command doc, and `skills/metadata.json` were updated to match.
+- **Skill taxonomy — new `project-evolution` category:** added to the taxonomy allowlist (in addition to the existing `implementation-capability`, `testing`, `review-quality`, `design-ui`, `legacy-migration`, `maintenance-docs`); `fec-alchemy` lives here, and the README skill tables, marketplace keywords, and `tests/install/metadata-consistency.test.ts` allowlist were updated across all 5 locales.
+- **Skill count:** 40 → 41 across all README locales and `skills/metadata.json`.
+- **README install sections restructured:** the en / zh-CN / zh-TW / ja-JP / ko-KR READMEs were reorganized into 3 install options (down from 4), with numbered steps (1–6), `install --all` examples for both `--local` and `--global`, and a final "Preview / query" step that surfaces `dry-run` and `fec list`. Option 1 is now explicitly "Install the fec CLI globally" so the `npm install -g` step is unambiguous; `Claude Code Marketplace` moved to Option 3 to reflect its position among the paths.
+- **CLI setup help text:** clarified that `npm install -g` only installs the `fec` terminal command and that `--global` is required to write to the AI tool's global config; scripted all-runtime installs must use `install --all`, not `install all`.
+- **`SKILL.md` References localization:** the "References" section header is now rendered as `详细参考` (Detailed References) in every `SKILL.md` to match the existing Chinese-first documentation convention.
+- **`pnpm-lock.yaml`:** now tracked in version control — pnpm is the canonical package manager for the repo.
+- **Marketplace plugin source pin:** `marketplace.json` source entry now follows `package.json` version consistently via `sync-version.ts` instead of being edited by hand.
+- **CLI project setup command:** renamed the terminal project initialization shortcut from `fec init` / `frontend-craft init` to `fec setup` / `frontend-craft setup`; the in-assistant `/fec-init` slash command is unchanged. `src/install/cli.ts` help text, command dispatcher, and default install location updated; `tests/install/cli.test.ts` asserts the new `setup` command and that legacy `init` is rejected.
+
+### Fixed
+
+- **Plugin install command scope:** README, runtime docs, and marketplace descriptions now reference the `@bovinphang/frontend-craft` npm scope consistently; the previous `@frontend-craft` references (no scope) were misleading.
+
+### Removed
+
+- **CLI `init` command:** `init` is no longer accepted as a terminal CLI command and exits with "Unknown command: init"; use `setup` for local project setup.
+
+### Chore
+
+- **`SKILL.md` BOM cleanup:** removed the UTF-8 byte order mark (BOM, U+FEFF) from the first line of 23 `SKILL.md` files; the BOM was rendering as an unknown glyph in some editors and tooling.
+- **JSON metadata formatting:** normalized indentation and trailing-newline conventions in `marketplace.json` and `skills/metadata.json` after the `sync-version.ts` migration.
+- **`CONTRIBUTING` guide:** added scenario-specific check instructions (skill authoring, installer changes, runtime template changes, OpenClaw packaging) so contributors know which commands to run before opening a PR.
+- **Runtime docs:** added build and Marketplace troubleshooting notes to per-runtime install docs under `docs/runtimes/`.
+- **npm package scope migration:** published package is now `@bovinphang/frontend-craft`; install commands, `pack:skills` output paths, README badges, and OpenClaw staging paths were updated in lockstep.
+
 
 ## [2.5.0] - 2026-06-01
 

package/CHANGELOG.zh-CN.md

@@ -10,6 +10,46 @@
 
 
 
+## [2.6.0] - 2026-06-07
+
+### 新增
+
+- **`fec-alchemy` 技能**：新增「项目吸收与原创化融合」工作流，从参考系统提取可借鉴的设计并以项目原生方式重构为原创能力；随附 `SKILL.md`、intake / absorption-plan 模板，以及涵盖方法论、原创性、许可证的参考文档。
+- **`fec setup all` 子命令**：一键为所有受支持的 runtime 安装 frontend-craft，默认安装到当前项目，除非显式传入 `--global`；帮助文本现在区分终端 `fec setup` 命令与 AI 助手内的 `/fec-init` 斜杠命令。
+- **README 技能表补全 `fec-debug-framework`**：该技能此前已在 `skills/` 中提供，现统一收录到各语言 README 技能表与 marketplace 元数据中。
+- **`scripts/sync-version.ts`**：将 `package.json` 的版本号同步到 `.claude-plugin/plugin.json`、`.claude-plugin/marketplace.json`（包含 npm source 钉版）、`openclaw.plugin.json`，以及 `skills/metadata.json` 的每条技能记录。可通过 `npm run sync:version` 执行；已接入 `version` 生命周期脚本。
+- **技能打包脚本压缩**：`pack-skills.ts` 与 `skill-packaging.ts` 在构建期通过 esbuild 压缩，输出到 `skill-packages/` 的独立技能包体积更小。
+- **关键技能参考文档**：为 `fec-debug-framework`、`fec-performance-optimization`、`fec-refactor-clean`、`fec-validation-fix` 新增独立参考文档，从各 `SKILL.md` 本地化后的「详细参考」一节链接。
+
+### 变更
+
+- **`fec-doc-sync` 同步范围扩展**：文档同步工作流与技能描述现在覆盖环境变量说明、脚本、接口/路由说明与部署文档，不再局限于面向用户的文档；示例提示词、`/fec-doc-sync` 命令文档以及 `skills/metadata.json` 同步更新。
+- **技能分类新增 `project-evolution`**：在原 `implementation-capability` / `testing` / `review-quality` / `design-ui` / `legacy-migration` / `maintenance-docs` 之外新增 `project-evolution`，`fec-alchemy` 归入此类；各语言 README 技能表、marketplace 关键词以及 `tests/install/metadata-consistency.test.ts` 白名单同步更新。
+- **技能数量**：40 → 41，已同步到各语言 README 与 `skills/metadata.json`。
+- **README 安装章节重构**：en / zh-CN / zh-TW / ja-JP / ko-KR 五种语言的 README 重新组织为 3 个安装选项（从 4 个收敛），步骤编号 1–6，并补充 `--local` / `--global` 两种场景下的 `install --all` 示例，新增「Preview / query」步骤展示 `dry-run` 与 `fec list`。「选项 1」改为「全局安装 fec CLI」，使 `npm install -g` 步骤不再有歧义；Claude Code Marketplace 下移至「选项 3」。
+- **CLI setup 帮助文本**：明确说明 `npm install -g` 仅安装终端 `fec` 命令，若要写入 AI 工具的全局配置需额外传 `--global`；脚本化的全 runtime 安装必须使用 `install --all`，不能使用 `install all`。
+- **`SKILL.md` References 本地化**：每份 `SKILL.md` 的「References」章节标题统一为「详细参考」，与既有中文优先的文档约定一致。
+- **`pnpm-lock.yaml` 纳入版本控制**：pnpm 已成为仓库规范化的包管理器。
+- **Marketplace 插件 source 钉版**：`marketplace.json` 的 source 字段现由 `sync-version.ts` 与 `package.json` 保持一致，无需手工修改。
+- **CLI 项目 setup 命令重命名**：终端里的项目初始化快捷命令从 `fec init` / `frontend-craft init` 重命名为 `fec setup` / `frontend-craft setup`；AI 助手内的 `/fec-init` 斜杠命令保持不变。`src/install/cli.ts` 的帮助文本、命令分发与默认安装位置同步更新；`tests/install/cli.test.ts` 已断言新 `setup` 命令并校验旧 `init` 会被拒绝。
+
+### 修复
+
+- **插件安装命令作用域**：README、runtime 文档与 marketplace 描述现在统一引用 `@bovinphang/frontend-craft` npm 作用域；先前未带作用域的 `@frontend-craft` 引用已修正。
+
+### 移除
+
+- **CLI `init` 命令**：终端 CLI 不再接受 `init`，遇到时直接退出并提示「Unknown command: init」；本地项目 setup 请改用 `setup`。
+
+### 工程
+
+- **`SKILL.md` BOM 清理**：从 23 份 `SKILL.md` 的首行移除 UTF-8 字节顺序标记（BOM, U+FEFF），避免部分编辑器与工具把首字符渲染为不可识别字形。
+- **JSON 元数据格式统一**：`sync-version.ts` 迁移后，统一 `marketplace.json` 与 `skills/metadata.json` 的缩进与末尾换行规范。
+- **`CONTRIBUTING` 贡献指南**：补充分场景的检查指引（技能编写、安装器变更、runtime 模板变更、OpenClaw 打包），让贡献者在提 PR 前明确应执行哪些命令。
+- **Runtime 文档**：在 `docs/runtimes/` 的各 runtime 安装文档中补充构建与 Marketplace 排错说明。
+- **npm 包作用域迁移**：发布包更名为 `@bovinphang/frontend-craft`；安装命令、`pack:skills` 输出路径、README 徽标与 OpenClaw staging 路径同步刷新。
+
+
 ## [2.5.0] - 2026-06-01
 
 ### 新增

package/CONTRIBUTING.md

@@ -10,15 +10,19 @@ Thanks for your interest in `frontend-craft`. Issues, pull requests, documentati
 - Git.
 - Run `npm install` before local development.
 
-Useful checks:
+For documentation-only changes, focus on the language and documentation policy plus the pull request checklist. For skill or OpenClaw changes, use the focused sections below before opening a pull request.
+
+Quick checks (minimum recommended):
 
 ```bash
-npm test
-npm run pack:skills
-npm run check:skills-publish
-npm run typecheck:openclaw
+npm test                         # General validation
+npm run pack:skills              # Skill changes
+npm run check:skills-publish     # Skill changes
+npm run typecheck:openclaw       # OpenClaw changes
 ```
 
+See the NPM Scripts section and Pull Request Checklist for complete scenario-specific checks.
+
 ## Project Structure
 
 ```
@@ -112,7 +116,7 @@ The canonical skill sources live under `skills/<skill-id>/`. Do not edit generat
 ```bash
 npm run pack:skills            # Build one standalone package per skill
 npm run check:skills-publish   # Verify package metadata, index, and copied references
-npm run pack:all               # Full test + OpenClaw package + standalone skill packages
+npm run pack:all               # Build + test + OpenClaw package + standalone skill packages
 ```
 
 `npm run pack:skills` writes `skill-packages/<skill-id>/` with `SKILL.md`, only the referenced `references/` files, `metadata.json`, `package.json`, `README.md`, and `LICENSE`. It also writes `skill-packages/index.json` for platform crawlers and release automation.
@@ -131,7 +135,7 @@ Use `package.json` scripts as the public development entrypoints.
 | Script                         | Purpose                                                                          |
 | ------------------------------ | -------------------------------------------------------------------------------- |
 | `npm run clean`                | Remove `dist/`.                                                                  |
-| `npm run typecheck`            | Run TypeScript checking for the main project with `tsconfig.json`.               |
+| `npm run typecheck`            | Run main TypeScript checks plus checked skill support scripts.                   |
 | `npm run build`                | Run `clean`, `typecheck`, and bundle CLI/hooks via `scripts/build-dist.ts`.      |
 | `npm test`                     | Build, then run the curated `node:test` suite with `tsx`.                        |
 | `npm run build:openclaw`       | Build the main project, then bundle OpenClaw runtime output.                     |
@@ -139,9 +143,9 @@ Use `package.json` scripts as the public development entrypoints.
 | `npm run typecheck:openclaw`   | Run TypeScript checking for OpenClaw with `tsconfig.openclaw.json`.              |
 | `npm run check:openclaw-dist`  | Verify the generated OpenClaw dist output.                                       |
 | `npm run pack:openclaw`        | Build, verify, and package the OpenClaw plugin.                                  |
-| `npm run pack:skills`          | Build standalone packages under `skill-packages/`.                               |
-| `npm run check:skills-publish` | Build, then verify standalone skill package metadata and copied files.           |
-| `npm run pack:all`             | Run tests, package OpenClaw, package skills, and verify skill publishing output. |
+| `npm run pack:skills`          | Build first, then create standalone packages under `skill-packages/`.            |
+| `npm run check:skills-publish` | Build first, then verify standalone skill package metadata and copied files.     |
+| `npm run pack:all`             | Build, run tests, package OpenClaw, package skills, and verify skill output.     |
 | `npm run sync:version`         | Sync package version metadata across release manifests.                          |
 | `npm run version`              | Run `sync:version`, then stage versioned manifests for npm version workflows.    |
 | `npm run prepack`              | Build before `npm pack`.                                                         |
@@ -161,6 +165,7 @@ Maintenance scripts live under `scripts/` and run from source with `tsx`; they a
 | ------------------------------------------ | ------------------------------------ |
 | `scripts/audit-skills.ts`                  | Skill size and trigger-overlap audit |
 | `scripts/build-dist.ts`                    | CLI and runtime hook bundler         |
+| `scripts/clean-dist.mjs`                   | Remove generated `dist/` output      |
 | `scripts/sync-codex-agents-toml.ts`        | Sync Codex agents configuration      |
 | `scripts/sync-version.ts`                  | Sync release version metadata        |
 | `scripts/pack-skills.ts`                   | Standalone skill package builder     |

package/CONTRIBUTING.zh-CN.md

@@ -10,15 +10,19 @@
 - Git。
 - 本地开发前运行 `npm install`。
 
-常用校验：
+仅修改文档时，重点阅读语言与文档策略以及 Pull Request 自检。修改 skill 或 OpenClaw 时，请在提交 PR 前参考下方对应章节。
+
+快速自检（最小推荐）：
 
 ```bash
-npm test
-npm run pack:skills
-npm run check:skills-publish
-npm run typecheck:openclaw
+npm test                         # 通用校验
+npm run pack:skills              # Skill 变更
+npm run check:skills-publish     # Skill 变更
+npm run typecheck:openclaw       # OpenClaw 变更
 ```
 
+完整的场景化命令请见后文 npm scripts 与 Pull Request 自检。
+
 ## 项目结构
 
 ```
@@ -112,7 +116,7 @@ Skill 的权威源文件位于 `skills/<skill-id>/`。不要手动修改 `skill-
 ```bash
 npm run pack:skills            # 为每个 skill 生成独立发布包
 npm run check:skills-publish   # 校验包元数据、索引和引用文件
-npm run pack:all               # 完整测试 + OpenClaw 包 + 独立 skill 包
+npm run pack:all               # 构建 + 测试 + OpenClaw 包 + 独立 skill 包
 ```
 
 `npm run pack:skills` 会生成 `skill-packages/<skill-id>/`，其中包含 `SKILL.md`、该 skill 实际引用的 `references/` 文件、`metadata.json`、`package.json`、`README.md` 和 `LICENSE`。同时会生成 `skill-packages/index.json`，供平台索引或发布自动化使用。
@@ -131,7 +135,7 @@ npm run pack:all               # 完整测试 + OpenClaw 包 + 独立 skill 包
 | Script                         | 用途                                                                       |
 | ------------------------------ | -------------------------------------------------------------------------- |
 | `npm run clean`                | 删除 `dist/`。                                                             |
-| `npm run typecheck`            | 使用 `tsconfig.json` 对主项目做 TypeScript 类型检查。                      |
+| `npm run typecheck`            | 运行主项目 TypeScript 检查，并检查 skill 辅助脚本。                        |
 | `npm run build`                | 运行 `clean`、`typecheck`，并通过 `scripts/build-dist.ts` 打包 CLI/hooks。 |
 | `npm test`                     | 先构建，再通过 `tsx` 运行精选的 `node:test` 测试集。                       |
 | `npm run build:openclaw`       | 构建主项目，然后打包 OpenClaw runtime 输出。                               |
@@ -139,9 +143,9 @@ npm run pack:all               # 完整测试 + OpenClaw 包 + 独立 skill 包
 | `npm run typecheck:openclaw`   | 使用 `tsconfig.openclaw.json` 检查 OpenClaw 类型。                         |
 | `npm run check:openclaw-dist`  | 校验生成的 OpenClaw dist 输出。                                            |
 | `npm run pack:openclaw`        | 构建、校验并打包 OpenClaw 插件。                                           |
-| `npm run pack:skills`          | 在 `skill-packages/` 下生成独立 skill 包。                                 |
-| `npm run check:skills-publish` | 构建后校验独立 skill 包元数据与复制文件。                                  |
-| `npm run pack:all`             | 运行测试、打包 OpenClaw、打包 skills，并校验 skill 发布产物。              |
+| `npm run pack:skills`          | 先构建，再在 `skill-packages/` 下生成独立 skill 包。                       |
+| `npm run check:skills-publish` | 先构建，再校验独立 skill 包元数据与复制文件。                              |
+| `npm run pack:all`             | 构建、运行测试、打包 OpenClaw、打包 skills，并校验 skill 产物。             |
 | `npm run sync:version`         | 同步发布清单中的 package 版本元数据。                                      |
 | `npm run version`              | 运行 `sync:version`，并为 npm version 工作流暂存版本清单。                 |
 | `npm run prepack`              | 在 `npm pack` 前构建。                                                     |
@@ -161,6 +165,7 @@ npm run pack:all               # 完整测试 + OpenClaw 包 + 独立 skill 包
 | ------------------------------------------ | ------------------------------ |
 | `scripts/audit-skills.ts`                  | Skill 大小与触发描述重叠度审计 |
 | `scripts/build-dist.ts`                    | CLI 与 runtime hook 打包       |
+| `scripts/clean-dist.mjs`                   | 删除生成的 `dist/` 输出        |
 | `scripts/sync-codex-agents-toml.ts`        | 同步 Codex agents 配置         |
 | `scripts/sync-version.ts`                  | 同步发布版本元数据             |
 | `scripts/pack-skills.ts`                   | 独立 skill 包构建              |

package/README.md

@@ -8,7 +8,7 @@
 
 [![Stars](https://img.shields.io/github/stars/bovinphang/frontend-craft?style=flat)](https://github.com/bovinphang/frontend-craft/stargazers)
 [![CI](https://github.com/bovinphang/frontend-craft/actions/workflows/ci.yml/badge.svg)](https://github.com/bovinphang/frontend-craft/actions/workflows/ci.yml)
-[![npm version](https://img.shields.io/npm/v/frontend-craft)](https://www.npmjs.com/package/frontend-craft)
+[![npm version](https://img.shields.io/npm/v/@bovinphang/frontend-craft)](https://www.npmjs.com/package/@bovinphang/frontend-craft)
 [![License](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
 ![Node](https://img.shields.io/badge/Node.js-22+-5FA04E?logo=node.js&logoColor=white)
 ![TypeScript](https://img.shields.io/badge/-TypeScript-3178C6?logo=typescript&logoColor=white)
@@ -32,7 +32,7 @@
 
 Per-runtime paths and caveats live in [`docs/runtimes/`](docs/runtimes/).
 
-It bundles **13 specialized agents**, **40 auto-activated skills**, **8 slash commands**, **5 event-driven hooks**, **MCP integrations** for 6 design-tool endpoints, and a complete **rules library** into a single installable package. Run one command, and every AI session on your team writes React, Vue, Next.js, or Nuxt the same way — typed, accessible, secure, and consistent.
+It bundles **13 specialized agents**, **41 auto-activated skills**, **8 slash commands**, **5 event-driven hooks**, **MCP integrations** for 6 design-tool endpoints, and a complete **rules library** into a single installable package. Run one command, and every AI session on your team writes React, Vue, Next.js, or Nuxt the same way — typed, accessible, secure, and consistent.
 
 ---
 
@@ -40,7 +40,7 @@ It bundles **13 specialized agents**, **40 auto-activated skills**, **8 slash co
 
 | Problem                                                              | What frontend-craft does                                                                       |
 | -------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- |
-| AI assistants write inconsistent, untyped, or insecure frontend code | **40 skills** encode team standards — auto-activated when the assistant touches matching files |
+| AI assistants write inconsistent, untyped, or insecure frontend code | **41 skills** encode team standards — auto-activated when the assistant touches matching files |
 | Each AI tool has its own plugin format                               | **One CLI** installs the same rules, agents, and hooks into 15 runtimes                        |
 | Design-to-code handoff is lossy                                      | **MCP integrations** bring in richer context from Figma, Figma Desktop, Sketch, MasterGo, Pixso, and 墨刀 |
 | Reviews are ad-hoc and shallow                                       | **13 agents** produce graded reports: code, security, a11y, performance, TS, UI fidelity       |
@@ -53,45 +53,59 @@ It bundles **13 specialized agents**, **40 auto-activated skills**, **8 slash co
 
 Requires **Node.js 22+**. Works on **Windows, macOS, and Linux**.
 
-### Option 1 - Global CLI project init (recommended)
+### Option 1 - Install the fec CLI globally (recommended)
 
 ```bash
-npm install -g frontend-craft@latest
+# 1. Install the fec command globally
+npm install -g @bovinphang/frontend-craft@latest
+
+# 2. Go to your frontend project
 cd your-project
-fec init
-fec init codex      # initialize for a specific runtime
-fec init claude     # initialize for Claude Code
-```
 
-`fec init` is the terminal CLI command for initializing the current project. In an interactive terminal, omit the runtime to choose one from the prompt; in non-interactive terminals, the CLI defaults to `claude` when no runtime is specified. `init` installs locally by default unless you explicitly pass `--global`, for example `fec init codex --global`. The in-assistant `/fec-init` slash command is separate and runs after frontend-craft is installed in your AI runtime.
+# 3. Choose the AI runtime(s) interactively
+fec setup
 
-### Option 2 — No-global interactive wizard
+# 4. Connect the current project
+fec setup codex
+fec setup claude
+fec setup all
 
-```bash
-npx frontend-craft@latest
+# 5. Connect globally, available across all projects
+fec setup codex --global
+fec setup claude --global
+fec setup all --global
+
+# 6. Preview / query
+fec install --all --dry-run --global
+fec list
 ```
 
-Use this when you do not want to install a global `fec` command. The wizard walks through the full install flow: choose one or more runtimes, then choose whether to install globally or into the current project.
+`npm install -g` only installs the `fec` terminal command. `fec setup` is the terminal CLI command for connecting frontend-craft to a project; it is not the in-assistant `/fec-init` slash command. In an interactive terminal, running only `fec setup` asks you to choose runtimes. `fec setup <runtime>` and `fec setup all` connect frontend-craft to the current project by default. Only pass `--global` when you want to connect frontend-craft to the selected AI tool's global config directory so it is available across projects.
 
-### Option 3 — Scripted install
+### Option 2 — Temporary npx run (no global fec command)
 
 ```bash
-# Install into the current project
-npx frontend-craft@latest install --local claude
-
-# Install globally for a runtime
-npx frontend-craft@latest install --global codex
-
-# Preview what would be installed across all runtimes
-npx frontend-craft@latest install --all --dry-run --global
-
-# List available runtimes
-npx frontend-craft@latest list
+# 1. Interactive wizard
+npx @bovinphang/frontend-craft@latest
+
+# 2. Connect the current project
+npx @bovinphang/frontend-craft@latest install --local codex
+npx @bovinphang/frontend-craft@latest install --local claude
+npx @bovinphang/frontend-craft@latest install --all --local
+
+# 3. Connect globally, available across all projects
+npx @bovinphang/frontend-craft@latest install --global codex
+npx @bovinphang/frontend-craft@latest install --global claude
+npx @bovinphang/frontend-craft@latest install --all --global
+
+# 4. Preview / query
+npx @bovinphang/frontend-craft@latest install --all --dry-run --global
+npx @bovinphang/frontend-craft@latest list
 ```
 
-> **CI / scripts:** always pass `--global` / `-g` or `--local` / `-l`. Without a TTY, the CLI defaults to `claude --global` if neither is set.
+Use `npx` when you do not want to install a global `fec` command. Without arguments, it opens the interactive wizard: choose one or more runtimes, then choose whether to connect globally or into the current project. For scripted all-runtime installs, use `install --all --local` or `install --all --global`; do not write `install all`. For CI / scripts, always pass `--global` / `-g` or `--local` / `-l`; in non-TTY environments without an explicit location, the CLI defaults to `claude --global`.
 
-### Option 4 — Claude Code Marketplace
+### Option 3 — Claude Code Marketplace
 
 For Claude Code users, **Claude Code Marketplace** is the preferred single-source install. Use the CLI for Claude only when you need cross-runtime installs, scripted/offline file copies, or non-Marketplace environments.
 
@@ -133,7 +147,7 @@ For a complete scenario-based prompt library, see [docs/example-prompts.md](docs
 ```text
 You: "Review my recent changes before merge. Focus on architecture, type safety, rendering behavior, styles, accessibility, and missing tests."
 You: "Before coding, plan the account billing feature: route structure, component boundaries, data flow, state ownership, validation flow, and rollout risks."
-You: "Build a multi-step registration form with React Hook Form + Zod, file upload, conditional fields, async validation, and accessible errors."
+You: "Build a multi-step registration form; choose the right form and schema validation approach for this project, with file upload, conditional fields, async validation, and accessible errors."
 You: "Implement the UI from Figma node 123:456. Use existing design tokens and components, match spacing and responsive states, and document assumptions."
 You: "`/fec-refactor-clean` Clean up dead code in this module."
 ```
@@ -155,13 +169,13 @@ Slash commands are the primary entry points for structured workflows. Most produ
 | `/fec-tdd`            | Red → green → refactor loop for frontend TDD                           | —                                                |
 | `/fec-debug`          | Diagnose and fix frontend issues: build, runtime, UI, and API failures | `debug-*.md`                                     |
 | `/fec-refactor-clean` | Classify and safely remove dead code, unused exports, styles, and deps | `refactor-clean-*.md`                            |
-| `/fec-doc-sync`       | Sync READMEs, runtime docs, capability tables, and metadata            | —                                                |
+| `/fec-doc-sync`       | Sync READMEs, docs, env notes, scripts, API/route notes, and deploy docs | —                                                |
 
 ### Skills (auto-activated)
 
 Skills are workflow definitions that activate automatically based on file patterns, frameworks, or task context. They encode review dimensions, output conventions, and report formats.
 
-The skills below are grouped by use case so you can quickly find project standards, implementation, testing, review, design, migration, and documentation workflows.
+The skills below are grouped by use case so you can quickly find project standards, implementation, testing, review, design, migration, project evolution, and documentation workflows.
 
 **Project standards** — conventions enforced whenever matching frameworks are detected:
 
@@ -178,17 +192,17 @@ The skills below are grouped by use case so you can quickly find project standar
 
 | Skill                     | Scope                                                                     |
 | ------------------------- | ------------------------------------------------------------------------- |
-| `fec-data-fetching`       | TanStack Query / server-state fetching, caching, optimistic updates       |
+| `fec-data-fetching`       | Server-state fetching, caching, invalidation, SSR, infinite loading       |
 | `fec-api-integration`     | Typed API clients, auth refresh, uploads, realtime integration            |
 | `fec-state-management`    | State ownership, store selection, URL state, server/form/local boundaries |
-| `fec-form-handling`       | React Hook Form + Zod, dynamic fields, uploads, multi-step flows          |
+| `fec-form-handling`       | Framework-aware forms, schema validation, dynamic fields, uploads         |
 | `fec-browser-storage`     | localStorage / sessionStorage / IndexedDB / Cookies selection             |
 | `fec-route-protection`    | Auth and permission routes for React Router, Next.js, Vue Router, Nuxt    |
 | `fec-pwa-implementation`  | Manifest, service worker, offline cache, install prompts                  |
 | `fec-web-workers`         | Web Worker integration, transferables, Comlink, worker pools              |
 | `fec-canvas-threejs`      | Canvas 2D, Three.js, React Three Fiber, WebGL                             |
 | `fec-svg-animation`       | CSS / Framer Motion / GSAP SVG animation with reduced-motion              |
-| `fec-list-virtualization` | react-window / TanStack Virtual with measurement strategies               |
+| `fec-list-virtualization` | Framework-aware list virtualization, measurement, grids, infinite scroll  |
 
 **Testing** — activated when planning or authoring frontend test coverage:
 
@@ -204,6 +218,7 @@ The skills below are grouped by use case so you can quickly find project standar
 | Skill                          | Scope                                                                         |
 | ------------------------------ | ----------------------------------------------------------------------------- |
 | `fec-code-review`              | Architecture, types, rendering, styles, a11y review                           |
+| `fec-debug-framework`          | Systematic diagnostics for build, runtime, UI, and API/data failures          |
 | `fec-typescript-type-safety`   | Type contracts, DTO mapping, type guards, generics, type-level checks         |
 | `fec-security-review`          | XSS, CSRF, sensitive data leakage, input validation                           |
 | `fec-accessibility-check`      | WCAG 2.2, keyboard, focus, touch, and screen-reader behavior                  |
@@ -228,13 +243,19 @@ The skills below are grouped by use case so you can quickly find project standar
 | Skill                            | Scope                                                      |
 | -------------------------------- | ---------------------------------------------------------- |
 | `fec-legacy-web-standard`        | Standards for JS + jQuery + HTML maintenance               |
-| `fec-legacy-to-modern-migration` | jQuery/MPA → React/Vue 3 + TS strategy and phased workflow |
+| `fec-legacy-to-modern-migration` | Legacy frontend modernization, target-stack selection, phased workflow |
+
+**Project evolution** — activated when absorbing reference systems into project-native improvements:
+
+| Skill         | Scope                                                                  |
+| ------------- | ---------------------------------------------------------------------- |
+| `fec-alchemy` | Absorb reference system ideas through original, project-native redesign |
 
 **Maintenance docs** — activated during documentation upkeep:
 
 | Skill                           | Scope                                                                                  |
 | ------------------------------- | -------------------------------------------------------------------------------------- |
-| `fec-doc-sync`                  | Keep public docs in sync with scripts, skills, agents, commands                        |
+| `fec-doc-sync`                  | Keep frontend docs in sync with code, config, scripts, routes, APIs, env, and deploy facts |
 | `fec-source-driven-development` | Verify version-sensitive frontend decisions against project facts and official sources |
 
 ### Agents
@@ -365,11 +386,12 @@ $env:MODAO_TOKEN = "your-modao-token"
 Every review, analysis, and evaluation writes a timestamped Markdown report to `reports/`. These serve as an audit trail and a handoff artifact for PRs.
 
 <details>
-<summary>Click to see all 15 report types</summary>
+<summary>Click to see all 16 report types</summary>
 
 | Report type            | Filename pattern                             | Produced by                                                         |
 | ---------------------- | -------------------------------------------- | ------------------------------------------------------------------- |
 | Code review            | `code-review-YYYY-MM-DD-HHmmss.md`           | `/fec-review`, `fec-code-review`, `fec-code-reviewer`               |
+| Debug diagnostics      | `debug-YYYY-MM-DD-HHmmss.md`                 | `/fec-debug`, `fec-debug-framework`, `fec-debugger`                 |
 | TypeScript / JS review | `typescript-review-YYYY-MM-DD-HHmmss.md`     | `fec-typescript-reviewer`                                           |
 | Security review        | `security-review-YYYY-MM-DD-HHmmss.md`       | `fec-security-review`, `fec-security-reviewer`                      |
 | Accessibility          | `accessibility-review-YYYY-MM-DD-HHmmss.md`  | `fec-accessibility-check`                                           |
@@ -393,7 +415,7 @@ Every review, analysis, and evaluation writes a timestamped Markdown report to `
 
 ## Update and Remove
 
-`fec` is the short command for `frontend-craft`. If you have not installed the global `fec` command, use the same arguments with `npx frontend-craft@latest`, for example `npx frontend-craft@latest update`.
+`fec` is the short command for `frontend-craft`. If you have not installed the global `fec` command, use the same arguments with `npx @bovinphang/frontend-craft@latest`, for example `npx @bovinphang/frontend-craft@latest update`.
 
 ### Update
 
@@ -437,7 +459,7 @@ npx skills check                           # preview available updates
 
 | CLI                  | Installs                                                            |
 | -------------------- | ------------------------------------------------------------------- |
-| `npx frontend-craft` | Skills + runtime-specific agents, commands, hooks, rules, templates |
+| `npx @bovinphang/frontend-craft` | Skills + runtime-specific agents, commands, hooks, rules, templates |
 | `npx skills`         | Skills only (for existing Skills CLI workflows)                     |
 
 To disable telemetry: `DISABLE_TELEMETRY=1`. Details: [skills.sh CLI docs](https://skills.sh/docs/cli).

package/README.openclaw.md

@@ -146,22 +146,22 @@ frontend-craft/
 | `fec-implement-from-design`      | Implement UI from Figma, Sketch, MasterGo, Pixso, Modao, or screenshots              |
 | `fec-validation-fix`             | Run validation commands, diagnose failures, and fix safely                           |
 | `fec-legacy-web-standard`        | JavaScript + jQuery + HTML/CSS legacy frontend standards                             |
-| `fec-legacy-to-modern-migration` | jQuery / MPA migration strategy to React or Vue + TypeScript                         |
+| `fec-legacy-to-modern-migration` | Legacy frontend modernization, target-stack selection, and phased migration          |
 | `fec-testing-strategy`           | Testing layer selection, risk matrix, and coverage planning                          |
 | `fec-e2e-testing`                | Playwright / Cypress E2E structure, artifacts, CI, and flaky test handling           |
 | `fec-nextjs-project-standard`    | Next.js App Router, SSR/SSG, routing, metadata, middleware                           |
 | `fec-nuxt-project-standard`      | Nuxt 3 SSR/SSG, composables, routing, middleware                                     |
 | `fec-monorepo-project-standard`  | pnpm workspace, Turborepo, Nx structure and task orchestration                       |
-| `fec-data-fetching`              | TanStack Query / server-state fetching, caching, invalidation, optimistic updates    |
+| `fec-data-fetching`              | Server-state fetching, caching, invalidation, SSR, and infinite loading              |
 | `fec-state-management`           | State ownership, store selection, URL/server/form/local state boundaries             |
-| `fec-form-handling`              | React Hook Form + Zod forms, dynamic fields, uploads, multi-step flows               |
+| `fec-form-handling`              | Framework-aware forms, schema validation, dynamic fields, uploads, multi-step flows  |
 | `fec-tailwind-design-system`     | Tailwind tokens, theme extension, variants, class governance, dark mode              |
 | `fec-responsive-layout`          | Mobile-first layouts, container queries, data-dense responsive UI                    |
 | `fec-browser-storage`            | localStorage/sessionStorage/IndexedDB/Cookies selection and safe client persistence  |
 | `fec-route-protection`           | Authenticated and permissioned routes for React Router, Next.js, Vue Router, Nuxt    |
 | `fec-component-testing`          | React Testing Library / Vue Test Utils component tests and regression scenarios      |
 | `fec-storybook-component-doc`    | Storybook component docs, addons, MDX, interaction and visual test integration       |
-| `fec-list-virtualization`        | Large-list windowing with react-window / TanStack Virtual and measurement strategies |
+| `fec-list-virtualization`        | Framework-aware virtualization, item measurement, grids, and infinite scrolling      |
 | `fec-pwa-implementation`         | Manifest, service worker, offline cache, install prompts, update handling            |
 | `fec-web-workers`                | Web Worker integration, transferable objects, Comlink, worker pools                  |
 | `fec-canvas-threejs`             | Canvas 2D, Three.js, React Three Fiber, WebGL performance and accessibility          |
@@ -195,19 +195,19 @@ This section is a quick OpenClaw-oriented sample, not the full prompt catalog. F
 | Implement from Figma / screenshot          | `fec-implement-from-design`      | “Implement this screen from Figma node `123:456`: match spacing and design tokens, reuse our `Button`, and note any assumptions.”                |
 | CI red or local script failures            | `fec-validation-fix`             | “`pnpm lint` and `pnpm test` are failing—find the root causes, fix them, and don’t weaken types or skip checks.”                                 |
 | Maintain jQuery / MPA legacy pages         | `fec-legacy-web-standard`        | “For `public/js/legacy/*.js`, suggest safe refactors and patterns that keep current behavior; we still ship this in production.”                 |
-| Plan jQuery → React/Vue migration          | `fec-legacy-to-modern-migration` | “We have `static/app.js` in jQuery + MPA. Outline a phased migration to React + TypeScript with risks and milestones.”                           |
+| Plan legacy frontend modernization         | `fec-legacy-to-modern-migration` | “We have `static/app.js` in jQuery + MPA. Evaluate keeping the MPA, local modernization, or moving to our target stack with risks and milestones.” |
 | Plan frontend test coverage                | `fec-testing-strategy`           | “For this checkout refactor, map risks to static checks, unit/component tests, E2E, visual, a11y, and security coverage before we write tests.”  |
 | Add or stabilize E2E                       | `fec-e2e-testing`                | “Add a Playwright smoke test for login; use a clear folder layout and Page Objects, and mention how to run it in CI.”                            |
 | Next.js App Router feature                 | `fec-nextjs-project-standard`    | “Review `app/(dashboard)/reports/page.tsx` and related server actions for Next.js App Router best practices (data fetching, errors, metadata).”  |
 | Nuxt 3 feature or layout                   | `fec-nuxt-project-standard`      | “Review `pages/admin/*.vue` and `composables/useApi.ts` for Nuxt 3 SSR/data/composables conventions.”                                            |
 | Monorepo boundaries and tasks              | `fec-monorepo-project-standard`  | “`apps/web` depends on `packages/ui`—check package boundaries, workspace config, and Turborepo task graph for issues.”                           |
-| Server-state data fetching                 | `fec-data-fetching`              | “Review `src/queries/useReports.ts` for TanStack Query patterns: caching keys, invalidation, and optimistic updates.”                            |
+| Server-state data fetching                 | `fec-data-fetching`              | “Review `src/data/reports.ts` for server-state fetching, cache keys, invalidation, SSR hydration, and whether a query library is warranted.”       |
 | State ownership and store selection        | `fec-state-management`           | “Audit our dashboard state: decide what belongs in URL params, TanStack Query, local state, or the global store, then propose a safe migration.” |
-| Complex form with validation               | `fec-form-handling`              | “Build a multi-step registration form with Zod validation, file upload, and dynamic conditional fields using React Hook Form.”                   |
+| Complex form with validation               | `fec-form-handling`              | “Build a multi-step registration form; choose the project-appropriate form library and schema validation approach, with uploads and dynamic fields.” |
 | Add route guards to an app                 | `fec-route-protection`           | “Secure the `/admin` routes in our React Router app: redirect unauthenticated users and enforce role-based access.”                              |
 | Write component unit tests                 | `fec-component-testing`          | “Add RTL tests for `src/components/UserCard.tsx`: render, user-event interactions, and snapshot for regression.”                                 |
 | Document a component library               | `fec-storybook-component-doc`    | “Set up Storybook for `packages/ui/` with MDX docs, accessibility addon, and interaction tests.”                                                 |
-| Render thousands of list rows              | `fec-list-virtualization`        | “Our `ProductList` renders 10k items—virtualize it with react-window or TanStack Virtual and measure scroll performance.”                        |
+| Render thousands of list rows              | `fec-list-virtualization`        | “Our `ProductList` renders 10k items—choose a virtualization approach for our framework, dynamic heights, browser search, and SEO constraints.”   |
 | Add offline support                        | `fec-pwa-implementation`         | “Make this React app a PWA: manifest, service worker, offline cache strategy, and install prompt.”                                               |
 | Heavy computation off main thread          | `fec-web-workers`                | “Move the image-processing logic to a Web Worker with Comlink to keep the UI responsive.”                                                        |
 | Build an interactive 3D scene              | `fec-canvas-threejs`             | “Add a Three.js product viewer to `src/components/ProductViewer.tsx` with performance and fallback considerations.”                              |

package/README.openclaw.zh-CN.md

@@ -146,22 +146,22 @@ frontend-craft/
 | `fec-implement-from-design`      | 基于 Figma、Sketch、MasterGo、Pixso、墨刀或截图实现 UI         |
 | `fec-validation-fix`             | 执行校验命令、分析失败并安全修复                               |
 | `fec-legacy-web-standard`        | JavaScript + jQuery + HTML/CSS 传统前端规范                    |
-| `fec-legacy-to-modern-migration` | jQuery / MPA 迁移到 React 或 Vue + TypeScript 的策略           |
+| `fec-legacy-to-modern-migration` | 遗留前端现代化、目标栈识别与分阶段迁移策略                     |
 | `fec-testing-strategy`           | 测试层级选择、风险矩阵与覆盖规划                               |
 | `fec-e2e-testing`                | Playwright / Cypress E2E 结构、产物、CI 与不稳定用例治理       |
 | `fec-nextjs-project-standard`    | Next.js App Router、SSR/SSG、路由、元数据、中间件              |
 | `fec-nuxt-project-standard`      | Nuxt 3 SSR/SSG、组合式函数、路由、中间件                       |
 | `fec-monorepo-project-standard`  | pnpm workspace、Turborepo、Nx 结构与任务编排                   |
-| `fec-data-fetching`              | TanStack Query / 服务端状态获取、缓存、失效、乐观更新          |
+| `fec-data-fetching`              | 服务端状态获取、缓存、失效、SSR 与无限加载                     |
 | `fec-state-management`           | 状态归属、store 选型、URL/服务端/表单/本地状态边界             |
-| `fec-form-handling`              | React Hook Form + Zod 表单、动态字段、上传、多步流程           |
+| `fec-form-handling`              | 跨框架表单选型、schema 校验、动态字段、上传、多步流程          |
 | `fec-tailwind-design-system`     | Tailwind token、主题扩展、组件变体、class 治理和暗色模式       |
 | `fec-responsive-layout`          | 移动优先布局、容器查询、数据密集型响应式界面                   |
 | `fec-browser-storage`            | localStorage/sessionStorage/IndexedDB/Cookies 选型与安全持久化 |
 | `fec-route-protection`           | React Router、Next.js、Vue Router、Nuxt 的权限路由保护         |
 | `fec-component-testing`          | RTL / Vue Test Utils 组件测试与回归用例                        |
 | `fec-storybook-component-doc`    | Storybook 组件文档、Addon、MDX、交互与视觉测试集成             |
-| `fec-list-virtualization`        | react-window / TanStack Virtual 大列表虚拟滚动                 |
+| `fec-list-virtualization`        | 按框架选型的大列表虚拟滚动、测量、网格和无限滚动               |
 | `fec-pwa-implementation`         | PWA manifest、Service Worker、离线缓存与安装提示               |
 | `fec-web-workers`                | Web Worker、Transferable、Comlink、Worker 池                   |
 | `fec-canvas-threejs`             | Canvas 2D、Three.js、React Three Fiber、WebGL 性能与可访问性   |
@@ -195,19 +195,19 @@ frontend-craft/
 | 按设计稿 / 截图实现 UI       | `fec-implement-from-design`      | 「请按 Figma 节点 `123:456` 实现该界面：间距与设计 Token 对齐，复用现有 `Button`，并说明假设条件。」                                   |
 | CI 或本地脚本失败            | `fec-validation-fix`             | 「`pnpm lint` 和 `pnpm test` 都挂了，请定位根因并修复，不要放宽类型或跳过检查。」                                                      |
 | 维护 jQuery / MPA 老页面     | `fec-legacy-web-standard`        | 「`public/js/legacy/*.js` 仍在生产使用，请在保持行为的前提下给出可维护性改进与模式建议。」                                             |
-| 规划 jQuery → React/Vue 迁移 | `fec-legacy-to-modern-migration` | 「我们有 `static/app.js` 的 jQuery + 多页应用，请输出迁到 React + TypeScript 的分阶段方案、风险与里程碑。」                            |
+| 规划遗留前端现代化         | `fec-legacy-to-modern-migration` | 「我们有 `static/app.js` 的 jQuery + 多页应用，请评估保留 MPA、局部现代化或迁到目标栈的分阶段方案、风险与里程碑。」                  |
 | 规划前端测试覆盖             | `fec-testing-strategy`           | 「这次 checkout 重构先别急着写测试，请把风险映射到静态检查、单元/组件、E2E、视觉、无障碍和安全覆盖。」                                 |
 | 补充或稳定 E2E               | `fec-e2e-testing`                | 「请用 Playwright 给登录流程加冒烟用例：目录清晰、使用 Page Object，并说明如何在 CI 里跑。」                                           |
 | Next.js App Router 功能      | `fec-nextjs-project-standard`    | 「请评审 `app/(dashboard)/reports/page.tsx` 及相关 server actions 是否符合 Next.js App Router 最佳实践（数据获取、错误、元数据等）。」 |
 | Nuxt 3 页面或布局            | `fec-nuxt-project-standard`      | 「请评审 `pages/admin/*.vue` 与 `composables/useApi.ts` 是否符合 Nuxt 3 的 SSR、数据与组合式用法惯例。」                               |
 | Monorepo 边界与任务编排      | `fec-monorepo-project-standard`  | 「`apps/web` 依赖 `packages/ui`，请检查包边界、workspace 配置和 Turborepo 任务图是否有问题。」                                         |
-| 服务端数据获取               | `fec-data-fetching`              | 「请评审 `src/queries/useReports.ts` 的 TanStack Query 模式：缓存 key、失效策略和乐观更新。」                                          |
+| 服务端数据获取               | `fec-data-fetching`              | 「请评审 `src/data/reports.ts` 的服务端状态获取：缓存 key、失效策略、SSR 水合，以及是否需要查询库。」                                  |
 | 状态归属与 store 选型        | `fec-state-management`           | 「请审计 dashboard 的状态：哪些属于 URL 参数、TanStack Query、本地 state 或全局 store，并给出安全迁移方案。」                          |
-| 复杂表单与校验               | `fec-form-handling`              | 「用 React Hook Form + Zod 构建多步注册表单，包含文件上传和动态条件字段。」                                                            |
+| 复杂表单与校验               | `fec-form-handling`              | 「构建多步注册表单：按项目框架选择表单库和 schema 校验方案，包含文件上传和动态条件字段。」                                             |
 | 为应用添加路由守卫           | `fec-route-protection`           | 「为 React Router 的 `/admin` 路由做权限保护：未登录用户重定向，基于角色控制访问。」                                                   |
 | 编写组件单元测试             | `fec-component-testing`          | 「为 `src/components/UserCard.tsx` 编写 RTL 测试：渲染、user-event 交互和快照回归用例。」                                              |
 | 组件库文档化                 | `fec-storybook-component-doc`    | 「为 `packages/ui/` 搭建 Storybook：MDX 文档、无障碍 addon 和交互测试。」                                                              |
-| 渲染上万条列表数据           | `fec-list-virtualization`        | 「`ProductList` 渲染上万行太卡，请用 react-window 或 TanStack Virtual 做虚拟滚动并测量滚动性能。」                                     |
+| 渲染上万条列表数据           | `fec-list-virtualization`        | 「`ProductList` 渲染上万行太卡，请按现有框架、动态高度、浏览器查找和 SEO 约束选择虚拟滚动方案并测量性能。」                            |
 | 添加离线支持                 | `fec-pwa-implementation`         | 「把这个 React 应用做成 PWA：manifest、Service Worker、离线缓存策略和安装提示。」                                                      |
 | 重计算移出主线程             | `fec-web-workers`                | 「把图片处理逻辑移到 Web Worker，用 Comlink 通信，保持 UI 响应。」                                                                     |
 | 构建交互式 3D 场景           | `fec-canvas-threejs`             | 「在 `src/components/ProductViewer.tsx` 添加 Three.js 产品展示，兼顾性能和降级方案。」                                                 |