self-improve
Skill0 starsChanged 27 days agoMITView on GitHub
Analyze past session logs to find repeated patterns, forgotten rules, and backtracking moments. Auto-update CLAUDE.md, skills, and rules to address gaps. "Correct once, never again.
39 other projects use a version of this.
Adopted by
Most recently taken up by
- savannahfeder/agentboxtheir own version, first seen Nov 15, 2026
- Hrutin-Suriya-Kotni/until-hiredtheir own version, first seen Nov 15, 2026
- 5uck1ess/devkittheir own version, first seen Nov 15, 2026
- Yeachan-Heo/oh-my-claudecodetheir own version, first seen Nov 9, 2026
- naman10parikh/pennyword for word, first seen Nov 8, 2026
- DYNO-SOFT/self-improving-looptheir own version, first seen Nov 8, 2026
Used with
Projects with it also use aeon-update, auto-workflow and 2 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
aaronjmarsSkillaeon-update
Pull framework updates from the upstream Aeon repo into this instance - 3-way merges canon's new commits into a PR, never clobbering operator config.
Also in 4 projects that use this
aaronjmarsSkillauto-workflow
Two-mode aeon.yml workflow builder - analyze inspects URLs and emits a tiered, signal-verified skill-enablement plan plus an aeon.yml diff; enable flips slugs to enabled:true and opens a PR.
Also in 4 projects that use this
- +2 more from aaronjmars
Other versions39 projects use a version of this.
Word for word · 4
- naman10parikh/agentgrid★ 9100% same
- naman10parikh/wikimem★ 8100% same
- naman10parikh/penny★ 0100% same
- naman10parikh/turbo★ 0100% same
Edited · 0
None found.
Wrote their own version · 35
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- zereight/gitlab-mcp★ 2.1ksame name
- aeonfun/aeon★ 793same name
- aaronjmars/aeon★ 789same name
- savannahfeder/agentbox★ 419same name
- forefy/.context★ 154same name
- eai-org/agent-toolkit★ 94same name
- nitinjain999/platform-skills★ 71same name
- aaronjmars/miroshark-aeon★ 20same name
25 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository59 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- agent-runtimeSkill
- frontend-designSkill
- architectSkill
- deep-thinkSkill
- design-systemsSkill
- ecosystem-referenceSkill
- fractal-delegationSkill
- harness-reviewSkill
- heartbeatSkill
- integrate-resourcesSkill
- llm-council-critiqueSkill
- loop-createSkill
- mcp-setupSkill
- memory-compressionSkill
- memorySkill
- model-routingSkill
- oss-project-scaffoldSkill
- playwright-cliSkill
- repo-scoutSkill
- skill-creatorSkill
- skill-routingSkill
- sprintSkill
- test-visualSkill
- troubleshootSkill
- ux-auditSkill
- Accessibility AuditorSkill
- artifacts-builderSkill
- brand-guidelinesSkill
- canvas-designSkill
- frontend-patternsSkill
- design-mirrorSkill
- design-system-starterSkill
- design-to-codeSkill
- feature-design-assistantSkill
- figma-implement-designSkill
- frontend-designSkill
- frontend-dev-guidelinesSkill
- mobile-designSkill
- motion-canvasSkill
- pixel-agent-uiSkill
- pixel-animateSkill
- pixel-anti-slopSkill
- pixel-brain-pageSkill
- pixel-migrate-next16Skill
- pixel-rsc-boundarySkill
- pixel-ship-gateSkill
- premium-web-designSkill
- senior-frontendSkill
- shadcnSkill
- tailwind-design-systemSkill
- tailwind-patternsSkill
- theme-factorySkill
- ui-design-systemSkill
- ui-ux-pro-maxSkill
- ux-researcher-designerSkill
- web-design-guidelinesSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 29 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
After several sessions of active development
- Distinctive: line 9
When you notice Claude making the same mistakes repeatedly
- Very specific: line 16
Read session files from ~/.claude/projects/ (JSONL format).
- Very specific: line 69
Fix: Always console.warn with context prefix and error message
- Very specific: line 70
RULE: Every catch block must either log or have // Intentionally silent: [reason]
“Common” is measured: kept by at least 6 in 10 of the 29 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
When to Use
- After several sessions of active development
- When you notice Claude making the same mistakes repeatedly
- Periodically (weekly) as a maintenance task
Process
1. Session Log Analysis
Read session files from ~/.claude/projects/ (JSONL format).
Look for:
- Questions Claude asks repeatedly (→ add answer to CLAUDE.md)
- Rules Claude forgets (→ add to .claude/rules/)
- Information Claude keeps re-discovering (→ promote to bootstrap memory)
- Patterns of backtracking (→ create a skill that prevents it)
- Tool call failures (→ improve error handling in hooks)
2. Signal Classification
- High confidence: Explicit corrections from user → immediately persist
- Medium confidence: Patterns that worked well → persist after confirming
- Low confidence: Observations → queue for review
3. Output
For each finding:
- Identify which file to update (CLAUDE.md, a rule, a skill, settings)
- Make the minimal change needed
- Log the improvement to CONTEXT.md
4. Verification
- Confirm CLAUDE.md is still under 80 lines / 2K tokens
- Confirm no conflicting rules exist
- Confirm skills are still discoverable (short descriptions)
Known Error Pattern Categories (Auto-Updated)
Category 1: Vercel Serverless State Loss
- Pattern: In-memory Maps/globals lost between Lambda invocations
- Files at risk: Any
const map = new Map()at module scope in API routes - Fix: Client-side state (Zustand/localStorage) + reconnect via SDK on every request
- Examples: ptyRegistry (terminal), desktopSessions (e2b-desktop)
Category 2: Race Conditions in E2B Sandbox Boot
- Pattern: Operation attempted before dependency is ready (Chrome, agent, PTY)
- Fix: Retry loop with backoff, never assume ready after fixed sleep
- Examples: Chrome window streaming, agent-runner readiness, CDP port binding
Category 3: SSE/Stream Timeout During Long Operations
- Pattern: Browser/proxy drops connection when no data flows for 10-15s
- Fix: Keepalive pings on all SSE streams
- Examples: Chat route during tool execution, terminal PTY during inactivity
Category 4: Silent Catch Blocks
- Pattern:
catch { }orcatch { /* comment */ }with no logging - Fix: Always
console.warnwith context prefix and error message - RULE: Every catch block must either log or have
// Intentionally silent: [reason]
Category 5: Missing Circuit Breakers
- Pattern: Unlimited retries or cascading failures from flaky dependencies
- Fix: Track failure count, open circuit after N failures, log transitions
- Examples: Anthropic API rate limits, Supabase connectivity, E2B sandbox creation
The Compound Effect
Each improvement makes the next session slightly better. Over weeks, this compounds into a dramatically better development experience. This IS AutoLab applied to our own tooling.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

