GIR (Get It Running)

A modular Claude Code plugin ecosystem. Install only what you need — curated agents, auto-delegation, memory bank, and domain-specific tooling.

"Doom Song!"

What Is GIR?

GIR is a modular ecosystem that separates:

• Universal workflows (all projects)
• Project-specific details (your stack)
• Modular agents (opt-in only)

Drop into any project for instant Claude Code productivity.

Why Modular?

GIR is designed so you only pay the token cost for what you use. Install gir-core, then add only the spokes your project needs. No wasted context, no irrelevant tools loaded into every session.

Setup	Token Savings vs. Monolithic
Core only	~45% reduction
Core + 1 spoke	~35–40% reduction
Core + 2–3 spokes	~25–35% reduction
All 7 modules	Comparable total, but fully modular

Each module self-registers at session start. Installed modules list their tools in .gir/GIR.modules. Uninstalled modules are invisible — zero token overhead.

---

Architecture

GIR uses a hub-and-spoke model. gir-core is required and provides the foundation. Spoke plugins are optional and extend it for specific domains.

                        ┌─────────────────┐
                        │    gir-core     │  ← REQUIRED
                        │                 │
                        │  agents:        │
                        │  • feature-architect
                        │  • code-reviewer│
                        │  • debugger     │
                        │  • team-lead    │
                        │  • spec-analyst │
                        │                 │
                        │  skills + cmds  │
                        │  hooks + MCP    │
                        └────────┬────────┘
                                 │
    ┌────────────┬───────────────┼───────────────┬────────────┬────────────┐
    │            │               │               │            │            │
┌───▼───┐  ┌────▼────┐  ┌───────▼──────┐  ┌────▼────┐  ┌────▼───┐  ┌────▼───┐
│gir-web│  │gir-auto-│  │  gir-tools   │  │gir-data-│  │ gir-ai │  │ gir-qa │
│       │  │ mation  │  │              │  │  base   │  │        │  │        │
│• docs │  │         │  │ • agenthub   │  │         │  │• Gemini│  │• Code- │
│• deploy│ │ • n8n-  │  │ • subtask-   │  │• Supa-  │  │  -CLI  │  │  Rabbit│
│• ui-  │  │   builder│ │   manager    │  │  base   │  │• Codex │  │• Jules │
│  gen  │  │         │  │ • subtask    │  │  tools  │  │        │  │        │
│       │  │         │  │   skills     │  │         │  │        │  │        │
└───────┘  └─────────┘  └──────────────┘  └─────────┘  └────────┘  └────────┘

---

Token Economics

GIR is designed for zero wasted context. You only load what you use.

Setup	Context Used	Token Savings
Core only	~7-8K (3.5-4%)	45% vs. monolithic
Core + 1 spoke	~9-10K (4.5-5%)	35-40% savings
Core + 2-3 spokes	~11-14K (5-7%)	25-35% savings
All modules	~19-32K (10-16%)	Full modular ecosystem

What this means: Installing just gir-core uses less than 4% of your 200K context window, leaving 193K+ tokens for your actual code and tasks. Each additional module adds only 2-4K tokens.

If you need a module, install it. If you don't, it costs nothing.

---

Install

Step 1: Add the marketplace

claude plugin marketplace add rivit-studio/GIR

Step 2: Install core (required)

claude plugin install gir-core

Step 3: Install the modules you need

claude plugin install gir-web           # Frontend/fullstack (v0, Figma, Vercel)
claude plugin install gir-automation    # n8n workflow automation
claude plugin install gir-tools         # AgentHub + team coordination
claude plugin install gir-database      # Database management (Supabase)
claude plugin install gir-ai            # AI delegation (Gemini-CLI, Codex)
claude plugin install gir-qa            # QA & review (CodeRabbit, Jules)

Step 4: Discover modules

/gir-core:modules

---

Quick Start by Tech Stack

Next.js / React Fullstack

claude plugin install gir-core
claude plugin install gir-web         # Frontend tooling (v0, Figma, Vercel)

Then run /gir-core:init-project to scaffold CLAUDE-project.md for your stack.

Backend API

claude plugin install gir-core

Then run /gir-core:init-project to scaffold CLAUDE-project.md for your stack.

Full-Stack + Automation

claude plugin install gir-core
claude plugin install gir-web          # Frontend
claude plugin install gir-automation   # n8n workflows

Then run /gir-core:init-project to scaffold CLAUDE-project.md for your stack.

Data/ML Projects with Supabase

claude plugin install gir-core
claude plugin install gir-database     # Supabase tools

Then run /gir-core:init-project to scaffold CLAUDE-project.md for your stack.

---

Modules

Module	Description	Includes	Who needs it
gir-core	Core hub. Agents, delegation, workflows, memory bank, slash commands	5 agents, 6 skills, 6 commands, SessionStart hook, sequential-thinking MCP	Everyone
gir-web	Frontend and fullstack tooling — v0, Figma, Vercel	3 agents, 3 skills	Frontend/fullstack devs
gir-automation	n8n workflow building	1 agent, 1 skill	Teams using n8n
gir-tools	AgentHub integration and agent team coordination	2 agents, 2 skills	Power users running parallel agent workflows
gir-database	Database management — Supabase	1 skill	Projects using Supabase
gir-ai	AI tool delegation — Gemini-CLI, Codex	1 skill	Users with external AI tools
gir-qa	QA & review tools — CodeRabbit, Jules	1 skill	Teams using automated code review

---

What Stays in Your Project

GIR plugins install globally. Your project keeps its own configuration:

Files You Own & Customize

