Installing Forge means deploying the architecture skill into your AI agent’s working directory. The installer copies the full skill runtime — scripts, templates, profiles, and reference documentation — into the agent-specific location your agent reads on startup, then wires up the appropriate hook so that rule enforcement happens automatically on every file write. You don’t need to configure anything in your project beyond running the install command; the skill loads itself the next time your agent starts a session.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/ronaldjdev/forge/llms.txt
Use this file to discover all available pages before exploring further.
Requirements
- Node.js 18 or higher — all skill scripts are pure ESM modules that run directly on Node.js with no build step
- One or more supported AI coding agents installed in your environment
| Agent | Notes |
|---|---|
| OpenCode | Primary target — full skill system via SKILL.md |
| Claude Code | Requires .claude/ directory |
| Cursor | Requires .cursor/ directory |
| Codex CLI | Uses .agents/ and .codex/ directories |
| Gemini Code Assist | Via .gemini/ directory |
Interactive Install
The recommended way to install Forge is through the interactive wizard. It detects which agents are installed in your environment, lets you choose one or more, and handles all directory creation, skill copying, hook wiring, and dependency setup automatically.Install for Specific Agents
If you already know which agent you want to target, pass the agent flag directly to skip the wizard entirely.- OpenCode
- Claude Code
- Cursor
- Codex CLI
- Gemini
- All Agents
Installs the skill into OpenCode loads skills automatically from
.opencode/skills/forge/ in your project directory, generates /forge-* slash commands, and installs the @opencode-ai/plugin dependency in .opencode/..opencode/skills/ when you open a project. No additional configuration is needed.Global Install
For OpenCode, you can install Forge globally so it is available in every project on your machine without a per-project install step.~/.config/opencode/skills/forge/ rather than .opencode/skills/forge/ in your current directory. OpenCode will load the global skill for any project that doesn’t have a local override.
What Gets Installed
The table below shows exactly where each agent’s skill lands, which hook is configured, and how the hook is triggered.| Agent | Skill Directory | Hook | Hook Type |
|---|---|---|---|
| OpenCode | .opencode/skills/forge/ | — | Via SKILL.md system (no separate hook file) |
| Claude Code | .claude/skills/forge/ | forgeSentinel | PostToolUse — runs after each Edit/Write/MultiEdit |
| Cursor | .cursor/skills/forge/ | forgeSmith | preToolUse — runs before each write, can deny |
| Codex CLI | .agents/skills/forge/ | forgeSentinel | PostToolUse — runs after each Edit/Write/apply_patch |
| Gemini | .gemini/skills/forge/ | — | Via SKILL.md (loaded at agent startup) |
/forge-* slash commands in .opencode/commands/ (for example /forge-cast, /forge-inspect, /forge-quench) so you can invoke any Forge command directly from the OpenCode command palette.
All hooks share the same detection logic from forgeSentinel-lib.mjs, so regardless of which agent you use, the rules being enforced are identical.
Verify Installation
After installation, confirm that Forge is active in one of these ways: Option 1 — Ask your agent directly: Open a session in the project and type:.opencode with the agent’s directory (.claude, .cursor, .agents, .gemini).
Option 3 — Check slash commands (OpenCode only):
Type /forge in the OpenCode command palette. You should see the full list of /forge-* commands available.
If you see errors about missing modules or scripts, re-run the install command. The skill directory may be incomplete if the install was interrupted.