Your History Is the Training Data
Every Claude Code session is saved on your machine as JSONL files in ~/.claude/projects. That's a complete record of how you actually work: what went well, what Claude kept getting wrong, and the manual steps you repeat every week. Most people never look at it. The BuildPartner plugin's improve-system skill does.
What improve-system Does
It reviews your past sessions to capture learnings, audit your setup for rot, and recap recent work. The point is to see where you're losing time based on your real history rather than guesswork.
From Patterns to Skills
The payoff is in what it does with those patterns. improve-system surfaces the manual tasks you keep repeating and helps turn them into reusable skills and CLAUDE.md rules, so you stop re-explaining the same things session after session. Run it weekly — the plugin even nudges you to — and your setup keeps getting sharper.
Good to Know
The command is namespaced: it's /buildpartner:improve-system, not a bare /improve-system. The plugin is free to install; the separate buildpartner.ai web app adds accounts and paid tiers.
What's in the Guide
Where Claude Code keeps your session history, what improve-system reads and reports, how it turns repeated work into skills, the install and run commands, and a direct link to the repo.
The full field guide is in the PDF.
Get the Guide
Drop your email below and we'll send it straight to your inbox.