• CLAUDE-project.md — Edit this. Your project-specific tech stack, dev commands, environment variables, conventions, and architectural decisions. This is the single source of truth for your project context. Create it by running:

  /gir-core:init-project
  

  Then customize it for your stack.

Memory Bank (Optional but Recommended)

Create .gir/ for session-persistent patterns and decisions:

/gir-core:init-memory-bank

Files GIR creates/manages here:

• CLAUDE-activeContext.md — Current session state
• CLAUDE-patterns.md — Code conventions (auto-populated by debugger)
• CLAUDE-decisions.md — Architecture choices (auto-populated by feature-architect)
• CLAUDE-troubleshooting.md — Known issues and solutions (auto-populated by debugger)
• CLAUDE-resources.md — External references and docs

GIR populates these across sessions. You can also edit them manually.

Auto-Generated Registry

• .gir/GIR.modules — Auto-generated list of installed modules and their tools. Updated each session, never edit manually.

---

Important: What NOT to Edit

GIR plugin files are read-only in your project. They live globally and are managed by the plugin system. Your CLAUDE-project.md tells them how to adapt to your project—you don't edit their files directly.

If you need to customize plugin behavior:

1. Add directives to CLAUDE-project.md under [GIR CUSTOMIZATION] section
2. Create custom agents in .claude/agents/custom/ if needed
3. Use hook overrides (see module documentation)

---

Updating Modules

Check for updates

claude plugin list

Look for available updates in the GIR marketplace.

Update a module

claude plugin upgrade gir-core
claude plugin upgrade gir-web    # Update specific modules

Or update all:

claude plugin upgrade-all

What happens on update:

• Module agents, skills, and commands are updated globally
• Your CLAUDE-project.md and .gir/ files are never touched
• Memory bank files persist across updates
• Session hooks are refreshed with latest logic

---

Creating Custom Modules

Any Claude Code plugin can become a GIR module by including a gir-module.json manifest, a SessionStart hook for self-registration, and declaring "requires": ["gir-core"]. See PLAN-modularization.md for the full module contract.

---

FAQ

How do I set up a new project with GIR?

1. Install gir-core globally: claude plugin install gir-core
2. Install any domain-specific modules you need (gir-web, gir-automation, etc.)
3. In your project, run /gir-core:init-project to generate CLAUDE-project.md
4. Optionally run /gir-core:init-memory-bank to set up the .gir/ memory bank
5. Start a Claude Code session — GIR auto-discovers your config

What's the difference between gir-core and the spokes?

gir-core (required):

• Foundation agents: feature-architect, code-reviewer, debugger, spec-analyst, team-lead
• Core workflows and delegation rules
• Memory bank system
• Session start hook

Spokes (optional, domain-specific):

• gir-web: v0, Figma, Vercel tools
• gir-automation: n8n builder
• gir-tools: AgentHub, subtask parallel execution
• gir-database: Supabase
• gir-ai: External AI tools (Gemini-CLI, Codex)
• gir-qa: Code review (CodeRabbit, Jules)

Install only what your project needs.

Which files in my project should I edit?

Always edit:

• CLAUDE-project.md — Your tech stack, commands, conventions

Optionally edit:

• .gir/CLAUDE-patterns.md — Code patterns (or let agents populate it)
• .gir/CLAUDE-decisions.md — Architecture (or let agents populate it)
• .gir/CLAUDE-troubleshooting.md — Known issues (or let agents populate it)

Never edit:

• .gir/GIR.modules — Auto-generated, do not modify
• Plugin files (they're global, managed by the plugin system)

How do I customize GIR for my project?

Edit CLAUDE-project.md. Add a [GIR CUSTOMIZATION] section with:

• Custom delegation rules (who handles what)
• Project-specific state machines
• Environment-specific behaviors
• Team-specific conventions

Example:

## [GIR CUSTOMIZATION]

### Delegation Rules
- Database changes: Always review with DBA
- API changes: Feature-architect → code-reviewer → deploy

### State Machines
Feature states: Design → Development → Testing → Review → Deploy

Can I work on multiple projects with different stacks?

Yes. Each project has its own CLAUDE-project.md and .gir/ directory. GIR automatically uses the right configuration for each project. The plugins are global, but your project-specific settings keep them in sync.

What if I don't need the memory bank?

It's optional. .gir/ is created automatically but not required. If you don't use it, GIR will function fine with just CLAUDE-project.md.

Can I create custom agents?

Yes. Create .claude/agents/custom/ in your project and add agent definitions there. Reference them in CLAUDE-project.md under [GIR CUSTOMIZATION]. See plugin documentation for the agent spec.

How much token overhead does GIR add?

Per session:

• gir-core: ~3-4% of 200K context (7-8K tokens)
• Each additional module: ~1-2% (2-4K tokens)
• Total with all modules: ~10-16% (19-32K tokens)

This leaves ~188-193K tokens for your actual code and conversation. The modular design means you only pay for what you use.

How do I migrate from GIR v1 to v2?

Run the migration command from your project root:

/gir-core:migrate-v1

It will scan for v1 artifacts, back everything up, convert your CLAUDE.md to the new CLAUDE-project.md format, preserve your memory bank, clean up v1 files, and guide you through installing the right v2 modules. Memory bank files (.gir/) are fully compatible and will not be touched.

What if a module has an issue?

1. Check the module's documentation in the marketplace
2. Open an issue: https://github.com/rivit-studio/GIR/issues
3. Temporarily disable the module: claude plugin uninstall gir-<module>
4. For Claude Code platform issues (not GIR-specific), use https://github.com/anthropics/claude-code/issues
5. For third-party module issues, file with that module's maintainer

---

License

MIT — rivit-studio, 2026.