No API key required — works with any Claude IDE

Scaffold AI agent projects
in seconds, not hours

One command gives you agents, slash commands, memory persistence, CI/CD pipelines, and devcontainers — all pre-wired for Claude Code.

Get started → See examples

Install via your preferred package manager

npm install -g claudeforge-cli
pip install claudeforge
uv tool install claudeforge
~ claudeforge create my-api
1
command to scaffold
25+
files generated
10
built-in slash commands
0
API keys needed

Everything you need for
AI-native development

claudeforge wires up the entire Claude Code ecosystem so you can ship, not configure.

🤖

Pre-built Agents

A production-ready code-reviewer agent ships out of the box. Add custom agents with one command — each with its own model, color, and description.

10 Slash Commands

/commit, /review-pr, /standup, /fix-issue and more — ready in Claude Code chat the moment you scaffold.

🧠

Persistent Memory

Four structured memory files load every Claude session so context survives restarts. Tell Claude to "remember" facts and they persist forever.

🔒

Safety Hooks

Pre-configured hooks block rm -rf, curl | bash, and credential file edits before they execute. Ship fast without shooting yourself in the foot.

🏗️

CI/CD out-of-the-box

GitHub Actions workflows for Node.js, Python, Go, and Rust. PR templates, issue templates, CODEOWNERS — all auto-detected from your stack.

🔌

Stack Detection

Scans your project for indicator files and auto-generates stack-specific commands, permissions, environment variables, and MCP server configs.

Zero to production in
four steps

The CLI scaffolds files; the Claude Code IDE extension handles all the AI work. No extra API keys.

1

Scaffold your project

Run claudeforge create my-project in your terminal. An interactive wizard asks for your project name, description, and tech stack — then generates 25+ files in seconds.

claudeforge create my-api
2

Set up context in the IDE

Open the project in VS Code / JetBrains with the Claude Code extension. Run /setup-project in chat — Claude reads your codebase and auto-fills every config file.

/setup-project "FastAPI with PostgreSQL"
3

Generate starter code

Run /scaffold-structure to create src/, tests/, and stack-appropriate starter files. Your project is now ready to develop.

/scaffold-structure
4

Use slash commands daily

Commit, review PRs, run standups, and fix issues — all from Claude Code chat. Extend with custom agents and commands as your project grows.

/commit   /review-pr   /standup

Real workflows,
ready to copy

Click a scenario to see exactly what to run.

Scaffold a production-ready Python API project with PostgreSQL, Redis, Docker, and GitHub Actions CI from scratch.

terminal
# 1. Create the project scaffold $ claudeforge create my-saas-api ✔ Project name: my-saas-api ✔ Description: SaaS REST API with auth and billing ✔ Stack: Python · FastAPI · PostgreSQL ✔ CI/CD: GitHub Actions ✔ Devcontainer: yes ✓ Scaffolded 27 files in my-saas-api/ # 2. Open in VS Code with Claude Code, then in chat: > /setup-project "FastAPI SaaS API with JWT auth, PostgreSQL, Redis cache, Stripe billing" Claude reading project… auto-filling CLAUDE.md, agents, memory ✓ Setup complete — run /scaffold-structure next # 3. Generate starter code > /scaffold-structure Created: src/main.py, src/models/, src/routes/, tests/ ✓ Starter structure ready

Set up a Next.js 14 app with TypeScript, Tailwind, and full GitHub Actions CI — in one command.

terminal
# Already have a Next.js project? Add claudeforge to it. $ cd my-nextjs-app $ claudeforge init Detected: Next.js · TypeScript · Tailwind CSS ✓ Created .claude/, memory/, CLAUDE.md, .mcp.json # Generate GitHub Actions CI for Node.js $ claudeforge github Stack detected: Node.js ✓ .github/workflows/ci.yml ✓ .github/pull_request_template.md ✓ .github/ISSUE_TEMPLATE/ (3 templates) ✓ .devcontainer/devcontainer.json # In Claude Code chat: > /setup-project "Next.js 14 app with App Router, Tailwind, Prisma, and NextAuth" ✓ All configs auto-generated from your description

Bootstrap a Go microservice with module detection, golangci-lint CI, and a custom reviewer agent.

terminal
$ claudeforge create payment-service ✔ Project name: payment-service ✔ Stack: Go ✔ CI/CD: GitHub Actions (golangci-lint + go test) ✓ Scaffolded in payment-service/ # Add a specialized migration safety reviewer $ claudeforge add agent migration-reviewer \ --description "Reviews Go database migrations for atomicity, rollback safety, and index impact" \ --model claude-opus-4-5 ✓ Created .claude/agents/migration-reviewer.md # In Claude Code chat: > /setup-project "gRPC payment microservice with CQRS, PostgreSQL, and distributed tracing" > /scaffold-structure ✓ Created cmd/, internal/, pkg/, migrations/, tests/

Add a SQL migration reviewer agent and a custom deploy command to any existing claudeforge project.

