@bovinphang/frontend-craft 2.7.0 → 2.9.0

package/docs/runtimes/claude.zh-CN.md

@@ -1,175 +1,189 @@
-# frontend-craft：Claude（Claude Code）
-
-大多数 Claude Code 用户推荐走 **Claude Code Marketplace**，让 Claude Code 原生插件系统作为唯一加载来源。
-
-仅当你需要跨运行时安装、离线/脚本化复制文件，或处在非 Marketplace 环境时，再使用 CLI：
-
-```bash
-npx @bovinphang/frontend-craft@latest install --local claude
-# 或
-npx @bovinphang/frontend-craft@latest install --global claude
-```
-
-> **非交互场景：** 请加上 `--local` 或 `--global`，避免询问安装位置。交互与脚本行为说明见根目录 README **通用安装**。
-
-同一个 Claude 作用域请只选择一个激活来源：Marketplace/原生插件、CLI 安装或 `--plugin-dir`。它们技术上可以共存，但不推荐在同一个 Claude 会话里同时启用多份完整插件，否则 commands、skills、agents 与 hooks 可能重复。
-
-CLI 会对 Marketplace 安装执行单一来源保护：如果已经由 Claude Code Marketplace 管理 `frontend-craft`，`frontend-craft install/update claude` 会停止，并提示改用 Marketplace 更新。`--force` 不会覆盖 Marketplace 安装。
-
----
-
-## Claude Code Marketplace
-
-仍可将 `frontend-craft` 作为 Claude Code 的 Marketplace 插件安装，由 Claude Code 原生加载插件。
-
-Marketplace 条目会从已发布的 npm 包解析插件；npm 包中包含 Claude hooks 使用的已编译 `dist/hooks/*.js` 运行时文件。如果 Marketplace 安装后提示缺少 `dist/hooks/fec-*.js`，请通过 Marketplace 更新或重新安装插件，让 Claude 刷新插件缓存，不建议手动复制文件到缓存目录。
-
----
-
-## Marketplace 安装后的快速开始
-
-### 第一步：安装插件
-
-```bash
-# 添加市场
-/plugin marketplace add bovinphang/frontend-craft
-
-# 安装插件
-/plugin install frontend-craft@frontend-craft
-
-# 激活
-/reload-plugins
-```
-
-### 第二步：初始化项目配置（推荐）
-
-```bash
-# 将项目模板复制到当前项目的 .claude/ 目录
-/fec-init
-```
-
-初始化后请根据项目实际情况修改：
-
-1. `.claude/CLAUDE.md` — 修改项目基础信息、包管理器、常用命令（仓库内模板位于 `templates/claude/`，`/fec-init` 会复制到 `.claude/`）
-2. `.claude/rules/` — 删除不适用的规则文件（如纯 React 项目删除 `fec-vue.md`，不需要 i18n 的项目删除 `fec-i18n.md`）
-3. `.claude/settings.json` — 调整权限白名单
-
-> **为什么需要这一步？** 插件提供可复用的 Skills、Agents 和 Hooks；CLAUDE.md 与 rules 属于项目级配置，须位于项目根目录的 `.claude/` 下才能被 Claude Code 识别。`/fec-init` 用于快速完成该步骤。
->
-> `/fec-init` 是项目配置初始化，不是第二次安装插件本体。插件本体请交给 Marketplace、CLI 或 `--plugin-dir` 其中之一管理。
-
-### 第三步：开始使用
-
-```bash
-# 代码评审（输出到 reports/code-review-*.md）
-/fec-review
-
-# 按规范创建页面/功能/组件
-/fec-scaffold page UserDetail
-/fec-scaffold component DataTable
-
-# 查看可用命令
-/plugin list frontend-craft@frontend-craft
-```
-
-具体 agents、skills、commands 清单见根目录 README **功能概览**。
-
----
-
-## 其他安装方式（仅 Claude Code）
-
-> **要求：** Claude Code v1.0.33+，Node.js 22+，npm/pnpm/yarn。
-
-### 选项 1：作为插件安装（推荐）
-
-与上文 **「Marketplace 安装后的快速开始」** 中 **第一步：安装插件** 相同（添加市场、安装插件、`/reload-plugins`）。亦可不在对话里执行命令，直接写入 `~/.claude/settings.json` 或项目 `.claude/settings.json`：
-
-```json
-{
-  "extraKnownMarketplaces": {
-    "frontend-craft": {
-      "source": {
-        "source": "github",
-        "repo": "bovinphang/frontend-craft"
-      }
-    }
-  }
-}
-```
-
-### 选项 2：团队项目级自动安装
-
-在项目根目录的 `.claude/settings.json` 中添加上述 `extraKnownMarketplaces` 配置，团队成员 trust 项目目录后会收到安装提示。
-
-### 选项 3：本地开发 / 测试
-
-克隆仓库后使用 `--plugin-dir` 加载（无需安装，适合开发调试）：
-
-```bash
-git clone https://github.com/bovinphang/frontend-craft.git
-cd frontend-craft
-npm install
-npm run build
-cd ..
-claude --plugin-dir ./frontend-craft
-```
-
-使用 `--plugin-dir` 做开发调试时，修改 hooks 或 CLI 源码后需要重新执行 `npm run build`，因为 Claude 会运行 `dist/` 下的已编译文件。请避免在同一会话里同时启用 Marketplace 版本，这样才能确定当前运行的是哪一份代码。
-
-### 选项 4：Git Submodule（项目内共享）
-
-```bash
-# 在项目根目录添加 submodule
-git submodule add https://github.com/bovinphang/frontend-craft.git .claude/plugins/frontend-craft
-
-git add .gitmodules .claude/plugins/frontend-craft
-git commit -m "feat: add frontend-craft as shared Claude Code plugin"
-```
-
-团队成员克隆后执行：
-
-```bash
-git submodule update --init --recursive
-```
-
-再使用 `--plugin-dir` 加载：
-
-```bash
-claude --plugin-dir .claude/plugins/frontend-craft
-```
-
----
-
-## 更新（Marketplace 与 submodule）
-
-通过 Marketplace 安装的插件，在 Claude Code 中执行：
-
-```text
-/plugin marketplace update frontend-craft
-```
-
-或开启自动更新，每次启动 Claude Code 时拉取最新版本：
-
-1. 在 Claude Code 中执行 `/plugin` 打开插件管理器
-2. 切换到 **Marketplaces** 标签页
-3. 选中 `frontend-craft`
-4. 选择 **Enable auto-update**
-
-> 第三方 Marketplace 默认不开启自动更新。启用后，Claude Code 每次启动时会刷新 Marketplace 数据并更新已安装插件。
-
-若使用 Git submodule 安装：
-
-```bash
-git submodule update --remote .claude/plugins/frontend-craft
-```
-
-**CLI 安装：** 对同一作用域执行 `npx @bovinphang/frontend-craft@latest update claude --local` 或 `... --global`，版本说明见 [CHANGELOG.zh-CN.md](../../CHANGELOG.zh-CN.md) 或 [CHANGELOG.md](../../CHANGELOG.md)。如果已经检测到 Claude Code Marketplace 安装，CLI 会拒绝 Claude install/update，并提示通过 Marketplace 更新。如果另一个 CLI 作用域已安装，交互式终端会询问是保持该来源并更新，还是卸载后切换；非交互终端会打印可执行命令。
-
-```bash
-npx @bovinphang/frontend-craft@latest update claude --global
-npx @bovinphang/frontend-craft@latest update claude --local
-```
-
----
-
-**English:** [claude.md](claude.md)
+# frontend-craft：Claude（Claude Code）
+
+大多数 Claude Code 用户推荐走 **Claude Code Marketplace**，让 Claude Code 原生插件系统作为唯一加载来源。
+
+仅当你需要跨运行时安装、离线/脚本化复制文件，或处在非 Marketplace 环境时，再使用 CLI：
+
+```bash
+npx @bovinphang/frontend-craft@latest install --local claude
+# 或
+npx @bovinphang/frontend-craft@latest install --global claude
+```
+
+> **非交互场景：** 请加上 `--local` 或 `--global`，避免询问安装位置。交互与脚本行为说明见根目录 README **通用安装**。
+
+同一个 Claude 作用域请只选择一个激活来源：Marketplace/原生插件、CLI 安装或 `--plugin-dir`。它们技术上可以共存，但不推荐在同一个 Claude 会话里同时启用多份完整插件，否则 commands、skills、agents 与 hooks 可能重复。
+
+CLI 会对 Marketplace 安装执行单一来源保护：如果已经由 Claude Code Marketplace 管理 `frontend-craft`，`frontend-craft install/update claude` 会停止，并提示改用 Marketplace 更新。`--force` 不会覆盖 Marketplace 安装。
+
+---
+
+## Claude Code Marketplace
+
+仍可将 `frontend-craft` 作为 Claude Code 的 Marketplace 插件安装，由 Claude Code 原生加载插件。
+
+Marketplace 条目会从已发布的 npm 包解析插件；npm 包中包含 Claude hooks 使用的已编译 `dist/hooks/*.js` 运行时文件。如果 Marketplace 安装后提示缺少 `dist/hooks/fec-*.js`，请通过 Marketplace 更新或重新安装插件，让 Claude 刷新插件缓存，不建议手动复制文件到缓存目录。
+
+---
+
+## Marketplace 安装后的快速开始
+
+### 第一步：安装插件
+
+```bash
+# 添加市场
+/plugin marketplace add bovinphang/frontend-craft
+
+# 安装插件
+/plugin install frontend-craft@frontend-craft
+
+# 激活
+/reload-plugins
+```
+
+### 第二步：初始化项目配置（推荐）
+
+```bash
+# 将项目模板复制到当前项目的 .claude/ 目录
+/fec-init
+```
+
+初始化后请根据项目实际情况修改：
+
+1. `.claude/CLAUDE.md` — 修改项目基础信息、包管理器、常用命令（仓库内模板位于 `templates/claude/`，`/fec-init` 会复制到 `.claude/`）
+2. `.claude/rules/` — 删除不适用的规则文件（如纯 React 项目删除 `fec-vue.md`，不需要 i18n 的项目删除 `fec-i18n.md`）
+3. `.claude/settings.json` — 调整权限白名单
+
+> **为什么需要这一步？** 插件提供可复用的 Skills、Agents 和 Hooks；CLAUDE.md 与 rules 属于项目级配置，须位于项目根目录的 `.claude/` 下才能被 Claude Code 识别。`/fec-init` 用于快速完成该步骤。
+>
+> `/fec-init` 是项目配置初始化，不是第二次安装插件本体。插件本体请交给 Marketplace、CLI 或 `--plugin-dir` 其中之一管理。
+
+### 第三步：开始使用
+
+```bash
+# 默认全项目审核（输出到 reports/code-review-*.md）
+/fec-review
+
+# 明确增量审核
+/fec-review 审核最近改动
+
+# 指定文件、目录或全项目（自然语言范围，不是 CLI 参数）
+/fec-review 审核 src/components/Button.tsx
+/fec-review 审核 src/features/
+/fec-review 审核整个项目
+
+# 按规范创建页面/功能/组件
+/fec-scaffold page UserDetail
+/fec-scaffold component DataTable
+
+# 查看可用命令
+/plugin list frontend-craft@frontend-craft
+```
+
+具体 agents、skills、commands 清单见根目录 README **功能概览**。
+
+---
+
+## 其他安装方式（仅 Claude Code）
+
+> **要求：** Claude Code v1.0.33+，Node.js 22+，npm/pnpm/yarn。
+
+### 选项 1：作为插件安装（推荐）
+
+与上文 **「Marketplace 安装后的快速开始」** 中 **第一步：安装插件** 相同（添加市场、安装插件、`/reload-plugins`）。亦可不在对话里执行命令，直接写入 `~/.claude/settings.json` 或项目 `.claude/settings.json`：
+
+```json
+{
+  "extraKnownMarketplaces": {
+    "frontend-craft": {
+      "source": {
+        "source": "github",
+        "repo": "bovinphang/frontend-craft"
+      }
+    }
+  }
+}
+```
+
+### 选项 2：团队项目级自动安装
+
+在项目根目录的 `.claude/settings.json` 中添加上述 `extraKnownMarketplaces` 配置，团队成员 trust 项目目录后会收到安装提示。
+
+### 选项 3：本地开发 / 测试
+
+克隆仓库后使用 `--plugin-dir` 加载（无需安装，适合开发调试）：
+
+```bash
+git clone https://github.com/bovinphang/frontend-craft.git
+cd frontend-craft
+npm install
+npm run build
+cd ..
+claude --plugin-dir ./frontend-craft
+```
+
+使用 `--plugin-dir` 做开发调试时，修改 hooks 或 CLI 源码后需要重新执行 `npm run build`，因为 Claude 会运行 `dist/` 下的已编译文件。请避免在同一会话里同时启用 Marketplace 版本，这样才能确定当前运行的是哪一份代码。
+
+### 选项 4：Git Submodule（项目内共享）
+
+```bash
+# 在项目根目录添加 submodule
+git submodule add https://github.com/bovinphang/frontend-craft.git .claude/plugins/frontend-craft
+
+git add .gitmodules .claude/plugins/frontend-craft
+git commit -m "feat: add frontend-craft as shared Claude Code plugin"
+```
+
+团队成员克隆后执行：
+
+```bash
+git submodule update --init --recursive
+```
+
+再使用 `--plugin-dir` 加载：
+
+```bash
+claude --plugin-dir .claude/plugins/frontend-craft
+```
+
+---
+
+## 更新（Marketplace 与 submodule）
+
+通过 Marketplace 安装的插件，在 Claude Code 中执行：
+
+```text
+/plugin marketplace update frontend-craft
+```
+
+或开启自动更新，每次启动 Claude Code 时拉取最新版本：
+
+1. 在 Claude Code 中执行 `/plugin` 打开插件管理器
+2. 切换到 **Marketplaces** 标签页
+3. 选中 `frontend-craft`
+4. 选择 **Enable auto-update**
+
+> 第三方 Marketplace 默认不开启自动更新。启用后，Claude Code 每次启动时会刷新 Marketplace 数据并更新已安装插件。
+
+若使用 Git submodule 安装：
+
+```bash
+git submodule update --remote .claude/plugins/frontend-craft
+```
+
+**CLI 安装：** 对同一作用域执行 `npx @bovinphang/frontend-craft@latest update claude --local` 或 `... --global`，版本说明见 [CHANGELOG.zh-CN.md](../../CHANGELOG.zh-CN.md) 或 [CHANGELOG.md](../../CHANGELOG.md)。如果已经检测到 Claude Code Marketplace 安装，CLI 会拒绝 Claude install/update，并提示通过 Marketplace 更新。如果另一个 CLI 作用域已安装，交互式终端会询问是保持该来源并更新，还是卸载后切换；非交互终端会打印可执行命令。
+
+```bash
+npx @bovinphang/frontend-craft@latest update claude --global
+npx @bovinphang/frontend-craft@latest update claude --local
+```
+
+---
+
+**English:** [claude.md](claude.md)
+
+## CLI 兼容性更新
+
+CLI 安装会将 hooks 合并到 `settings.json`，保留其他用户配置；无效 JSON 会阻止安装。原生 Marketplace 插件继续使用 `hooks/hooks.json`。参见[兼容性与升级说明](compatibility.md)。
+
+审核默认覆盖全项目；指定文件或目录时审核全部现有代码，仅明确要求改动 / PR / 提交时增量审核。技术图使用结构化源文件，PNG 导出需本地浏览器并报告 QA 覆盖情况。详见[审核范围与技术图交付](../zh-CN/review-and-diagram-workflows.md)。

