-
Notifications
You must be signed in to change notification settings - Fork 0
FAQ
Yes, but you lose behavioral rules (communication, planning, critical partner). The global CLAUDE.md defines how Claude works. The project one defines what it works on.
/forge diff detects it and /forge sync warns you before overwriting. You can accept or reject each file individually.
Create stacks/<name>/ with rules/*.md (with globs: frontmatter) and settings.json.partial. See Creating Stacks.
/forge export cursor → .cursorrules
/forge export codex → AGENTS.md
/forge export windsurf → .windsurfrules
/forge export openclaw → OpenClaw workspace skill
Hooks are converted to text instructions (no enforcement outside Claude Code).
cd ~/path/to/claude-kit
git pull
./global/sync.shThen in each project: /forge diff → /forge sync.
registry/projects.yml tracks all bootstrapped projects: name, path, stacks, score, audit history. /forge status reads it for the dashboard.
No. With minimal profile they aren't installed. With standard/full they are, but Claude decides when to use them based on the orchestration rule.
Yes. global/sync.sh detects the platform and uses file copies as fallback when symlinks aren't supported (Git Bash, WSL).
Yes. Either:
-
/forge export openclaw— generates a project-specific OpenClaw skill -
bash integrations/openclaw/install.sh— installs the forge bridge for all projects
/forge rule-check cross-references rule globs against git history. Rules with <10% match rate are candidates for removal. /forge benchmark compares full config vs minimal on standardized tasks.
Plugin mode (via marketplace) gives you skills, agents, hooks, and commands. Full mode (git clone) adds the factory system: stack detection, template sync, registry tracking, practices pipeline, session metrics, config validation.