@bovinphang/frontend-craft 2.8.0 → 2.9.0

package/docs/runtimes/antigravity.md

@@ -1,10 +1,18 @@
-# frontend-craft: antigravity
-
-See root README **Universal Install** and run:
-
-```bash
-npx @bovinphang/frontend-craft install antigravity
-```
-
-> **Non-interactive:** append `--local` or `--global` to skip install-location prompts. See the repository README **Universal Install** for interactive vs. scripted behavior.
-
+# frontend-craft: Antigravity
+
+```bash
+fec setup antigravity
+fec setup antigravity --global
+fec doctor antigravity --local
+fec doctor antigravity --global
+```
+
+Without a global CLI installation, use `npx @bovinphang/frontend-craft install antigravity --local` or `--global`.
+
+Project skills retain backward-compatible `.agent/skills`; the current IDE/2.0 user base is `~/.gemini/config`, so skills go in `~/.gemini/config/skills`. For Antigravity CLI set `ANTIGRAVITY_CONFIG_DIR` to `~/.gemini/antigravity-cli` before global installation. The override selects one product scope; this adapter does not install plugins or hooks. After upgrading an old default global install, run `fec setup antigravity --global`; the old `~/.gemini/antigravity` files 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://antigravity.google/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/augment.md

@@ -1,10 +1,18 @@
-# frontend-craft: augment
-
-See root README **Universal Install** and run:
-
-```bash
-npx @bovinphang/frontend-craft install augment
-```
-
-> **Non-interactive:** append `--local` or `--global` to skip install-location prompts. See the repository README **Universal Install** for interactive vs. scripted behavior.
-
+# frontend-craft: Augment
+
+```bash
+fec setup augment
+fec setup augment --global
+fec doctor augment --local
+fec doctor augment --global
+```
+
+Without a global CLI installation, use `npx @bovinphang/frontend-craft install augment --local` or `--global`.
+
+Skills use `.augment/skills` or `~/.augment/skills` (`AUGMENT_CONFIG_DIR` override). The adapter currently installs skills only. Native agents, rules, hooks and MCP support in Augment do not imply that this adapter installs those capabilities.
+
+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.augmentcode.com/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/claude.md

