Configure once. Forget it exists.

Forge is a set-and-forget CLI. Run the wizard once, and your AI skills, rules, and workflows sync automatically across every tool and repo — forever.

forge init → forge sync

Terminal demo coming soon

Two minutes to set up. Zero maintenance.

Global setup (once per machine)

Run forge init --global and point it at your team's shared resource repo. The wizard detects your AI tools and writes the config. That's it — every new project you open gets synced automatically.

$ bun add -g @crucibledx/forge-cli
$ forge init --global
Done. Forge will sync automatically.

Per-project setup (once per repo)

Need project-specific skills? Run forge init inside the repo. Same wizard, same simplicity. Once configured, forget about it — Forge keeps everything in sync.

$ cd my-project
$ forge init
Project-level config created.

No YAML to hand-edit. No complex configs to learn. The wizard handles everything.

Best paired with an AI Resources Platform

Forge pulls from any git repo. But for the best experience, we recommend using a structured AI Resources Platform as your source — it gives you convention-over-configuration, versioned resources, automated testing, and a clear lifecycle from idea to delivery.

Forge works with any git source. The resources platform just makes it better.

12 commands. Everything you need.

CommandWhat it does
forge initInteractive wizard — detects AI tools, configures sources, writes config.
forge syncFetches from all sources, resolves targets, places files for each assistant.
forge statusShows drift between last sync and current filesystem state.
forge healthSLI dashboard — sync frequency, drift count, source reachability.
forge configInteractive config editor with section-based menu.
forge source listShows configured sources with type, synced file counts.
forge source addAdd a new source interactively.
forge source removeRemove a source with optional cleanup of synced files.
forge source editEdit existing source configuration with pre-filled values.
forge schedulerInstall/uninstall/status for OS-level auto-sync scheduling.
forge telemetryShows telemetry status, config, and what's collected.
forge uninstallRemoves .crucible directory, scheduler, and all synced files.

5 assistants. One config.

AssistantConfig PathsTransforms
Claude Code.claude/skills/, .claude/rules/, .claude/commands/None (passthrough)
Cursor.cursor/rules/.md → .mdc + frontmatter injection
Windsurf.windsurf/rules/, .windsurf/workflows/Frontmatter injection only
GitHub Copilot.github/skills/, .github/instructions/.md → .instructions.md + frontmatter
Cline.cline/skills/, .clinerules/None (passthrough)

Adding a new assistant = one file. Zero command handler changes.Learn more →

Built for real teams

Multi-source

Parallel fetching via Promise.allSettled. Failed sources don't block others.

🔀

Conflict resolution

Source + local conflict strategies: last-wins, first-wins, or error.

💾

Backup

When remote-wins overwrites local changes, .bak copies are created automatically.

🔐

SHA-256 detection

No unnecessary rewrites. Only writes when content actually changed.

📋

Dry-run

Preview all changes without writing. See what would happen before it does.

Rollback

On mutation failure, already-written files are rolled back. No partial state.

Scheduler

Cross-platform auto-sync: launchd (macOS), crontab (Linux), schtasks (Windows).

📊

Health dashboard

SLI metrics: sync frequency, drift count, source reachability, active assistants.

Three source layouts, auto-detected

Canonical

Flat files organized as skills/, rules/, workflows/ — distributed and transformed per assistant.

Pre-structured

Contains assistant-specific directories (.claude/, .cursor/, etc.) — copied as-is without transforms.

Hybrid

Mix of both — canonical files transformed and distributed; pre-structured files copied directly. Auto-detected by default.

Ready to get started?

Install Forge, run forge init, and sync your first config in under 2 minutes.

Quick Start Guide →