package/docs/runtimes/cline.md

@@ -1,10 +1,18 @@
-# frontend-craft: cline
-
-See root README **Universal Install** and run:
-
-```bash
-npx @bovinphang/frontend-craft install cline
-```
-
-> **Non-interactive:** append `--local` or `--global` to skip install-location prompts. See the repository README **Universal Install** for interactive vs. scripted behavior.
-
+# frontend-craft: Cline
+
+```bash
+fec setup cline
+fec setup cline --global
+fec doctor cline --local
+fec doctor cline --global
+```
+
+Without a global CLI installation, use `npx @bovinphang/frontend-craft install cline --local` or `--global`.
+
+Project rules: `.clinerules/frontend-craft.md`, preserving other files in the directory. An existing legacy `.clinerules` file is backed up as `.clinerules.frontend-craft-backup` and copied into `.clinerules/legacy.md` before installing the new bundle. An existing backup stops migration to avoid overwriting it. Global rules: `~/Documents/Cline/Rules/frontend-craft.md`. Set `CLINE_CONFIG_DIR` to the parent of your actual `Rules` directory when Documents is redirected or Cline uses a different location. Manifest-tracked old default `~/.cline` installs are copied to the new location on install/update; originals and user edits are preserved.
+
+The capability matrix describes what frontend-craft installs, not every feature offered by the host. `doctor` checks installation artifacts; it does not launch the host or certify a release version.
+
+[Official reference](https://docs.cline.bot/customization/cline-rules) 路 [Compatibility and upgrade notes](compatibility.md)
+
+Review defaults to the full project; a file/directory request includes unchanged code, while incremental review requires an explicit changes/PR/commit request. Technical diagrams use structured sources; PNG export requires a local browser and disclosed QA coverage. See [review scope and technical diagram delivery](../review-and-diagram-workflows.md).

package/docs/runtimes/codebuddy.md

@@ -1,10 +1,18 @@
-# frontend-craft: codebuddy
-
-See root README **Universal Install** and run:
-
-```bash
-npx @bovinphang/frontend-craft install codebuddy
-```
-
-> **Non-interactive:** append `--local` or `--global` to skip install-location prompts. See the repository README **Universal Install** for interactive vs. scripted behavior.
-
+# frontend-craft: CodeBuddy
+
+```bash
+fec setup codebuddy
+fec setup codebuddy --global
+fec doctor codebuddy --local
+fec doctor codebuddy --global
+```
+
+Without a global CLI installation, use `npx @bovinphang/frontend-craft install codebuddy --local` or `--global`.
+
+Skills use `.codebuddy/skills` or `~/.codebuddy/skills` (`CODEBUDDY_CONFIG_DIR` override). This adapter installs skills only; commands, agents, hooks and MCP supported by the product are separate integration opportunities.
+
+The capability matrix describes what frontend-craft installs, not every feature offered by the host. `doctor` checks installation artifacts; it does not launch the host or certify a release version.
+
+[Official reference](https://www.codebuddy.ai/docs/cli/skills) · [Compatibility and upgrade notes](compatibility.md)
+
+Review defaults to the full project; a file/directory request includes unchanged code, while incremental review requires an explicit changes/PR/commit request. Technical diagrams use structured sources; PNG export requires a local browser and disclosed QA coverage. See [review scope and technical diagram delivery](../review-and-diagram-workflows.md).

package/docs/runtimes/codex.md

@@ -1,10 +1,18 @@
-# frontend-craft: codex
-
-See root README **Universal Install** and run:
-
-```bash
-npx @bovinphang/frontend-craft install codex
-```
-
-> **Non-interactive:** append `--local` or `--global` to skip install-location prompts. See the repository README **Universal Install** for interactive vs. scripted behavior.
-
+# frontend-craft: Codex
+
+```bash
+fec setup codex
+fec setup codex --global
+fec doctor codex --local
+fec doctor codex --global
+```
+
+Without a global CLI installation, use `npx @bovinphang/frontend-craft install codex --local` or `--global`.
+
+Project skills: `.agents/skills`; user skills: `~/.agents/skills`. Agents: `.codex/agents/*.toml` or `$CODEX_HOME/agents`. Existing `config.toml` is preserved. New agents inherit the session model and reasoning effort; edited agent files are preserved by `fec update`. Hooks and active MCP configuration are not installed by this adapter.
+
+The capability matrix describes what frontend-craft installs, not every feature offered by the host. `doctor` checks installation artifacts; it does not launch the host or certify a release version.
+
+[Official reference](https://learn.chatgpt.com/docs/agent-configuration/subagents) · [Compatibility and upgrade notes](compatibility.md)
+
+Review defaults to the full project; a file/directory request includes unchanged code, while incremental review requires an explicit changes/PR/commit request. Technical diagrams use structured sources; PNG export requires a local browser and disclosed QA coverage. See [review scope and technical diagram delivery](../review-and-diagram-workflows.md).

package/docs/runtimes/compatibility.md

@@ -0,0 +1,27 @@
+# Runtime compatibility and upgrades
+
+The adapters install different capability subsets. Run `fec matrix` for the project-level inventory and read the runtime-specific page for global differences. A successful install or doctor result proves the expected artifacts exist, not that every host feature is integrated or a particular release was tested interactively.
+
+## Updating existing installations
+
+Use `fec update <runtime> --local` or `--global` with the new CLI. Updates preserve manifest-tracked files changed by the user. Fresh installs retain existing Codex configuration and context files. Merge any missing rule imports into existing Gemini context files manually.
+
+Unchanged manifest-owned legacy command paths are retired when replacements are installed for OpenCode, Kilo, Copilot, Gemini, OpenClaw and global Windsurf. Unknown or edited old files are preserved. Files that remain in old directories stay tracked for a later uninstall. Claude CLI hooks now live in settings.json; the original native Marketplace packaging stays unchanged.
+
+Antigravity and Cline global defaults changed. Run `fec setup antigravity --global` / `fec setup cline --global` to copy manifest-tracked files to the current destination before updating; user edits and old originals are preserved. `fec update --global` also discovers these legacy installations. For product-specific or redirected directories, use the documented runtime configuration-directory environment variable. It is an installer override; configure the host consistently too.
+
+Shared Claude/Qoder settings are never owned as a whole file. The manifest records installed hook entries, so uninstall removes only exact matching entries and preserves other settings. A user-modified hook entry is preserved; remove it manually if it still refers to a script you uninstall. Malformed settings stop the operation rather than being replaced. Keep the install manifest for safe updates and uninstall.
+
+## Scope differences
+
+- Copilot project installs provide IDE prompt files and path-specific instructions. Global installs provide CLI user instructions, not IDE global prompts.
+- Kilo targets the current CLI discovery contract. Antigravity defaults to its IDE/2.0 global directory; its CLI uses a different override.
+- OpenClaw project installs require the agent workspace as the working directory. Native plugin packaging is separate from the universal installer.
+- Cursor, Augment and CodeBuddy keep their existing supported capability subsets. New host features are not automatically installed.
+- Codex agents inherit the selected model and reasoning effort. Older manually edited TOML files remain untouched by update; remove their model overrides yourself if you want inheritance.
+
+## Verification
+
+Regression tests exercise artifact discovery paths, metadata, existing settings, repeated installation and uninstall behavior. `npm test` runs the package's build, type checks and test suite. `npm run typecheck:openclaw` and `npm run pack:openclaw` verify the separate native package. Full host-session tests require the corresponding installed product and account.
+
+Review scope and diagram delivery rules are shared across adapters; installed artifacts do not guarantee that local Mermaid or a Chromium browser is available. See [review scope and technical diagram delivery](../review-and-diagram-workflows.md).

package/docs/runtimes/copilot.md

@@ -1,10 +1,18 @@
-# frontend-craft: copilot
-
-See root README **Universal Install** and run:
-
-```bash
-npx @bovinphang/frontend-craft install copilot
-```
-
-> **Non-interactive:** append `--local` or `--global` to skip install-location prompts. See the repository README **Universal Install** for interactive vs. scripted behavior.
-
+# frontend-craft: GitHub Copilot
+
+```bash
+fec setup copilot
+fec setup copilot --global
+fec doctor copilot --local
+fec doctor copilot --global
+```
+
+Without a global CLI installation, use `npx @bovinphang/frontend-craft install copilot --local` or `--global`.
+
+Local installation targets repository customization: `.github/instructions/frontend-craft.instructions.md` with `applyTo: "**"` and `.github/prompts/fec-*.prompt.md`. Prompt files are supported by compatible IDE clients. Global installation targets Copilot CLI user instructions in `~/.copilot/copilot-instructions.md` (`COPILOT_CONFIG_DIR` override), preserving an existing file. Global IDE prompt installation is not provided; use `--local` for prompts.
+
+The capability matrix describes what frontend-craft installs, not every feature offered by the host. `doctor` checks installation artifacts; it does not launch the host or certify a release version.
+
+[Official reference](https://docs.github.com/en/copilot/reference/customization-cheat-sheet) · [Compatibility and upgrade notes](compatibility.md)
+
+Review defaults to the full project; a file/directory request includes unchanged code, while incremental review requires an explicit changes/PR/commit request. Technical diagrams use structured sources; PNG export requires a local browser and disclosed QA coverage. See [review scope and technical diagram delivery](../review-and-diagram-workflows.md).

package/docs/runtimes/cursor.md

@@ -1,10 +1,18 @@
-# frontend-craft: cursor
-
-See root README **Universal Install** and run:
-
-```bash
-npx @bovinphang/frontend-craft install cursor
-```
-
-> **Non-interactive:** append `--local` or `--global` to skip install-location prompts. See the repository README **Universal Install** for interactive vs. scripted behavior.
-
+# frontend-craft: Cursor
+
+```bash
+fec setup cursor
+fec setup cursor --global
+fec doctor cursor --local
+fec doctor cursor --global
+```
+
+Without a global CLI installation, use `npx @bovinphang/frontend-craft install cursor --local` or `--global`.
+
+Project skills: `.cursor/skills`; user skills: `~/.cursor/skills` (or `CURSOR_CONFIG_DIR/skills`). Project rules use `.cursor/rules/*.mdc`. This adapter installs skills and project rules; it does not install native agents, hooks, commands or MCP configuration.
+
+The capability matrix describes what frontend-craft installs, not every feature offered by the host. `doctor` checks installation artifacts; it does not launch the host or certify a release version.
+
+[Official reference](https://cursor.com/docs/skills) · [Compatibility and upgrade notes](compatibility.md)
+
+Review defaults to the full project; a file/directory request includes unchanged code, while incremental review requires an explicit changes/PR/commit request. Technical diagrams use structured sources; PNG export requires a local browser and disclosed QA coverage. See [review scope and technical diagram delivery](../review-and-diagram-workflows.md).

package/docs/runtimes/gemini.md

@@ -1,10 +1,18 @@
-# frontend-craft: gemini
-
-See root README **Universal Install** and run:
-
-```bash
-npx @bovinphang/frontend-craft install gemini
-```
-
-> **Non-interactive:** append `--local` or `--global` to skip install-location prompts. See the repository README **Universal Install** for interactive vs. scripted behavior.
-
+# frontend-craft: Gemini CLI
+
+```bash
+fec setup gemini
+fec setup gemini --global
+fec doctor gemini --local
+fec doctor gemini --global
+```
+
+Without a global CLI installation, use `npx @bovinphang/frontend-craft install gemini --local` or `--global`.
+
+Skills use `.gemini/skills` or `~/.gemini/skills` (`GEMINI_CONFIG_DIR` override). Rules are copied into `rules/` under that base. If absent, project `GEMINI.md` or user `~/.gemini/GEMINI.md` is created with resolvable rule imports. Existing context files are preserved; add the rule imports manually if you want them in an existing context. This installs native skills, not an incomplete extension.
+
+The capability matrix describes what frontend-craft installs, not every feature offered by the host. `doctor` checks installation artifacts; it does not launch the host or certify a release version.
+
+[Official reference](https://geminicli.com/docs/cli/skills/) · [Compatibility and upgrade notes](compatibility.md)
+
+Review defaults to the full project; a file/directory request includes unchanged code, while incremental review requires an explicit changes/PR/commit request. Technical diagrams use structured sources; PNG export requires a local browser and disclosed QA coverage. See [review scope and technical diagram delivery](../review-and-diagram-workflows.md).

package/docs/runtimes/kilo.md

@@ -1,10 +1,18 @@
-# frontend-craft: kilo
-
-See root README **Universal Install** and run:
-
-```bash
-npx @bovinphang/frontend-craft install kilo
-```
-
-> **Non-interactive:** append `--local` or `--global` to skip install-location prompts. See the repository README **Universal Install** for interactive vs. scripted behavior.
-
+# frontend-craft: Kilo CLI
+
+```bash
+fec setup kilo
+fec setup kilo --global
+fec doctor kilo --local
+fec doctor kilo --global
+```
+
+Without a global CLI installation, use `npx @bovinphang/frontend-craft install kilo --local` or `--global`.
+
+This adapter targets the current Kilo CLI: project `.kilo`, user `$XDG_CONFIG_HOME/kilo` or `~/.config/kilo`, with `KILO_CONFIG_DIR` override. Skills use `skills/`, commands use canonical `commands/`. Official CLI source also discovers legacy singular directories and home `.kilo` / `.kilocode` roots. IDE-only installations can have different global discovery behavior; this is not a blanket IDE certification.
+
+The capability matrix describes what frontend-craft installs, not every feature offered by the host. `doctor` checks installation artifacts; it does not launch the host or certify a release version.
+
+[Official reference](https://github.com/Kilo-Org/kilocode/blob/main/packages/opencode/src/config/paths.ts) · [Compatibility and upgrade notes](compatibility.md)
+
+Review defaults to the full project; a file/directory request includes unchanged code, while incremental review requires an explicit changes/PR/commit request. Technical diagrams use structured sources; PNG export requires a local browser and disclosed QA coverage. See [review scope and technical diagram delivery](../review-and-diagram-workflows.md).

package/docs/runtimes/openclaw.md

@@ -1,10 +1,18 @@
-# frontend-craft: openclaw
-
-See root README **Universal Install** and run:
-
-```bash
-npx @bovinphang/frontend-craft install openclaw
-```
-
-> **Non-interactive:** append `--local` or `--global` to skip install-location prompts. See the repository README **Universal Install** for interactive vs. scripted behavior.
-
+# frontend-craft: OpenClaw
+
+```bash
+fec setup openclaw
+fec setup openclaw --global
+fec doctor openclaw --local
+fec doctor openclaw --global
+```
+
+Without a global CLI installation, use `npx @bovinphang/frontend-craft install openclaw --local` or `--global`.
+
+Universal CLI: run from the agent workspace; project skills go into `<workspace>/skills`, with the install manifest in `.openclaw`. User skills go into `$OPENCLAW_STATE_DIR/skills` or `~/.openclaw/skills`; `OPENCLAW_CONFIG_DIR` remains a fallback alias. Commands are converted to named skill directories with `SKILL.md`. Global setup does not write project context files. The separately packed native plugin includes hook handlers and an optional workspace initialization tool; `npm run pack:openclaw` generates its command skills.
+
+The capability matrix describes what frontend-craft installs, not every feature offered by the host. `doctor` checks installation artifacts; it does not launch the host or certify a release version.
+
+[Official reference](https://docs.openclaw.ai/skills) · [Compatibility and upgrade notes](compatibility.md)
+
+Review defaults to the full project; a file/directory request includes unchanged code, while incremental review requires an explicit changes/PR/commit request. Technical diagrams use structured sources; PNG export requires a local browser and disclosed QA coverage. See [review scope and technical diagram delivery](../review-and-diagram-workflows.md).