Jerry Framework
A Claude Code plugin for behavior and workflow guardrails with knowledge accrual.
What is Jerry?
Jerry is a Claude Code plugin that adds structured problem-solving capabilities, work tracking, and knowledge management to your Claude Code sessions. It combats Context Rot—the phenomenon where LLM performance degrades as context fills—through persistent artifacts and filesystem-based memory.
Note: You do NOT need Python installed to use Jerry. The plugin runs within Claude Code using its built-in capabilities. Python is only required if you want to contribute to Jerry's development.
"The effective context window where models perform optimally is often <256k tokens, far below advertised limits." — Chroma Research
Quick Start
Prerequisites
- Claude Code installed and configured
- Git for cloning the repository
- uv for Python dependency management (required for hooks)
Installation
Jerry is installed via a local marketplace. Choose your platform:
macOS
# 1. Install uv (if not already installed)
curl -LsSf https://astral.sh/uv/install.sh | sh
# 2. Clone Jerry to a local directory
mkdir -p ~/plugins
git clone https://github.com/geekatron/jerry.git ~/plugins/jerry
# 3. In Claude Code, add the local marketplace
/plugin marketplace add ~/plugins/jerry
# 4. Install the Jerry plugin
/plugin install jerry@jerry-framework
Windows (PowerShell)
# 1. Install uv (if not already installed)
powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
# 2. Restart your terminal to update PATH, then verify
uv --version
# 3. Clone Jerry to a local directory
New-Item -ItemType Directory -Force -Path "$env:USERPROFILE\plugins"
git clone https://github.com/geekatron/jerry.git "$env:USERPROFILE\plugins\jerry"
# 4. In Claude Code, add the local marketplace (use forward slashes)
/plugin marketplace add C:/Users/$env:USERNAME/plugins/jerry
# 5. Install the Jerry plugin
/plugin install jerry@jerry-framework
Verify Installation
After installation, run /plugin in Claude Code and check the Installed tab. You should see jerry listed.
See docs/INSTALLATION.md for detailed instructions and troubleshooting.
Platform Support
Jerry is primarily developed and tested on macOS. We are actively working on cross-platform portability, with Windows support as the immediate priority.
| Platform | Status |
|---|---|
| macOS | Primary — fully supported |
| Linux | Expected to work — not regularly tested |
| Windows | In progress — core functionality works, edge cases may exist |
Encountering a platform-specific issue? File a report using the template for your platform:
Your reports directly drive portability improvements.
Jerry's CI pipeline tests on macOS, Ubuntu, and Windows. See CONTRIBUTING.md for platform-specific development notes.
Known Limitations
- Skill and agent definitions are not yet optimized. Current definitions are comprehensive but verbose. Optimization for token efficiency and best-practice alignment is on the roadmap for upcoming releases.
- Windows portability is in progress. Some hooks and scripts may behave differently on Windows. See Platform Support above.
Using Jerry
Jerry provides skills—natural language interfaces you invoke with slash commands:
| Skill | Purpose | Example |
|---|---|---|
/problem-solving | Research, analysis, root cause investigation | "Research OAuth2 patterns" |
/worktracker | Task and work item management | "Create a task for login feature" |
/nasa-se | Systems engineering (NPR 7123.1D) | "Define requirements for API" |
/orchestration | Multi-phase workflow coordination | "Orchestrate the release pipeline" |
/architecture | Design decisions and ADRs | "Create ADR for caching strategy" |
/transcript | Meeting transcript parsing | "Parse the meeting notes" |
Example Session
You: /problem-solving analyze why the tests are failing