You are a documentation agent that explains how to create and use Claude Code agents.
**Traditional solo workflow:**
Build and deploy Node.js backend apps with first-class Vercel support (Serverless Functions), using modern tooling, deterministic builds, and production-grade conventions.
You are a code review agent. Your job is to systematically review pull requests using git terminal commands only, following industry best practices. You do not use GUI tools or web interfaces—only git commands executed in the terminal.
Analyze errors, trace issues, and fix bugs systematically.
You are a codebase agent specializing in lint compliance and code quality. You MUST keep existing lint scripts unchanged. Your job is to make code changes that satisfy all linting tools while applying TypeScript + React best practices for production-grade / enterprise-grade quality.
You are an expert TypeScript test-infrastructure engineer. You will generate a production-grade, reusable “Backend Conformance Kit†that validates common enterprise web-application behaviors (insurance-grade) using black-box HTTP tests. This kit must be framework-agnostic and reusable across any backend (Node, Bun, Laravel, Spring Boot, Go, etc.) by configuration only. Do NOT use any framework-native testing utilities. Treat the target system as an external HTTP API.
Executes bash commands
Hook triggers when Bash tool is used
Modifies files
Hook triggers on file write and edit operations
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Has parse errors
Some configuration could not be fully parsed
Has parse errors
Some configuration could not be fully parsed
A centralized Claude Code plugin containing agents, skills, hooks, and coding rules. Use this across all your projects without duplicating setup.
git clone https://github.com/judigot/ai.git ~/ai
Add to your .bashrc, .zshrc, or shell config:
alias cc='claude --plugin-dir ~/ai'
Reload your shell:
source ~/.bashrc
cd /path/to/any/project
cc
All your agents, skills, hooks, and rules are now available!
ai/
├── .claude-plugin/
│ └── plugin.json # Plugin manifest (required)
├── agents/ # Agent definitions (.md files)
│ ├── code-reviewer.md # Git-based PR review
│ ├── task-master.md # Worktree task execution
│ ├── multitasker.md # Parallel worktree management
│ └── agentic-workflow.md # Multi-agent coordination
├── skills/ # Specialized skills (subdirectories)
│ ├── lint-master/
│ │ └── SKILL.md # Multi-tool linting workflow
│ └── test-master/
│ └── SKILL.md # Testing infrastructure
├── hooks/
│ └── hooks.json # SessionStart, PreToolUse, Stop hooks
├── commands/ # Slash commands (.md files)
├── scripts/ # Helper scripts
├── settings/ # Personal settings (compartmentalized)
│ └── rules.md # Coding rules loaded on session start
├── CLAUDE.md # Plugin entry point
└── README.md
Your personal coding rules are stored in settings/rules.md, separate from ~/.claude. This provides:
The hooks/hooks.json loads your rules on every session start:
{
"SessionStart": [
{
"matcher": "*",
"hooks": [
{
"type": "command",
"command": "cat ${CLAUDE_PLUGIN_ROOT}/settings/rules.md"
}
]
}
]
}
The --plugin-dir flag tells Claude Code to load this plugin for any project:
claude --plugin-dir ~/ai
This applies your agents, skills, hooks, and settings globally without copying files to each project.
| Agent | Purpose |
|---|---|
code-reviewer | Git-based PR review with enterprise-grade analysis |
task-master | Execute single task in a worktree autonomously |
multitasker | Sprint orchestrator - creates worktrees and spawns parallel subagents |
agentic-workflow | Multi-agent coordination architecture |
Compatibility: All agents work with both Claude Code and OpenCode.
| Skill | Purpose |
|---|---|
lint-master | Multi-tool linting workflow (ESLint > Oxlint > Biome) |
test-master | Testing infrastructure and implementation |
Give the multitasker a list of tasks - it creates worktrees and spawns subagents:
"I need to work on auth, dashboard, and API features"
The multitasker will:
.worktrees/feat-auth, .worktrees/feat-dashboard, .worktrees/feat-apiPhilosophy: Git is the only source of truth. No Context.md, no .state files, no metadata.
For tasks that touch the same files or need strict sequencing:
./ai/scripts/ralph/ralph.sh 10
Start here: ai/scripts/ralph/
Local projects can have their own settings that extend the global ones:
my-project/
├── CLAUDE.md # Project-specific rules
├── .claude/
│ └── settings.local.json # Project-specific settings
└── agents/ # Project-specific agents (optional)
Claude Code loads in this order:
--plugin-dir) ← This repositoryCLAUDE.md.claude/ settingscd ~/ai
git pull
Changes apply to the next Claude Code session.
Create a new .md file in agents/:
---
name: my-agent
description: Use this agent when [conditions]. Examples:
<example>
Context: [Situation]
user: "[Request]"
assistant: "[Response]"
<commentary>
[Why this agent triggers]
</commentary>
</example>
model: inherit
color: blue
tools: ["Read", "Write", "Bash"]
---
You are an expert at...
[Agent instructions here]
Create a new subdirectory in skills/ with a SKILL.md file:
skills/
└── my-skill/
└── SKILL.md
The skill file follows the same format as agents.
npx claudepluginhub judigot/aiHarness for Claude Code — skills, /harness:* slash commands, persona subagents, lifecycle hooks, and MCP tools without per-repo `harness setup`. Sibling plugins exist for Cursor, Gemini CLI, and Codex.
11 agents, 35 skills, 18 commands, 9 hooks — spec-driven multi-agent orchestration for Claude Code, with optional cross-device semantic memory.
Standardize AI-generated projects with Ralph autonomous loop, persistent memory, and quality gates. Supports 28 languages, 17 frameworks, 13 MCP modules, and 20 services.
Complete project development toolkit: 23 agents, 23 slash commands, 29 lifecycle hooks, and 69 reusable skills for Claude Code workflows
Persistent memory, shared standards, and structured workflows for AI coding agents. Detects project setup and injects agent context automatically.
Portable Development System — AI-assisted development methodology with skills for consistency and agents for scale.