@event4u/agent-config 2.2.2 → 2.3.0

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

@@ -0,0 +1,68 @@
+# Continue.dev Setup
+
+Continue.dev (VS Code + JetBrains extension) auto-discovers
+`.continue/rules/*.md` as system-level rules per project.
+
+## Prerequisites
+
+- Continue extension: <https://continue.dev>.
+- Node.js ≥ 18 for the install entrypoints.
+
+## Install
+
+Project scope (default):
+
+```bash
+npx @event4u/agent-config init --tools=continue
+```
+
+Global scope (cross-project, deploys the universal skill bundle to
+`~/.continue/`):
+
+```bash
+npx @event4u/agent-config init --tools=continue --global
+```
+
+Populates (project):
+
+- `.continue/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 `.continue/rules/*.md` load automatically on every
+  Continue session — no manual action required.
+- Continue exposes **Chat**, **Edit** (inline) and **Autocomplete**
+  surfaces. All three honor the rules; Chat is the surface that
+  reads `AGENTS.md` and the skill bundle.
+- Slash commands and skills live under `.augment/commands/` and
+  `.augment/skills/`. Continue does not register them natively —
+  invoke them by name in chat (e.g. *"run the create-pr command"*).
+- For repository-aware orchestration, use **`@codebase`** in
+  Continue chat alongside the named command/skill so Continue
+  retrieves the relevant files first.
+
+## Verification
+
+```bash
+test -f .continue/rules/agent-config.md
+test -f AGENTS.md
+```
+
+In VS Code or JetBrains: open the Continue 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 the IDE window after install. |
+| Marker missing | Re-run `npx @event4u/agent-config init --tools=continue --force`. |
+| Continue ignores `@codebase` results | Index the workspace once via the Continue settings panel. |
+
+## Cross-references
+
+- [`AGENTS.md`](../../../AGENTS.md) — canonical agent self-orientation.
+- [`docs/installation.md`](../../installation.md) — install matrix index.

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

@@ -0,0 +1,65 @@
+# 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/jetbrains.md

@@ -0,0 +1,76 @@
+# 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

@@ -0,0 +1,66 @@
+# 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

@@ -0,0 +1,72 @@
+# 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

@@ -0,0 +1,62 @@
+# 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

@@ -0,0 +1,63 @@
+# 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

@@ -0,0 +1,68 @@
+# 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.

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

@@ -0,0 +1,63 @@
+# Trae Setup
+
+Trae (ByteDance's AI IDE, <https://trae.ai>) reads the Anthropic-shaped
+markdown skill bundle from its user-scope anchor `~/.trae/`. The
+package deploys via the universal skill convention; project-scope
+bridge is not yet wired (Phase 2.4 anchor).
+
+## Prerequisites
+
+- Trae IDE: <https://trae.ai>.
+- Node.js ≥ 18 for the install entrypoints.
+
+## Install
+
+Global only (canonical scope):
+
+```bash
+npx @event4u/agent-config init --tools=trae --global
+```
+
+Populates:
+
+- `~/.trae/skills/`   — Anthropic-shaped skill bundle
+- `~/.trae/rules/`    — kernel + tier-1/2 rules
+- `~/.trae/personas/` — review-lens personas
+
+(Project-scope `--tools=trae` is rejected with exit code 1 — Trae
+has no documented project-discovery convention yet.)
+
+## How to use
+
+- Trae reads the skill bundle from `~/.trae/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.
+- Trae exposes **Chat** and **Builder** modes; both surfaces read
+  the same skill bundle. Builder is the closest match for the
+  package's `/implement-ticket` flow.
+
+## Verification
+
+```bash
+test -d ~/.trae/skills
+test -d ~/.trae/rules
+```
+
+In Trae: 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=trae --global --force`. |
+| `--tools=trae` rejected | Add `--global` (Trae has global-only scope). |
+| Builder ignores rules | Reload the Trae workspace; the bundle is indexed on session start. |
+
+## Cross-references
+
+- [`AGENTS.md`](../../../AGENTS.md) — canonical agent self-orientation.
+- [`docs/installation.md`](../../installation.md) — install matrix index.

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

@@ -0,0 +1,63 @@
+# Warp Setup
+
+Warp (the AI terminal, <https://www.warp.dev>) reads the
+Anthropic-shaped markdown skill bundle from its user-scope anchor
+`~/.warp/`. The package deploys via the universal skill convention;
+project-scope bridge is not yet wired (Phase 2.4 anchor).
+
+## Prerequisites
+
+- Warp terminal: <https://www.warp.dev/download>.
+- Node.js ≥ 18 for the install entrypoints.
+
+## Install
+
+Global only (canonical scope):
+
+```bash
+npx @event4u/agent-config init --tools=warp --global
+```
+
+Populates:
+
+- `~/.warp/skills/`   — Anthropic-shaped skill bundle
+- `~/.warp/rules/`    — kernel + tier-1/2 rules
+- `~/.warp/personas/` — review-lens personas
+
+(Project-scope `--tools=warp` is rejected with exit code 1 — Warp
+has no documented project-discovery convention yet.)
+
+## How to use
+
+- Warp's **Agent Mode** reads the skill bundle from `~/.warp/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 the Warp AI prompt.
+- For repository-aware work, `cd` into the project root before
+  invoking Agent Mode so the agent can locate `AGENTS.md` and the
+  project's own `agents/` overlay.
+
+## Verification
+
+```bash
+test -d ~/.warp/skills
+test -d ~/.warp/rules
+```
+
+In Warp: open Agent Mode and ask *"What is this repo?"* — the
+answer should cite the AGENTS.md emergency triage block when the
+working directory is inside the project.
+
+## Troubleshooting
+
+| Symptom | Fix |
+|---|---|
+| Skills not listed | Re-run `npx @event4u/agent-config init --tools=warp --global --force`. |
+| `--tools=warp` rejected | Add `--global` (Warp has global-only scope). |
+| AGENTS.md not picked up | `cd` into the project root before invoking Agent Mode. |
+
+## Cross-references
+
+- [`AGENTS.md`](../../../AGENTS.md) — canonical agent self-orientation.
+- [`docs/installation.md`](../../installation.md) — install matrix index.