Getting Started
From zero to architecture-aware AI in 5 minutes.
Prerequisites
Forge DevKit works as a plugin system for AI coding assistants. You need one of these installed:
Claude Code
CLI for developers by Anthropic
Recommended
Claude Cowork
Desktop app with plugin support
Cursor
AI-powered code editor
Node.js 18+ is required for the Forge CLI.
Verify with node --version
Install Forge
Choose your preferred installation method:
Option A: CLI (recommended)
$ npm install -g @reumbra/forge
Installs the forge command globally. Works on all platforms.
Option B: Desktop App
Download for your platform
Pick the file for your OS in the Assets section: .exe for Windows, .dmg for macOS.
Windows (.exe)
The app is not code-signed yet. Windows SmartScreen may block the installer:
- When you see "Windows protected your PC", click "More info"
- Click "Run anyway"
macOS (.dmg)
The app is not notarized yet. macOS Gatekeeper will block it:
- Open System Settings → Privacy & Security
- Scroll down to find the blocked app message
- Click "Open Anyway"
Don't trust unsigned apps? Use the CLI instead - npm install -g @reumbra/forge is the same tool, installed from npm. Code signing is on our roadmap.
Activate your license
$ forge activate FRG-XXXX-XXXX-XXXX
Use the license key from your purchase confirmation email. Device activations per tier: Starter 2, Pro 3, Complete 5.
Don't have a license? Get one here.
Install plugins
After activation, forge automatically installs all plugins included in your plan. Run it to see your ecosystem:
forge
✦ Forge - Plugin manager for Claude Code v0.3.8
● Licensed FRG-YGGT..TRE4 · bundle · expires Mar 6, 2027 (365d)
6 plugins installed
◆ What would you like to do?
● Manage plugins (6 installed)
○ License & devices
○ Run diagnostics
○ Deactivate
○ Exit
| Plugin | Version | Status | Description |
|---|---|---|---|
| forge-autopilot | v1.4.0 | ✓ up to date | Batch autonomous development - Agent Teams orchestration |
| forge-core | v4.13.0 | ✓ up to date | Architecture audit, quality patterns, dev-skills generation |
| forge-product | v3.9.0 | ✓ up to date | Product design module - user flows, stories, UX criteria |
| forge-qa | v3.7.0 | ✓ up to date | QA meta-tool - test generation, coverage analysis, requirement traceability |
| forge-tracker | v3.3.0 | ✓ up to date | Issue tracking integration - GitHub/Linear/Jira sync |
| forge-worktree | v1.2.0 | ✓ up to date | Git worktree lifecycle - Docker isolation, port offsets, safe teardown |
Set up your AI environment
Follow the instructions for your platform:
Claude Code
We recommend running Claude Code with permissions bypassed:
$ claude --dangerously-skip-permissions
Why is this safe with Forge?
Forge has its own 7-gate quality system that validates every step before execution. The setup wizard reads dozens of files, runs detection commands, and writes configuration - standard Claude Code permission prompts would require hundreds of manual "Allow" clicks without adding meaningful safety. Forge's gates are your safety net.
Claude Cowork
After installing plugins, they appear in Claude Cowork but are disabled by default. You need to enable them:
- Open the Customize panel (briefcase icon in the left sidebar)
- Find Personal plugins section - you'll see all Forge plugins listed as "Disabled"
- Click each Forge plugin and toggle it to Enabled
- Start a new conversation
Tip: You don't need to enable all plugins at once. Start with Forge core - it's the foundation. Enable others as you need them.
Cursor
Install plugins the same way as for Claude Code (Steps 1-3 above). Cursor automatically picks up installed plugins from ~/.claude/.
After installation, reload the window: Cmd+Shift+P → Developer: Reload Window.
Run the setup wizard
Navigate to your project directory and type in the chat:
/forge:setup
The wizard runs through gates sequentially - detecting your ecosystem, auditing architecture, configuring pipeline, and generating project-specific dev-skills.
◆ Forge Ecosystem
Your project management meta-tools. Each adapter generates artifacts
in your project's .claude/ directory and can be safely removed afterward.
| Module | Version | What it does |
|---|---|---|
| forge-core | v4.13.0 | Dev-pipeline: architecture + contracts + code |
| forge-product | v3.9.0 | Product design: user flows, stories, UX |
| forge-qa | v3.7.0 | Test strategy: coverage, acceptance tests |
| forge-tracker | v3.3.0 | Task hub: GitHub/Linear/ClickUp sync |
| forge-autopilot | v1.4.0 | Agent Teams: triage, waves, zero conflicts |
| forge-worktree | v1.2.0 | Git worktree management for isolated dev |
Legend: All 6 modules installed, none yet configured.
Commands available after setup:
| Category | Commands |
|---|---|
| Setup & Management | /forge:setup, /forge:patch |
| Smart Routing | /forge:hub "describe what you want" |
| Development | /dev |
| Product | /forge:product design/epic/roadmap/strategy |
| Testing | /forge:qa test/coverage/plan |
| Task Tracking | /forge:tracker pick/sync/close |
| Autopilot | /forge:autopilot |
| Worktrees | /forge:worktree-setup |
◆ Gate 1: Architecture Audit - Results
Stack: Astro 5.7.0 + TypeScript 5.8.0 + Tailwind CSS 4.1.0
Build: Vite │ Linter: Biome 2.0.0 │ Hosting: Cloudflare Pages
Architecture: FSD-adapted (4 layers)
Layers:
pages: src/pages/ (15 files) - assembly & routing, i18n (en + ru)
widgets: src/widgets/ (32 files, 21 widgets) - composite blocks, zero cross-imports
shared: src/shared/ (41 files) - ui(13) + config(22) + i18n(3) + lib
layouts: src/layouts/ (2 files) - BaseLayout
Conflict zones: none (0 files)
Parallel readiness: 9/10 - highly parallel
Sibling repos:
| Repo | Stack | Role | Forge? |
|---|---|---|---|
| acme-web | React 19.2+TanStack | frontend | ✓ 4.6 |
| acme-api | NestJS 11+Prisma | backend-api | ✓ 4.12 |
You're all set
Your AI is now architecture-aware. The dashboard shows your complete ecosystem:
● Forge Ecosystem Dashboard - acme-web
| Component | Version | Status |
|---|---|---|
| forge-core | v4.13.0 | Configured |
| forge-product | v3.9.0 | Configured |
| forge-qa | v3.7.0 | Configured |
| forge-tracker | v3.3.0 | Configured |
| forge-autopilot | v1.4.0 | Active (6 batches) |
| forge-worktree | v1.2.0 | Active |
Project Profile
| Property | Value |
|---|---|
| Stack | React 19 + TanStack Start + Tailwind v4 + Vite + TypeScript strict |
| Architecture | FSD (5 layers, 13 features) |
| Pipeline | Parallel, trunk-based, conventional commits |
| Git workflow | Trunk-based with worktrees |
| CI/CD | Vercel (SSR Docker) |
| Backend | acme-api (bidirectional propagation) |
Ecosystem is fully configured and up to date. Available actions:
– /forge:hub - describe what you want, Hub routes to the right pipeline
– /forge:tracker - task management via Notion
– /forge:autopilot - batch development pipeline
– /forge:qa - testing and coverage
Start with Hub
Type /forge:hub "add payment system" and describe what you want to build. Hub classifies your intent, checks what prerequisites exist, and runs the right pipeline automatically. No commands to memorize.
Power users can also type /dev directly to skip prerequisite checks.
Other actions
- Run
/forge:setupanytime to see the dashboard or reconfigure - Check the Usage Guide for the full command reference
Quick command reference
| Command | Description | Plan |
|---|---|---|
| /forge:setup | Setup wizard, dashboard, upgrade, reconfigure | Starter+ |
| /forge:hub NEW | Universal entry point - describe what you want, Hub resolves prerequisites | Starter+ |
| /dev | Full development pipeline (generated after setup) | Starter+ |
| /forge:patch | Quick config patches without full setup | Starter+ |
| /forge:product | Design features, epics, roadmap, strategy | Pro+ |
| /forge:qa | Test strategy, generation, coverage analysis | Pro+ |
| /forge:tracker | Task management (GitHub, Linear, ClickUp, Notion, Jira) | Pro+ |
| /forge:autopilot | Batch development with Agent Teams | Complete |
| /forge:worktree-setup | Git worktree lifecycle templates | Starter+ |
| /forge:prompts | Prompt engineering (inventory, audit, evolve) | Pro+ |
| Advisory modules (Complete plan) | ||
| /forge:discovery | Product discovery (ideate, research, validate) | Complete |
| /forge:marketing | Marketing strategy (position, price, GTM) | Complete |
| /forge:copy | Brand voice copy (generate, review) | Complete |
| /forge:seo | SEO strategy (audit, keywords, schema) | Complete |
| /forge:analytics | Analytics planning (tracking, schemas, dashboards) | Complete |
| /forge:onboarding | Onboarding design (activation flows, audit) | Complete |
| /forge:growth | Growth strategy (retain, refer, expand) | Complete |
| /forge:ab | A/B experiments (hypothesis, design, analyze) | Complete |
Ready to make your AI architecture-aware?
One-time purchase. 14-day money-back guarantee.
Get Forge - from €29 →Troubleshooting
Plugins not showing up?
Claude Code: Type /exit then run claude again. Verify with /plugins.
Claude Cowork: Go to Customize → Personal plugins. If plugins are listed but "Disabled", click each one and enable it.
Setup wizard stuck?
The wizard saves progress after each gate. If interrupted, run /forge:setup again - it resumes from where you left off.
Windows SmartScreen blocks the installer?
Click "More info" → "Run anyway". The desktop app isn't code-signed yet. If you prefer, use the CLI: npm install -g @reumbra/forge.
macOS says "unidentified developer"?
System Settings → Privacy & Security → "Open Anyway". Or use the CLI instead.
License activation issues?
Run forge --diagnostics and send the output to support@reumbra.com.