Quickstart

Get ContextForge running in an existing project in under two minutes.

ContextForge works with any existing project — it does not scaffold a new one. Run it inside your repo root.

Step 1 — Run init

From your project root, run:

bash

npx @contextforge/cli init

ContextForge will detect your stack, fetch the right packs from the registry, install them under .contextforge/, and create tiny pointer files at your root.

txt

$ npx @contextforge/cli init

✓ Fetching registry...
✓ Detected stack: nextjs, react, typescript, tailwind
✓ Installing core packs:
  · verification-before-completion
  · systematic-debugging
  · code-review
  · git-workflow
  · dependency-management
  · diataxis-docs
✓ Installing stack packs:
  · nextjs-best-practices
  · react-performance
  · tailwind-v4
  · typescript-advanced-types
✓ Writing .contextforge/config.json
✓ Writing .contextforge/lock.json
✓ Writing AGENTS.md
✓ Writing CLAUDE.md

Done. Your repo is AI-agent ready.

Step 2 — Choose your AI tool

During init, you will be asked which AI tools to configure:

txt

? Which AI tools do you use?
  ❯ All agents
    Codex only
    Claude Code only
    Cursor only
    GitHub Copilot only

ContextForge creates tool-specific instruction files for your selection.

Step 3 — Add more packs

After init, you can add extra packs at any time:

bash

npx @contextforge/cli add supabase

All CLI commands

npx @contextforge/cli initFirst-time setup. Detects stack and installs packs.

npx @contextforge/cli add <pack>Add a single pack.

npx @contextforge/cli syncRe-detect stack, update packs from registry.

npx @contextforge/cli doctorCheck installation health.

npx @contextforge/cli listList all registry packs.

npx @contextforge/cli search <query>Search packs by name or topic.

If something looks wrong after init, run npx @contextforge/cli doctor to diagnose, then npx @contextforge/cli sync to fix it.

Next: How ContextForge Works