terminal
# Add a SQL safety reviewer agent $ claudeforge add agent sql-reviewer \ --description "Reviews SQL migrations for safety: checks for missing transactions, \ dangerous lock escalations, and missing rollback steps" \ --color "#f97316" ✓ .claude/agents/sql-reviewer.md # Add a /deploy slash command $ claudeforge add command deploy \ --description "Run pre-deploy checks, deploy to staging, run smoke tests, notify Slack" ✓ .claude/commands/deploy.md # Add a skill for project conventions $ claudeforge add skill api-conventions \ --description "REST API naming and error handling conventions for this repo" ✓ .claude/skills/api-conventions/SKILL.md # Check everything is wired up $ claudeforge status Agents: code-reviewer ✓ sql-reviewer ✓ Commands: commit ✓ deploy ✓ review-pr ✓ standup ✓ … Skills: api-conventions ✓ project-conventions ✓

A typical developer day using claudeforge slash commands in Claude Code chat.

Claude Code chat (IDE)
# Morning: generate standup from last 2 days of commits > /standup "last 2 days" Yesterday: Added JWT middleware, fixed race in auth handler Today: Migrating billing to Stripe v3, unblocked by auth work Blockers: None # Fix a bug fast > /fix-issue "TypeError: 'NoneType' has no attribute 'stripe_id' in billing/checkout.py line 87" Reading billing/checkout.py… Root cause: user.stripe_id not checked before use when subscription is free-tier ✓ Added null guard at billing/checkout.py:87 # Review your own PR before pushing > /review-pr Correctness ✓ LGTM Security ~ Add rate limiting to /checkout endpoint Performance ✓ LGTM Tests ⚠ Missing test for free-tier null guard # Commit with a conventional commit message > /commit ✓ fix(billing): guard against null stripe_id for free-tier users

Adding claudeforge to an existing repo without overwriting any of your current files.

terminal
$ cd my-existing-project # Preview what will be created (no writes) $ claudeforge init --dry-run Would create: .claude/settings.json Would create: .claude/commands/ (10 files) Would create: memory/MEMORY.md Would create: CLAUDE.md … (22 more) # Run for real — never overwrites existing files $ claudeforge init ✓ Scaffolded .claude/ infrastructure # Let Claude analyze your actual codebase (no description needed) > /analyze-project Reading package.json, src/, tests/ … Detected: Express.js · TypeScript · Jest · PostgreSQL ✓ CLAUDE.md filled with real commands, architecture, gotchas ✓ settings.json updated with stack-specific tool permissions ✓ memory/ seeded with project context

Agents for every
engineering task

One ships with claudeforge. Add more with a single command.

🔍
code-reviewer
Built-in · claude-sonnet-4-6
Reviews PRs across 7 categories: correctness, security, error handling, performance, test coverage, style, and documentation.
correctness security performance tests
🗄️
sql-reviewer
Custom · any model
Checks migrations for missing transactions, lock escalations, missing rollback steps, and index impact before they reach production.
migrations safety rollback
🔐
security-auditor
Custom · claude-opus-4-6
Audits code for OWASP Top 10 issues, secrets in source, insecure dependencies, and auth/authz flaws — powered by a deeper model for critical paths.
OWASP secrets auth
📝
doc-writer
Custom · any model
Generates README sections, API docs, and inline JSDoc/docstrings from code. Keeps docs in sync with implementation automatically.
README API docs JSDoc

Add any of the custom agents above with: claudeforge add agent <name> --description "..."

All commands at a glance

CLI (Terminal)

create [name]
Interactive wizard — scaffold a complete project from scratch
init
Add .claude/, memory/, hooks, and CLAUDE.md to any directory
project "desc"
Detect stack and write SETUP_CONTEXT.md for the IDE
add agent
Create a new specialized sub-agent in .claude/agents/
add command
Create a new slash command in .claude/commands/
add skill
Create a context skill in .claude/skills/
github
Generate GitHub Actions CI, PR templates, and devcontainer
status
Show configured agents, commands, memory files, and MCP servers
upgrade
Update built-in hooks and commands to latest (safe, preserves edits)
clear
Remove all claudeforge files (keeps your source code)

Slash Commands (Claude Code IDE)

/analyze-project
Auto-reads codebase and fills all configs — no description needed
/setup-project
AI-fills CLAUDE.md, agents, commands, memory from your description
/scaffold-structure
Creates src/, tests/, and stack-appropriate starter files
/project-health
Audits your AI setup and gives prioritized improvement suggestions
/memory-sync
Reviews session context and updates persistent memory files
/commit
Read git diff, stage files, and write a conventional commit
/review-pr
Review branch diff across 7 quality categories
/fix-issue "error"
Locate bug, form hypothesis, apply minimal fix
/standup
Generate standup summary from recent git commits
/explain-codebase
Explain architecture, flows, and what files to read first

Love it? Give it a star

Stars help other developers discover claudeforge. It takes one click and makes a huge difference.

Stars 0
Forks 0
Watching 0
jainvaibhav62 / claudeforge
Scaffold production-ready Claude Code projects in one command
JavaScript 🍴 📄 MIT
Join the community →

Ready to forge your first project?

Install claudeforge, run one command, and start building with AI — no API keys, no setup friction.