
# /init-project Generate a `CLAUDE-project.md` for the current project by detecting its tech stack and prompting for key configuration values. --- ## Instructions Follow these steps in order: ### Step 1: Detect the tech stack Look for these files in the current directory and read them if they exist: - `package.json` — Node.js/JavaScript/TypeScript project; extract `name`, `scripts`, `dependencies`, `devDependencies` - `Cargo.toml` — Rust project; extract `[package]` name and dependencies
# /migrate-v1 Migrate an existing GIR-v1 project to the GIR-v2 modular plugin system. Preserves all memory bank data, converts configuration files, removes v1 artifacts, and guides through v2 plugin installation. --- ## Instructions Follow these steps in order. **Do not skip steps.** Ask for user confirmation before any destructive action. ### Step 1: Detect GIR-v1 installation Scan the current project directory for GIR-v1 artifacts. Check for the existence of each of these files and direc
# /modules List installed GIR modules and discover available ones. --- ## Instructions Read `.gir/GIR.modules` and display the currently installed modules in a clean table format. Then inform the user about available official modules they haven't installed: **Official GIR Modules:** | Module | Description | Install | |--------|-------------|---------| | gir-core | Core agents, workflows, best practices (REQUIRED) | `claude plugin install gir-core` | | gir-web | Frontend/fullstack agents a
# /status Show an overview of the user's GIR configuration — what's installed, what's configured, and what's missing. --- ## Instructions Follow these steps in order. Gather all information before presenting the report. ### Step 1: Check installed GIR plugins Look for plugin directories under `~/.claude/plugins/`. Check whether these directories exist: - `~/.claude/plugins/gir-core/` - `~/.claude/plugins/gir-web/` - `~/.claude/plugins/gir-automation/` - `~/.claude/plugins/gir-tools/` - `~
Patterns for managing multiple Claude Code sessions using AgentHub
Parallel task execution using Git worktrees. Use this skill when the user wants to work on multiple features simultaneously, spawn parallel subagents, or distribute work across isolated environments. Enables faster development by running tasks concurrently while preventing code conflicts.
MCP tool reference for web development — v0, Figma, Vercel. Apply when doing UI generation or deployment for frontend work.
Enforce a precise, minimal design system inspired by Linear, Notion, and Stripe. Use this skill when building dashboards, admin interfaces, or any UI that needs Jony Ive-level precision - clean, modern, minimalist with taste. Every pixel matters.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
MCP tool reference for n8n workflow automation. Apply when building, validating, or debugging n8n workflows.
Spec-driven quality gates (SpecKit) for Claude Code. Enforces specification verification before implementation, test coverage requirements, and acceptance criteria checks. Use when building features that require formal specifications or quality assurance workflows.
Advanced workflow patterns for Claude Code including Explore-Plan-Code-Commit (E-P-C-C), multi-Claude coordination, parallel development, and iterative refinement loops. Use when planning multi-step implementations or complex engineering tasks.
Auto-delegation and task prioritization rules for Claude Code. Determines when to use subagents, which agent to delegate to, and how to break down complex tasks. Apply when planning work, starting new tasks, or when a task involves multiple concerns.
# /drift-check Assess whether the `.gir/` memory bank is stale and recommend what to update. --- ## Instructions Follow these steps in order: ### Step 1: Check if `.gir/CLAUDE-activeContext.md` exists Check whether `.gir/CLAUDE-activeContext.md` exists in the current project directory. **If it does not exist**, respond with: ``` No memory bank found. .gir/CLAUDE-activeContext.md does not exist in this directory. To set up a memory bank, run: /gir-core:init-memory-bank The memory ban
Autonomous execution mode for GIR — unattended operation, cap fail-safe, checkpoint/resume protocol. On-demand skill loaded by /gir:run.
Universal Claude Code best practices for any coding task. Covers tool usage patterns, anti-patterns, code review standards, commit conventions, and workflow quality standards. Apply to ALL software engineering tasks.
Native parallel agent execution using Claude Code's built-in Agent tool with worktree isolation. On-demand skill — load when parallel work is needed.
Continuous autonomous iteration patterns (Ralph Loops) for Claude Code. Enables self-directed build-test-fix cycles, progressive refinement, and autonomous quality improvement. Use when the user wants Claude to iterate autonomously on a task until completion.
GIR orchestration core — routing rules, delegation tiers, cost discipline, Graphify integration, escalation trigger, and lazy-load instructions. Always loaded.
AI tool delegation patterns — Gemini-CLI, Codex, and other external AI tools. Apply when delegating tasks to external AI tools to save tokens.
# /init-memory-bank Scaffold the `.gir/` memory bank directory in the current project with all 5 template files. --- ## Instructions Follow these steps in order: ### Step 1: Check for existing `.gir/` directory Check if `.gir/` already exists in the current project directory. - If `.gir/` **does not exist**: proceed directly to Step 2. - If `.gir/` **does exist**: warn the user and ask for confirmation before continuing: ``` Warning: .gir/ already exists in this directory. Existin
State machine templates and patterns for Claude Code. Provides structured state management for workflows, UI components, and process orchestration. Use when implementing stateful logic, workflow engines, or multi-step processes.
MCP tool reference for database management — Supabase. Apply when managing database schemas, migrations, edge functions, or querying data.
QA and code review tool integrations — CodeRabbit PR reviews, Jules AI delegation. Apply when doing code reviews, PR analysis, or delegating QA tasks.