Accelerate

Unified Claude Code Agent Framework by Acceleration Guy

One command. Seven modules. 53 slash commands. Everything works together.

Quick Start

npx @accel/cli

Press Enter to install all modules. Restart Claude Code. Done.

What is Accelerate?

Accelerate brings structure and discipline to AI-assisted development with Claude Code. Instead of working with Claude in an unstructured way, Accelerate gives you:

• Rules that Claude follows automatically (Vector)
• Workspace state tracking so Claude knows what you're working on (Momentum)
• Structured development workflow — plan first, then build, then review (Drive)
• Guided project ideation for new projects (Ignition)
• Automated security auditing (Radar)
• Custom skill creation tools (Forge)
• One installer that manages everything (Mission Control)

The 7 Modules

Vector — Rules Engine

Runs automatically in the background. No slash commands needed.

Vector injects behavioral rules into every Claude Code session based on context. You define rules (e.g., "when touching auth code, always validate input") and Vector automatically applies them when your prompt matches trigger keywords.

How to use: Edit ~/.accel/modules/vector/vector.json to add your rules.

{
  "domains": {
    "security": {
      "rules": ["Always validate input at API boundaries"],
      "triggers": ["auth", "login", "password"]
    }
  }
}

| Command | What it does | |---------|-------------| | /vector:help | Show how Vector works and how to configure rules |

Momentum — Workspace State

Tracks your projects, tasks, and workspace health.

Momentum keeps Claude aware of what you're working on across sessions. It tracks active tasks, backlog items, project status, and workspace health as structured JSON. Python hooks inject this context into every Claude session automatically.

| Command | What it does | |---------|-------------| | /momentum:scaffold | Start here. Set up workspace tracking for your project | | /momentum:pulse | Quick health check — what's active, what's stale, any drift? | | /momentum:status | Show current workspace state | | /momentum:groom | Clean up backlog, reprioritize, close stale items | | /momentum:audit | Deep workspace optimization — find inefficiencies | | /momentum:history | Timeline of workspace changes | | /momentum:surface-create | Create a new data surface (tasks, backlog, etc.) | | /momentum:surface-list | Show all registered data surfaces | | /momentum:surface-convert | Convert a markdown file into a tracked data surface | | /momentum:vector-hygiene | Review and maintain Vector rules | | /momentum:audit-claude-md | Audit your CLAUDE.md and suggest improvements |

Drive — Dev Workflow

Structured development: plan first, build second, review third.

Drive enforces a Plan-Apply-Unify loop so you never write code without a plan. It tracks phases, milestones, and progress. Think of it as a project manager that lives inside Claude Code.

| Command | What it does | |---------|-------------| | /drive:init | Start here. Initialize Drive in your project | | /drive:progress | Where am I? Shows current phase and suggests next action | | /drive:plan | Create a detailed plan for a phase | | /drive:apply | Execute the current plan | | /drive:unify | Reconcile plan vs. what actually happened | | /drive:resume | Pick up where you left off (restores context) | | /drive:pause | Save context and prepare for a break | | /drive:handoff | Generate comprehensive handoff document | | /drive:help | Show all Drive commands | | /drive:milestone | Create a new milestone | | /drive:add-phase | Add a phase to current milestone | | /drive:remove-phase | Remove a future phase | | /drive:complete-milestone | Mark current milestone done | | /drive:discuss | Explore and articulate a phase vision | | /drive:discuss-milestone | Explore next milestone vision | | /drive:assumptions | Surface Claude's assumptions before planning | | /drive:research | Research a topic using subagents | | /drive:research-phase | Research unknowns for a specific phase | | /drive:discover | Explore technical options before planning | | /drive:consider-issues | Review deferred issues, triage them | | /drive:plan-fix | Plan fixes for issues found during testing | | /drive:verify | Guide manual acceptance testing | | /drive:audit | Run architectural audit on current plan | | /drive:flows | Configure workflow integrations | | /drive:config | Configure Drive settings | | /drive:map-codebase | Analyze codebase structure | | /drive:register | Register an existing project with Drive | | /drive:status | (Deprecated — use /drive:progress) |