@@ -1,177 +1,191 @@
-# frontend-craft: Claude (Claude Code)
-
-Recommended path for most Claude Code users: install through **Claude Code Marketplace** so Claude Code is the single plugin loader.
-
-Use the CLI only when you need cross-runtime installation, offline/scripted file copies, or a non-Marketplace environment:
-
-```bash
-npx @bovinphang/frontend-craft@latest install --local claude
-# or
-npx @bovinphang/frontend-craft@latest install --global claude
-```
-
-> **Non-interactive:** append `--local` or `--global` to skip install-location prompts. See the repository README **Universal Install** for interactive vs. scripted behavior.
-
-Choose one active source of truth for the same Claude scope: Marketplace/native plugin, CLI install, or `--plugin-dir`. They can technically coexist, but running multiple complete copies in the same Claude session can duplicate commands, skills, agents, and hooks.
-
-The CLI enforces this for Marketplace installs: if Claude Code Marketplace already manages `frontend-craft`, `frontend-craft install/update claude` stops and tells you to update through Marketplace instead. `--force` does not override a Marketplace install.
-
----
-
-## Claude Code Marketplace
-
-You can install `frontend-craft` as a Claude Code marketplace plugin. This loads the plugin natively inside Claude Code.
-
-The Marketplace entry resolves the plugin from the published npm package, which includes the compiled `dist/hooks/*.js` runtime files used by Claude hooks. If a Marketplace install reports a missing `dist/hooks/fec-*.js` file, update or reinstall the Marketplace plugin so Claude refreshes its plugin cache instead of copying files into the cache manually.
-
----
-
-## Quick start after Marketplace install
-
-Get started in a few minutes:
-
-### Step 1: Install the plugin
-
-```bash
-# Add marketplace
-/plugin marketplace add bovinphang/frontend-craft
-
-# Install plugin
-/plugin install frontend-craft@frontend-craft
-
-# Activate
-/reload-plugins
-```
-
-### Step 2: Initialize project config (recommended)
-
-```bash
-# Copy project templates to .claude/ directory
-/fec-init
-```
-
-After initialization, customize for your project:
-
-1. `.claude/CLAUDE.md` — Update project info, package manager, common commands (source templates: `templates/claude/`; `/fec-init` copies into `.claude/`)
-2. `.claude/rules/` — Remove inapplicable rules (e.g. delete `fec-vue.md` for React-only projects, delete `fec-i18n.md` if i18n is not needed)
-3. `.claude/settings.json` — Adjust permission whitelist
-
-> **Why this step?** The plugin provides reusable Skills, Agents, and Hooks. CLAUDE.md and rules are project-level config and must live under the project root `.claude/` for Claude Code to recognize them. The `/fec-init` command helps you set this up quickly.
->
-> `/fec-init` initializes project config; it is not a second plugin install. Keep the plugin body managed by Marketplace, CLI, or `--plugin-dir`, not more than one at once.
-
-### Step 3: Start using
-
-```bash
-# Code review (outputs to reports/code-review-*.md)
-/fec-review
-
-# Create page/feature/component by convention
-/fec-scaffold page UserDetail
-/fec-scaffold component DataTable
-
-# List available commands
-/plugin list frontend-craft@frontend-craft
-```
-
-You now have access to the bundled agents, skills, and commands (see the root README **Feature overview** for the current list).
-
----
-
-## Alternate install paths (Claude Code only)
-
-> **Requirements:** Claude Code v1.0.33+, Node.js 22+, npm/pnpm/yarn.
-
-### Option 1: Install as plugin (recommended)
-
-Same as **Step 1: Install the plugin** under **Quick start after Marketplace install** above (add marketplace, install plugin, `/reload-plugins`). You can also skip typing those commands in chat and add the marketplace via `~/.claude/settings.json` or project `.claude/settings.json`:
-
-```json
-{
-  "extraKnownMarketplaces": {
-    "frontend-craft": {
-      "source": {
-        "source": "github",
-        "repo": "bovinphang/frontend-craft"
-      }
-    }
-  }
-}
-```
-
-### Option 2: Team project-level auto-install
-
-Add the `extraKnownMarketplaces` config above to `.claude/settings.json` in the project root. Team members will be prompted to install when they trust the project directory.
-
-### Option 3: Local development / testing
-
-Clone the repo and load via `--plugin-dir` (no install, suitable for development and debugging):
-
-```bash
-git clone https://github.com/bovinphang/frontend-craft.git
-cd frontend-craft
-npm install
-npm run build
-cd ..
-claude --plugin-dir ./frontend-craft
-```
-
-When using `--plugin-dir` for development, run `npm run build` after changing hook or CLI sources because Claude executes the compiled files under `dist/`. Disable or avoid a Marketplace install of the same plugin in that session so you know which copy is running.
-
-### Option 4: Git Submodule (project-level sharing)
-
-```bash
-# Add as submodule in project root
-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"
-```
-
-After cloning, team members run:
-
-```bash
-git submodule update --init --recursive
-```
-
-Then load with `--plugin-dir`:
-
-```bash
-claude --plugin-dir .claude/plugins/frontend-craft
-```
-
----
-
-## Updating (Marketplace and submodule)
-
-For Marketplace installs, run in Claude Code:
-
-```text
-/plugin marketplace update frontend-craft
-```
-
-Or enable auto-update so Claude Code pulls the latest on each start:
-
-1. Run `/plugin` in Claude Code to open the plugin manager
-2. Switch to the **Marketplaces** tab
-3. Select `frontend-craft`
-4. Choose **Enable auto-update**
-
-> Third-party Marketplaces do not enable auto-update by default. After enabling, Claude Code will refresh Marketplace data and update installed plugins on each start.
-
-For Git submodule installs:
-
-```bash
-git submodule update --remote .claude/plugins/frontend-craft
-```
-
-**CLI installs:** re-run `npx @bovinphang/frontend-craft@latest update claude --local` or `... --global` for the same scope, and read [CHANGELOG.md](../../CHANGELOG.md) for release notes. If Claude Code Marketplace is already installed, the CLI refuses Claude install/update and prints the Marketplace update path. If the opposite CLI scope is already installed, interactive terminals ask whether to keep that source updated or uninstall it before switching; non-interactive terminals print the exact commands to run.
-
-```bash
-npx @bovinphang/frontend-craft@latest update claude --global
-npx @bovinphang/frontend-craft@latest update claude --local
-```
-
----
-
-**Other languages:** [简体中文](claude.zh-CN.md)
+# frontend-craft: Claude (Claude Code)
+
+Recommended path for most Claude Code users: install through **Claude Code Marketplace** so Claude Code is the single plugin loader.
+
+Use the CLI only when you need cross-runtime installation, offline/scripted file copies, or a non-Marketplace environment:
+
+```bash
+npx @bovinphang/frontend-craft@latest install --local claude
+# or
+npx @bovinphang/frontend-craft@latest install --global claude
+```
+
+> **Non-interactive:** append `--local` or `--global` to skip install-location prompts. See the repository README **Universal Install** for interactive vs. scripted behavior.
+
+Choose one active source of truth for the same Claude scope: Marketplace/native plugin, CLI install, or `--plugin-dir`. They can technically coexist, but running multiple complete copies in the same Claude session can duplicate commands, skills, agents, and hooks.
+
+The CLI enforces this for Marketplace installs: if Claude Code Marketplace already manages `frontend-craft`, `frontend-craft install/update claude` stops and tells you to update through Marketplace instead. `--force` does not override a Marketplace install.
+
+---
+
+## Claude Code Marketplace
+
+You can install `frontend-craft` as a Claude Code marketplace plugin. This loads the plugin natively inside Claude Code.
+
+The Marketplace entry resolves the plugin from the published npm package, which includes the compiled `dist/hooks/*.js` runtime files used by Claude hooks. If a Marketplace install reports a missing `dist/hooks/fec-*.js` file, update or reinstall the Marketplace plugin so Claude refreshes its plugin cache instead of copying files into the cache manually.
+
+---
+
+## Quick start after Marketplace install
+
+Get started in a few minutes:
+
+### Step 1: Install the plugin
+
+```bash
+# Add marketplace
+/plugin marketplace add bovinphang/frontend-craft
+
+# Install plugin
+/plugin install frontend-craft@frontend-craft
+
+# Activate
+/reload-plugins
+```
+
+### Step 2: Initialize project config (recommended)
+
+```bash
+# Copy project templates to .claude/ directory
+/fec-init
+```
+
+After initialization, customize for your project:
+
+1. `.claude/CLAUDE.md` — Update project info, package manager, common commands (source templates: `templates/claude/`; `/fec-init` copies into `.claude/`)
+2. `.claude/rules/` — Remove inapplicable rules (e.g. delete `fec-vue.md` for React-only projects, delete `fec-i18n.md` if i18n is not needed)
+3. `.claude/settings.json` — Adjust permission whitelist
+
+> **Why this step?** The plugin provides reusable Skills, Agents, and Hooks. CLAUDE.md and rules are project-level config and must live under the project root `.claude/` for Claude Code to recognize them. The `/fec-init` command helps you set this up quickly.
+>
+> `/fec-init` initializes project config; it is not a second plugin install. Keep the plugin body managed by Marketplace, CLI, or `--plugin-dir`, not more than one at once.
+
+### Step 3: Start using
+
+```bash
+# Full project review by default (outputs to reports/code-review-*.md)
+/fec-review
+
+# Explicit change review
+/fec-review review recent changes
+
+# Specify a file, directory or entire project (natural language, not CLI flags)
+/fec-review review src/components/Button.tsx
+/fec-review review src/features/
+/fec-review review the entire project
+
+# Create page/feature/component by convention
+/fec-scaffold page UserDetail
+/fec-scaffold component DataTable
+
+# List available commands
+/plugin list frontend-craft@frontend-craft
+```
+
+You now have access to the bundled agents, skills, and commands (see the root README **Feature overview** for the current list).
+
+---
+
+## Alternate install paths (Claude Code only)
+
+> **Requirements:** Claude Code v1.0.33+, Node.js 22+, npm/pnpm/yarn.
+
+### Option 1: Install as plugin (recommended)
+
+Same as **Step 1: Install the plugin** under **Quick start after Marketplace install** above (add marketplace, install plugin, `/reload-plugins`). You can also skip typing those commands in chat and add the marketplace via `~/.claude/settings.json` or project `.claude/settings.json`:
+
+```json
+{
+  "extraKnownMarketplaces": {
+    "frontend-craft": {
+      "source": {
+        "source": "github",
+        "repo": "bovinphang/frontend-craft"
+      }
+    }
+  }
+}
+```
+
+### Option 2: Team project-level auto-install
+
+Add the `extraKnownMarketplaces` config above to `.claude/settings.json` in the project root. Team members will be prompted to install when they trust the project directory.
+
+### Option 3: Local development / testing
+
+Clone the repo and load via `--plugin-dir` (no install, suitable for development and debugging):
+
+```bash
+git clone https://github.com/bovinphang/frontend-craft.git
+cd frontend-craft
+npm install
+npm run build
+cd ..
+claude --plugin-dir ./frontend-craft
+```
+
+When using `--plugin-dir` for development, run `npm run build` after changing hook or CLI sources because Claude executes the compiled files under `dist/`. Disable or avoid a Marketplace install of the same plugin in that session so you know which copy is running.
+
+### Option 4: Git Submodule (project-level sharing)
+
+```bash
+# Add as submodule in project root
+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"
+```
+
+After cloning, team members run:
+
+```bash
+git submodule update --init --recursive
+```
+
+Then load with `--plugin-dir`:
+
+```bash
+claude --plugin-dir .claude/plugins/frontend-craft
+```
+
+---
+
+## Updating (Marketplace and submodule)
+
+For Marketplace installs, run in Claude Code:
+
+```text
+/plugin marketplace update frontend-craft
+```
+
+Or enable auto-update so Claude Code pulls the latest on each start:
+
+1. Run `/plugin` in Claude Code to open the plugin manager
+2. Switch to the **Marketplaces** tab
+3. Select `frontend-craft`
+4. Choose **Enable auto-update**
+
+> Third-party Marketplaces do not enable auto-update by default. After enabling, Claude Code will refresh Marketplace data and update installed plugins on each start.
+
+For Git submodule installs:
+
+```bash
+git submodule update --remote .claude/plugins/frontend-craft
+```
+
+**CLI installs:** re-run `npx @bovinphang/frontend-craft@latest update claude --local` or `... --global` for the same scope, and read [CHANGELOG.md](../../CHANGELOG.md) for release notes. If Claude Code Marketplace is already installed, the CLI refuses Claude install/update and prints the Marketplace update path. If the opposite CLI scope is already installed, interactive terminals ask whether to keep that source updated or uninstall it before switching; non-interactive terminals print the exact commands to run.
+
+```bash
+npx @bovinphang/frontend-craft@latest update claude --global
+npx @bovinphang/frontend-craft@latest update claude --local
+```
+
+---
+
+**Other languages:** [简体中文](claude.zh-CN.md)
+
+## CLI compatibility update
+
+CLI hooks are merged into `settings.json`, preserving unrelated settings. Malformed JSON stops installation. Native Marketplace plugins continue to use `hooks/hooks.json`. See [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).