Your AI writes code. Forge makes it production-ready.
One command scans your repo — stack, layers, patterns — and generates guardrails your AI actually follows. 50+ quality rules. Works with Claude Code, Cursor, and any AI agent.
◆ Gate 1: Architecture Audit
Stack: NestJS 11.0 + TypeScript 5.8 + Prisma 6.2
Architecture: Clean Architecture (3 layers)
Database: PostgreSQL 16 │ CI: GitHub Actions
✓ 12 dev-skills generated
✓ 24 quality patterns applied
✓ Parallel readiness: 9/10
✦ Project ready. AI is now architecture-aware.
AI writes code fast. You fix it faster.
“Your AI forgets your architecture every session. You spend 20 minutes re-explaining what NestJS guards do.”
“Claude patches over bugs with quick fixes until the entire module is unmaintainable spaghetti.”
“I ran 3 agents in parallel. Spent 4 hours resolving merge conflicts. Net productivity: negative.”
“Unit tests pass with 100% coverage. Every assertion uses mock data. Zero real behavior tested.”
The real problem isn’t AI coding speed — it’s unstructured AI creating technical debt at scale.
Architecture-aware pipeline for AI agents
Understands your project
8-gate wizard auto-detects stack, layers, architecture patterns, and conventions. No manual config.
Enforces your standards
24 quality patterns, naming conventions, 15 LLM rationalization detectors. Prevention, not detection.
Structures the workflow
Design → Build → Verify. Scoped phases with quality gates. Requirement traceability end to end.
One forge setup → your AI codes like a senior engineer who’s read every file in the repo.
Six modules. One pipeline.
Each module handles one stage. Use all six for a full pipeline, or pick what you need — every module works standalone.
Your AI forgets your architecture. Forge doesn’t.
8-gate wizard auto-detects your stack, layers, architecture patterns, and conventions. Generates project-specific dev-skills. No manual config. No prompt engineering.
◆ 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 |
$ forge autopilot "auth, payments, notifications"
✓ Triage: 3 features classified
✓ Conflicts: auth ↔ payments (shared User model)
✓ Wave 1: [auth] [notifications] — parallel
✓ Wave 2: [payments] — after auth merges
⚡ Deploying 2 teammates to worktrees...
Parallel agents without merge hell
Agent Teams are powerful — until 3 agents edit the same file. forge-autopilot orchestrates autonomous teammates like Kubernetes orchestrates containers: backlog triage, conflict detection, wave execution, auto-merge.
Tests that trace back to requirements. Not AI guesswork.
forge-product creates verifiable acceptance criteria BEFORE code. forge-qa generates tests FROM those criteria. Every test proves a requirement.
// checkout.spec.ts
describe('US-3: Order Confirmation', () => {
// AC: US-3.AC-1
it('creates order with valid items
and shipping address', async () => {
const order = await checkout(validCart);
expect(order.status).toBe('confirmed');
expect(order.items).toHaveLength(3);
});
// AC: US-3.AC-2
it('sends confirmation email within
5 minutes', async () => {
await checkout(validCart);
const email = await getLastEmail(user);
expect(email.subject).toContain('Order');
expect(email.sentWithin).toBeLessThan(300);
});
// UX: loading-2
it('shows spinner during payment
processing', async () => {
const { getByRole } = render(<Checkout />);
fireEvent.click(getByRole('button'));
expect(getByRole('progressbar')).toBeVisible();
});
});
One setup. Project-aware AI forever.
INSTALL
npm i -g @reumbra/forge
Global CLI install
ACTIVATE
forge activate <license>
License key from purchase
SETUP
forge setup
8-gate wizard analyzes project, generates dev-skills
CODE
Use your AI normally
Claude Code / Cursor / Cowork detect .claude/ automatically
Generated artifacts work independently. Remove the plugin — your rules stay.
Six modules. One pipeline.
◇forge-core
Architecture audit & AI guardrails
7-gate
wizard
50+
quality patterns
15
rationalization detectors
3
template families
◇forge-product
Feature design in business language
- ✓ Product archetypes
- ✓ User flow generation
- ✓ User stories with acceptance criteria
- ✓ UX criteria library
◇forge-qa
Tests from requirements
- ✓ Multi-framework test generation
- ✓ Acceptance criteria to unit tests
- ✓ Use cases to E2E tests
- ✓ Requirement traceability matrix
◇forge-tracker
Bridge backlog and development
- ✓ GitHub integration
- ✓ ClickUp integration
- ✓ Linear integration
- ✓ Notion integration
- ✓ Jira integration
◇forge-autopilot
Parallel agents without merge hell
- ✓ Backlog → conflict detection → wave execution
- ✓ Autonomous teammates in isolated worktrees
- ✓ Auto-merge with conflict prevention
- ✓ 3 autonomy modes: supervised, semi-auto, full-auto
◇forge-worktree
Git worktree lifecycle manager
- ✓ 3 templates: Docker backend, Frontend, Generic
- ✓ Docker port isolation per worktree
- ✓ Auto-cleanup on branch merge
Use all six for a full pipeline. Use separately — each module works standalone.
One command. Full ecosystem visibility.
After setup, /forge:setup becomes your dashboard — plugin versions, project profile, integrations, and available actions. Everything your AI needs to know, always up to date.
● 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:setup upgrade --check — check for updates
– /forge:tracker — task management via Notion
– /forge:autopilot — batch development pipeline
– /forge:qa — testing and coverage
Transparent pricing. No token billing.
CORE
Includes 1 year of updates
Foundation for architecture-aware AI development
- ✓ Auto-detects your stack, layers, conventions
- ✓ 50+ quality patterns for AI-generated code
- ✓ Project-aware dev-skills — one setup, forever
- ✓ Scoped phases prevent runaway sessions
PRO
Includes 1 year of updates
Complete pipeline from design to tested code
- ✓ Everything in Core
- ✓ Describe features in business language — AI builds from spec
- ✓ Tests that trace back to requirements, not AI guesswork
- ✓ Full pipeline: design → code → test
BUNDLE
Includes 1 year of updates
All 6 modules today. Every new module tomorrow. One purchase.
- ✓ Everything in Pro
- ✓ Task tracker sync — GitHub, Linear, ClickUp, Jira, Notion
- ✓ forge-autopilot — parallel agent orchestration
- ✓ forge-worktree — git worktree lifecycle
- ✓ Every future module included
One-time purchase. Your artifacts stay forever.
Includes 1 year of updates. Renewal optional at reduced price.
No per-token charges. No usage limits. No surprise bills.
Frequently asked questions
How is this different from writing .cursorrules myself?
Auto-generated from architecture audit. Full pipeline, not just rules. Platform-agnostic — works in Cursor AND Claude Code AND Cowork.
Does it work with my stack?
8+ frameworks supported. 3 template families (NestJS/Clean Arch, generic backend, frontend). Stack-specific quality patterns auto-detected.
What if I remove Forge?
Disposable meta-tool: generated artifacts (dev-skills, tests, docs) work independently. Your code doesn't depend on Forge.
Does it work outside Claude Code?
.claude/ directory auto-detected by Cursor, Claude Desktop, Claude Cowork. Forge installs there — all platforms pick it up.
Is there a money-back guarantee?
Yes. 14-day money-back guarantee, no questions asked. If Forge doesn't improve your workflow, email us and we'll refund immediately.
What's the ROI of using Forge?
One prevented production bug pays for the entire year. At €29–79, Forge costs less than a single hour of debugging AI-generated regressions.
How does Forge compare to Devin?
Devin is an autonomous AI developer — it writes code for you. Forge is infrastructure for YOUR AI agent — it makes your existing tools (Claude Code, Cursor, Windsurf) architecture-aware. Devin costs €240/yr mandatory. Forge starts at €29 one-time.
Does Forge work with Claude Agent Teams?
Yes. forge-autopilot is specifically designed to orchestrate Agent Teams — it handles backlog triage, conflict detection, wave planning, and auto-merge. Think of it as Kubernetes for AI agents.
What AI coding tools does Forge support?
Any tool that reads CLAUDE.md, .cursorrules, or similar config files. This includes Claude Code, Cursor, Windsurf, Cline, and any future AI agent. Forge generates platform-agnostic artifacts.
What happens after the 1-year update period?
Your generated artifacts continue working forever — they're files in your project, not a service. You just won't get new quality patterns or module updates. Optionally renew at a reduced price to stay current.
Your AI should respect your architecture.
50+ guardrails. 7-gate audit. Tests from requirements. One setup.
One-time purchase. 14-day money-back guarantee.