Ignition — Project Incubation

Turn ideas into structured planning documents.

Ignition guides you through collaborative ideation for new projects. Instead of jumping straight to code, it walks you through questions that produce a solid PLANNING.md document.

5 project types: application, campaign, client, utility, workflow

| Command | What it does | |---------|-------------| | /ignition | Start here. Begin guided ideation for a new project | | /ignition:ideate | Full ideation workflow with guided questions | | /ignition:status | Check ideation progress | | /ignition:graduate | Promote ideation to a managed build | | /ignition:launch | Hand off to Drive for structured execution | | /ignition:add-type | Add a custom project type |

Radar — Security Auditing

12 engineering personas across 14 audit domains.

Radar performs comprehensive codebase audits using multiple specialized perspectives (security engineer, performance analyst, API designer, etc.). It can install real security tools (semgrep, gitleaks, trivy) for deep analysis.

| Command | What it does | |---------|-------------| | /radar:audit | Start here. Run a full codebase audit | | /radar:init | Initialize Radar for a target project | | /radar:status | Check audit progress | | /radar:report | Generate the audit report | | /radar:remediate | Generate fix plans for findings | | /radar:playbook | Create remediation playbook for a specific finding | | /radar:guardrails | Generate project rules from audit findings | | /radar:resume | Resume an interrupted audit | | /radar:validate | Test tool installation and framework integrity | | /radar:transform | Run full transform pipeline on completed audit |

Forge — Skill Builder

Build your own Claude Code slash commands.

Forge helps you create custom Claude Code skills (slash commands). It provides syntax specs, scaffolding templates, and quality auditing for the SKILL.md format.

| Command | What it does | |---------|-------------| | /forge | Overview of Forge workflows | | /forge:discover | Analyze an existing workflow to extract a skill | | /forge:scaffold | Generate the file structure for a new skill | | /forge:distill | Refine a rough skill into proper SKILL.md format | | /forge:audit | Quality-check a skill before sharing |

Mission Control — Orchestrator

Install, manage, and monitor all modules.

| Command | What it does | |---------|-------------| | /accel:status | Show all installed modules and health | | /accel:install | Install or update modules | | /accel:insights | Cross-module analytics and insights |

How Modules Work Together

Modules communicate through a file-based event bus. You don't manage this — it happens automatically.

/ignition → creates PLANNING.md → event → /drive picks it up
/drive → tracks phase progress → event → /momentum updates state
/radar → finds security issues → event → /momentum adds to backlog
/vector → rules applied to ALL modules automatically

Example flow:

1. You run /ignition and brainstorm a new app idea
2. Ignition produces a PLANNING.md and fires a plan-created event
3. You run /drive:progress — Drive finds the plan and starts tracking it
4. As you work through phases, Drive fires phase-progress events
5. /momentum:pulse shows your progress in the workspace health check
6. You run /radar:audit when ready — findings go to Momentum's backlog

Installation

Install all modules (recommended)

npx @accel/cli

Non-interactive (CI/scripting)

npx @accel/cli --all --non-interactive

Check status

npx @accel/cli status

Update

npx @accel/cli update

Remove a module

npx @accel/cli remove radar

Uninstall everything

npx @accel/cli uninstall

Requirements

• Claude Code — Accelerate extends Claude Code
• Node.js >= 16 — for the installer
• Python >= 3.9 — only if using Vector or Momentum (they use Python hooks)

What Gets Installed

~/.accel/                    Accelerate home
  manifest.json              What's installed
  modules/                   Module files
  events/                    Cross-module event bus
  mcp/                       MCP servers

~/.claude/
  commands/{module}/         Slash commands
  hooks/                     Python hooks (Vector, Momentum)

~/.mcp.json                  MCP server registration
~/.claude/settings.json      Hook registration

Documentation

• Getting Started — First 5 minutes with Accelerate
• Module Guide — Architecture, dependencies, event bus, troubleshooting

License

MIT — Built by Yogi Gnanavel (Acceleration Guy)

Based on open-source foundations by Chris Kahler, with integration, branding, and cross-module orchestration by Acceleration Guy.