@event4u/agent-config 9.7.0 → 9.9.0

package/docs/setup/per-ide/cursor.md

@@ -1,125 +0,0 @@
-# Cursor Setup
-
-Cursor reads two rule formats:
-
-- **Modern (`.mdc`)** — `.cursor/rules/<rule>.mdc` with YAML frontmatter
-  (`description`, `globs`, `alwaysApply`). Preferred for any 2025+
-  Cursor build.
-- **Legacy (`.cursorrules`)** — single-file aggregate at the repo root.
-  Still read by older Cursor versions; the package keeps it for
-  backward compatibility.
-
-The package ships **both** so you don't have to pick.
-
-## Prerequisites
-
-- Cursor 0.45+ (any 2025/2026 build): <https://cursor.com>.
-- Node.js ≥ 18.
-
-## Project install
-
-```bash
-npx @event4u/agent-config init --tools=cursor
-```
-
-This populates:
-
-- `.cursor/rules/*.mdc`     — one file per rule, modern frontmatter format
-- `.cursor/commands/*.md`   — slash commands mirrored from `dist/agent-src/commands/`
-- `.cursorrules`            — legacy single-file aggregate
-- `.agent-settings.yml`     — per-project knobs
-
-Combine surfaces if you use both Cursor and Claude Code:
-
-```bash
-npx @event4u/agent-config init --tools=cursor,claude-code
-```
-
-## Global install
-
-```bash
-npx @event4u/agent-config global --tools=cursor
-```
-
-Seeds `~/.cursor/rules/imported/event4u/` with the curated kernel +
-top-N skills. Cursor merges global + workspace rules — workspace wins
-on conflicts.
-
-## Modern `.mdc` frontmatter
-
-Each `.mdc` file has the Cursor-shaped header:
-
-```mdc
----
-description: Scope control — no unsolicited architectural changes
-globs:
-alwaysApply: true
----
-
-# Scope Control
-...
-```
-
-- `alwaysApply: true` ↔ source `type: "always"` (kernel rules).
-- `alwaysApply: false` ↔ Cursor model decides per turn (auto rules).
-- `globs:` is intentionally empty in the package's projection — apply
-  per-rule if you need path-scoped rules in your fork.
-
-## Cursor commands
-
-`.cursor/commands/<slug>.md` mirrors `.claude/commands/`. Nested
-clusters (e.g. `council/default.md`) flatten to `council-default.md` so
-Cursor's command palette stays flat.
-
-## Marketplace install (planned — Phase 7 / S35)
-
-The Cursor marketplace listing is filed in
-`road-to-simplicity-and-everywhere.md` Phase 7. Once accepted you'll
-be able to install via Cursor's Extensions panel without `npx`.
-
-## MCP block (when MCP Phase 3 ships)
-
-Add to `.cursor/mcp.json` (Cursor's project-scoped MCP config):
-
-```json
-{
-  "mcpServers": {
-    "event4u-agent-config": {
-      "command": "npx",
-      "args": ["-y", "@event4u/agent-config-mcp"]
-    }
-  }
-}
-```
-
-Track <https://github.com/event4u-app/agent-config> for the actual
-release tag — until `road-to-mcp-full-coverage` Phase 3 ships, this
-block is informational.
-
-## Verification
-
-```bash
-ls -la .cursor/rules/   | head -5      # *.mdc files exist
-ls -la .cursor/commands/| head -5      # *.md command files exist
-test -f .cursorrules                   # legacy aggregate exists
-```
-
-In Cursor itself: open the chat panel — settings should show the rules
-under **Project Rules**.
-
-## Troubleshooting
-
-| Symptom | Fix |
-|---|---|
-| Rules not picked up | Cursor < 0.45 — upgrade or rely on `.cursorrules`. |
-| Modern + legacy duplicate triggers | Disable `.cursorrules` in Cursor settings. |
-| Command missing in palette | `task generate-tools` then reload Cursor window. |
-| Global rules ignored | Cursor needs `~/.cursor/rules/` — check OS path expansion. |
-
-## Cross-references
-
-- [`docs/installation.md`](../../installation.md) — install matrix index.
-- [`AGENTS.md`](../../../AGENTS.md) — package self-orientation; Cursor
-  reads it via the projected rules.
-- [`src/templates/cursor-rule.mdc.j2`](../../../templates/cursor-rule.mdc.j2) —
-  template used by the projection generator.

package/docs/setup/per-ide/droid.md

@@ -1,65 +0,0 @@
-# Droid (Factory) Setup
-
-Droid (Factory AI's coding agent, <https://factory.ai>) reads the
-Anthropic-shaped markdown skill bundle from its user-scope anchor
-`~/.factory/`. The package deploys via the universal skill
-convention; project-scope bridge is not yet wired (Phase 2.4
-anchor).
-
-## Prerequisites
-
-- Factory CLI / extension: <https://factory.ai>.
-- Node.js ≥ 18 for the install entrypoints.
-
-## Install
-
-Global only (canonical scope):
-
-```bash
-npx @event4u/agent-config init --tools=droid --global
-```
-
-Populates:
-
-- `~/.factory/skills/`   — Anthropic-shaped skill bundle
-- `~/.factory/rules/`    — kernel + tier-1/2 rules
-- `~/.factory/personas/` — review-lens personas
-
-(Project-scope `--tools=droid` is rejected with exit code 1 —
-Droid has no documented project-discovery convention yet.)
-
-## How to use
-
-- Droid reads the skill bundle from `~/.factory/skills/` on every
-  session — no manual action required.
-- Slash commands (`/work`, `/implement-ticket`, `/commit`,
-  `/create-pr`, …) ship inside the skill bundle as named skills.
-  Invoke them by name in chat.
-- Factory ships **Droids** (named agent profiles); each Droid
-  honors the same skill bundle. Pick the Droid that matches the
-  task profile (e.g. *Code Droid* for implementation, *Review
-  Droid* for PR review).
-
-## Verification
-
-```bash
-test -d ~/.factory/skills
-test -d ~/.factory/rules
-```
-
-In Factory: spawn a Droid and ask *"What is this repo?"* — the
-answer should cite the AGENTS.md emergency triage block when the
-workspace is open.
-
-## Troubleshooting
-
-| Symptom | Fix |
-|---|---|
-| Skills not listed | Re-run `npx @event4u/agent-config init --tools=droid --global --force`. |
-| `--tools=droid` rejected | Add `--global` (Droid has global-only scope). |
-| Droid profile ignores rules | All Factory Droids read the same `~/.factory/skills/` bundle; verify the anchor exists. |
-
-## Cross-references
-
-- [`AGENTS.md`](../../../AGENTS.md) — canonical agent self-orientation.
-- [`docs/installation.md`](../../installation.md) — install matrix index.

package/docs/setup/per-ide/gemini-cli.md

@@ -1,45 +0,0 @@
-# Gemini CLI Setup
-
-Google's Gemini CLI reads `GEMINI.md` (which is a symlink to `AGENTS.md`
-in the package's projection) for project context.
-
-## Prerequisites
-
-- Gemini CLI installed: <https://github.com/google-gemini/gemini-cli>.
-- Node.js ≥ 18 (for the install entrypoints).
-
-## Install
-
-```bash
-npx @event4u/agent-config init --tools=gemini
-```
-
-Populates:
-
-- `GEMINI.md` → `AGENTS.md` — symlink so Gemini CLI loads the same
-  self-orientation as Codex / Aider / Augment.
-- `AGENTS.md`             — canonical content (single source of truth).
-- `.agent-settings.yml`   — per-project knobs.
-
-## Verification
-
-```bash
-test -L GEMINI.md && readlink GEMINI.md   # → AGENTS.md
-gemini --version                           # confirm CLI installed
-```
-
-In a Gemini CLI session: `GEMINI.md` informs every turn — verify by
-asking *"what is this repo?"* and confirming the answer matches
-`AGENTS.md`'s emergency-triage block.
-
-## Troubleshooting
-
-| Symptom | Fix |
-|---|---|
-| Gemini CLI doesn't see `GEMINI.md` | Some Gemini versions require absolute paths — `gemini --context $(pwd)/GEMINI.md`. |
-| Symlink broken on Windows | Re-run installer; on Windows the projection may emit a copy instead of a symlink. |
-
-## Cross-references
-
-- [`AGENTS.md`](../../../AGENTS.md) — canonical agent self-orientation.
-- [`docs/installation.md`](../../installation.md) — install matrix index.

package/docs/setup/per-ide/jetbrains.md

@@ -1,76 +0,0 @@
-# JetBrains AI Assistant Setup
-
-JetBrains AI Assistant reads custom prompts and guidelines from
-project-level config (`.idea/`) and user-scope settings. Because
-`.idea/` is team-shared, the canonical scope for this bridge is
-**global** — the project-scope marker is informational only.
-
-## Prerequisites
-
-- JetBrains IDE (IntelliJ IDEA, PyCharm, WebStorm, PhpStorm, …) with
-  the AI Assistant plugin enabled.
-- Node.js ≥ 18 for the install entrypoints.
-
-## Install
-
-Canonical (global, cross-project):
-
-```bash
-npx @event4u/agent-config init --tools=jetbrains --global
-```
-
-Deploys the universal skill bundle to `~/.config/JetBrains/`.
-
-Project-scope marker (informational only):
-
-```bash
-npx @event4u/agent-config init --tools=jetbrains
-```
-
-Populates (global):
-
-- `~/.config/JetBrains/skills/`  — Anthropic-shaped skill bundle
-- `~/.config/JetBrains/rules/`   — kernel + tier-1/2 rules
-- `~/.config/JetBrains/personas/` — review-lens personas
-
-Populates (project, informational):
-
-- `.jetbrains/agent-config.md` — pointer to the global install
-- `AGENTS.md`                  — canonical agent self-orientation
-- `.agent-settings.yml`        — per-project knobs
-
-## How to use
-
-- In your JetBrains IDE, open **Settings → Tools → AI Assistant →
-  Prompts** and point the custom-prompts path at
-  `~/.config/JetBrains/` (or copy the relevant rules into your
-  JetBrains profile via the *Import* button).
-- AI Assistant exposes **Chat**, **Ask**, and **inline edits**.
-  Chat is the surface that reads the imported rules; inline edits
-  stay local to the current selection.
-- Slash commands and skills live under `.augment/commands/` and
-  `.augment/skills/`. JetBrains AI does not register them natively
-  — invoke them by name in chat (e.g. *"run the create-pr command"*).
-
-## Verification
-
-```bash
-test -d ~/.config/JetBrains/skills
-test -f AGENTS.md
-```
-
-In the IDE: open the AI Assistant chat and ask *"What is this repo?"*
-— the answer should cite the AGENTS.md emergency triage block.
-
-## Troubleshooting
-
-| Symptom | Fix |
-|---|---|
-| Custom prompts not shown | Restart the IDE after pointing the prompts path at `~/.config/JetBrains/`. |
-| `.jetbrains/` missing | The project marker is optional; the canonical install is `--global`. |
-| AI Assistant ignores rules | Verify the prompts path under Settings; AI Assistant does not auto-discover `.idea/agent-config.md`. |
-
-## Cross-references
-
-- [`AGENTS.md`](../../../AGENTS.md) — canonical agent self-orientation.
-- [`docs/installation.md`](../../installation.md) — install matrix index.

package/docs/setup/per-ide/kilocode.md

@@ -1,66 +0,0 @@
-# Kilo Code Setup
-
-Kilo Code (VS Code extension, Cline fork) auto-discovers
-`.kilocode/rules/*.md` as system-level rules per project.
-
-## Prerequisites
-
-- Kilo Code VS Code extension: <https://github.com/Kilo-Org/kilocode>.
-- Node.js ≥ 18 for the install entrypoints.
-
-## Install
-
-Project scope (default):
-
-```bash
-npx @event4u/agent-config init --tools=kilocode
-```
-
-Global scope (cross-project, deploys the universal skill bundle to
-`~/.kilocode/`):
-
-```bash
-npx @event4u/agent-config init --tools=kilocode --global
-```
-
-Populates (project):
-
-- `.kilocode/rules/agent-config.md` — auto-discovered rule marker
-- `AGENTS.md`                       — canonical agent self-orientation
-- `.agent-settings.yml`             — per-project knobs
-
-## How to use
-
-- Rules under `.kilocode/rules/*.md` load automatically on every
-  Kilo Code session — no manual action required.
-- Kilo Code exposes a **mode switcher** (Architect / Code / Ask /
-  Debug / Orchestrator). Every mode sees these rules; switch modes
-  to trigger different cognition profiles. **Orchestrator** is the
-  closest match for running this package's `/implement-ticket` or
-  `/work` flows end-to-end.
-- Slash commands and skills live under `.augment/commands/` and
-  `.augment/skills/`. Kilo Code does not register them natively —
-  invoke them by name in chat (e.g. *"run the create-pr command"*).
-
-## Verification
-
-```bash
-test -f .kilocode/rules/agent-config.md
-test -f AGENTS.md
-```
-
-In VS Code: open the Kilo Code panel and ask *"What is this repo?"*
-— the answer should cite the AGENTS.md emergency triage block.
-
-## Troubleshooting
-
-| Symptom | Fix |
-|---|---|
-| Rules not picked up | Reload VS Code window after install. |
-| Marker missing after install | Re-run with `--force`. |
-| Orchestrator skips skills | Kilo Code does not auto-register `.augment/skills/`; name the skill in chat. |
-
-## Cross-references
-
-- [`AGENTS.md`](../../../AGENTS.md) — canonical agent self-orientation.
-- [`docs/installation.md`](../../installation.md) — install matrix index.

package/docs/setup/per-ide/kiro.md

@@ -1,72 +0,0 @@
-# Kiro Setup
-
-Kiro (Amazon's agentic IDE) auto-discovers `.kiro/steering/*.md`
-as steering documents per project.
-
-## Prerequisites
-
-- Kiro IDE: <https://kiro.dev>.
-- Node.js ≥ 18 for the install entrypoints.
-
-## Install
-
-Project scope (default):
-
-```bash
-npx @event4u/agent-config init --tools=kiro
-```
-
-Global scope (cross-project, deploys the universal skill bundle to
-`~/.kiro/`):
-
-```bash
-npx @event4u/agent-config init --tools=kiro --global
-```
-
-Populates (project):
-
-- `.kiro/steering/agent-config.md` — auto-discovered steering marker
-- `AGENTS.md`                      — canonical agent self-orientation
-- `.agent-settings.yml`            — per-project knobs
-
-## How to use
-
-Kiro ships two top-level workflows; both honor the steering
-documents in `.kiro/steering/`.
-
-- **Spec mode** — plan-first. Kiro produces a spec → task list →
-  implementation under your review. The closest match for the
-  package's `/implement-ticket` flow.
-- **Vibe mode** — free-form chat. Best for exploration, quick
-  edits, and one-off questions.
-- Steering documents load automatically on every Kiro session —
-  no manual action required for either workflow.
-- Slash commands and skills live under `.augment/commands/` and
-  `.augment/skills/`. Kiro does not register them natively —
-  invoke them by name in chat (e.g. *"run the create-pr command"*).
-- When the global skill bundle is installed, Kiro reads it from
-  `~/.kiro/steering/` (the skills are projected into the
-  steering anchor, not a separate `skills/` directory).
-
-## Verification
-
-```bash
-test -f .kiro/steering/agent-config.md
-test -f AGENTS.md
-```
-
-In Kiro: start a new Spec and ask *"What is this repo?"* — the
-answer should cite the AGENTS.md emergency triage block.
-
-## Troubleshooting
-
-| Symptom | Fix |
-|---|---|
-| Steering not loaded | Restart Kiro after install. |
-| Marker missing | Re-run with `--force`. |
-| Spec mode ignores rules | Both Spec and Vibe read `.kiro/steering/`; check the marker file actually exists at the project root. |
-
-## Cross-references
-
-- [`AGENTS.md`](../../../AGENTS.md) — canonical agent self-orientation.
-- [`docs/installation.md`](../../installation.md) — install matrix index.

package/docs/setup/per-ide/opencode.md

@@ -1,62 +0,0 @@
-# OpenCode Setup
-
-OpenCode (<https://opencode.ai>) reads the Anthropic-shaped markdown
-skill bundle from its user-scope anchor `~/.opencode/`. The package
-deploys via the universal skill convention; project-scope bridge
-is not yet wired (Phase 2.4 anchor).
-
-## Prerequisites
-
-- OpenCode CLI / IDE: <https://opencode.ai>.
-- Node.js ≥ 18 for the install entrypoints.
-
-## Install
-
-Global only (canonical scope):
-
-```bash
-npx @event4u/agent-config init --tools=opencode --global
-```
-
-Populates:
-
-- `~/.opencode/skills/`   — Anthropic-shaped skill bundle
-- `~/.opencode/rules/`    — kernel + tier-1/2 rules
-- `~/.opencode/personas/` — review-lens personas
-
-(Project-scope `--tools=opencode` is rejected with exit code 1 —
-OpenCode has no documented project-discovery convention yet.)
-
-## How to use
-
-- OpenCode reads the skill bundle from `~/.opencode/skills/` on
-  every session — no manual action required.
-- Slash commands (`/work`, `/implement-ticket`, `/commit`,
-  `/create-pr`, …) ship inside the skill bundle as named skills.
-  Invoke them by name in chat.
-- For repository-aware work, run OpenCode from the project root
-  so the agent can locate `AGENTS.md` and the project's own
-  `agents/` overlay.
-
-## Verification
-
-```bash
-test -d ~/.opencode/skills
-test -d ~/.opencode/rules
-```
-
-In OpenCode: ask *"What is this repo?"* — the answer should cite
-the AGENTS.md emergency triage block when the workspace is open.
-
-## Troubleshooting
-
-| Symptom | Fix |
-|---|---|
-| Skills not listed | Re-run `npx @event4u/agent-config init --tools=opencode --global --force`. |
-| `--tools=opencode` rejected | Add `--global` (OpenCode has global-only scope). |
-| AGENTS.md not picked up | Run OpenCode from the project root; the agent reads `AGENTS.md` from the workspace. |
-
-## Cross-references
-
-- [`AGENTS.md`](../../../AGENTS.md) — canonical agent self-orientation.
-- [`docs/installation.md`](../../installation.md) — install matrix index.

package/docs/setup/per-ide/qoder.md

@@ -1,63 +0,0 @@
-# Qoder Setup
-
-Qoder (<https://qoder.com>) reads the Anthropic-shaped markdown
-skill bundle from its user-scope anchor `~/.qoder/`. The package
-deploys via the universal skill convention; project-scope bridge
-is not yet wired (Phase 2.4 anchor).
-
-## Prerequisites
-
-- Qoder IDE: <https://qoder.com>.
-- Node.js ≥ 18 for the install entrypoints.
-
-## Install
-
-Global only (canonical scope):
-
-```bash
-npx @event4u/agent-config init --tools=qoder --global
-```
-
-Populates:
-
-- `~/.qoder/skills/`   — Anthropic-shaped skill bundle
-- `~/.qoder/rules/`    — kernel + tier-1/2 rules
-- `~/.qoder/personas/` — review-lens personas
-
-(Project-scope `--tools=qoder` is rejected with exit code 1 —
-Qoder has no documented project-discovery convention yet.)
-
-## How to use
-
-- Qoder reads the skill bundle from `~/.qoder/skills/` on every
-  session — no manual action required.
-- Slash commands (`/work`, `/implement-ticket`, `/commit`,
-  `/create-pr`, …) ship inside the skill bundle as named skills.
-  Invoke them by name in chat.
-- For repository-aware work, point Qoder at the project root so
-  the agent can locate `AGENTS.md` and the project's own
-  `agents/` overlay.
-
-## Verification
-
-```bash
-test -d ~/.qoder/skills
-test -d ~/.qoder/rules
-```
-
-In Qoder: open the chat panel and ask *"What is this repo?"* —
-the answer should cite the AGENTS.md emergency triage block when
-the workspace is open.
-
-## Troubleshooting
-
-| Symptom | Fix |
-|---|---|
-| Skills not listed | Re-run `npx @event4u/agent-config init --tools=qoder --global --force`. |
-| `--tools=qoder` rejected | Add `--global` (Qoder has global-only scope). |
-| AGENTS.md not picked up | Open the project root in Qoder; the agent reads `AGENTS.md` from the workspace. |
-
-## Cross-references
-
-- [`AGENTS.md`](../../../AGENTS.md) — canonical agent self-orientation.
-- [`docs/installation.md`](../../installation.md) — install matrix index.

package/docs/setup/per-ide/roocode.md

@@ -1,68 +0,0 @@
-# Roo Code Setup
-
-Roo Code (VS Code extension, formerly Roo Cline) auto-discovers
-`.roo/rules/*.md` as system-level instructions per project.
-
-## Prerequisites
-
-- Roo Code VS Code extension: <https://github.com/RooCodeInc/Roo-Code>.
-- Node.js ≥ 18 for the install entrypoints.
-
-## Install
-
-Project scope (default):
-
-```bash
-npx @event4u/agent-config init --tools=roocode
-```
-
-Global scope (cross-project, deploys the universal skill bundle to
-`~/.roo/`):
-
-```bash
-npx @event4u/agent-config init --tools=roocode --global
-```
-
-Populates (project):
-
-- `.roo/rules/agent-config.md` — auto-discovered rule marker
-- `AGENTS.md`                  — canonical agent self-orientation
-- `.agent-settings.yml`        — per-project knobs
-
-## How to use
-
-- Rules under `.roo/rules/*.md` load automatically on every Roo Code
-  session — no manual action required.
-- Roo Code exposes a **mode switcher** (Architect / Code / Ask /
-  Debug / Custom). Every mode sees these rules; switch modes to
-  trigger different cognition profiles without losing context.
-- Slash commands and skills live under `.augment/commands/` and
-  `.augment/skills/`. Roo Code does not register them natively —
-  invoke them by name in chat (e.g. *"run the create-pr command"*).
-- For free-form orchestration with the project's `/work` or
-  `/implement-ticket` workflows, name the command in chat; the
-  agent reads `.augment/commands/<name>.md` and follows the steps.
-
-## Verification
-
-```bash
-test -f .roo/rules/agent-config.md
-test -f AGENTS.md
-```
-
-In VS Code: open the Roo Code panel, switch to **Ask mode**, then
-ask *"What is this repo?"* — the answer should cite the AGENTS.md
-emergency triage block.
-
-## Troubleshooting
-
-| Symptom | Fix |
-|---|---|
-| Rules not picked up | Reload VS Code window after install. |
-| `.roo/rules/agent-config.md` missing | Re-run with `--force`. |
-| Mode switch loses context | Roo Code keeps rules across modes by design; verify the marker file still exists. |
-
-## Cross-references
-
-- [`AGENTS.md`](../../../AGENTS.md) — canonical agent self-orientation.
-- [`docs/installation.md`](../../installation.md) — install matrix index.