continuous-improvement
About
This skill helps developers capture learnings after completing tasks by triggering on completion events, repeated mistakes, or retrospective requests. It guides reflection on what worked well, what was difficult, and identifies missing automation or documentation. The skill then systematically stores these insights in appropriate locations like Memory MCP, `.claude/rules/`, or creates new skills and TODOs.
Quick Install
Claude Code
Recommended/plugin add https://github.com/majiayu000/claude-skill-registrygit clone https://github.com/majiayu000/claude-skill-registry.git ~/.claude/skills/continuous-improvementCopy and paste this command in Claude Code to install this skill
Documentation
Continuous Improvement
After completing a task, briefly reflect and capture learnings.
When to Activate
- Task just completed
- Same mistake made twice
- User asks "what did I learn" or "retrospective"
- Complex process was difficult or slow
Reflect (30 seconds)
Ask yourself:
- What worked well?
- What was difficult or slow?
- What's missing (automation, docs, tools)?
Capture
| Learning Type | Action |
|---|---|
| Pattern/gotcha | Store in Memory MCP |
| Missing automation | Create issue/TODO |
| Repeated mistake | Update .claude/rules/ |
| Complex process | Create .claude/skills/ |
Memory Pattern
When storing a learning in Memory MCP:
mcp__memory__create_entities({
entities: [{
name: "Learning_TOPIC",
entityType: "development_learning",
observations: [
"Context: What was happening",
"Learning: What was learned",
"Application: How to apply it"
]
}]
})
Improvement Actions
| Issue | Solution |
|---|---|
| Same mistake twice | Add rule to .claude/rules/ |
| Manual process > 5 min | Create skill or hook |
| New tool/pattern | Store in Memory MCP |
| Missing documentation | Update docs |
Rule Addition Example
When you make the same mistake twice:
- Identify the pattern
- Create or update a rule file:
# .claude/rules/my-rules.md
---
paths: relevant/path/**
description: Rules for this area
---
## Critical Rules
| Rule | Why |
|------|-----|
| Don't do X | Because Y happens |
Skill Addition Example
When a process is complex and repeated:
- Create skill directory:
.claude/skills/my-skill/ - Create SKILL.md:
# .claude/skills/my-skill/SKILL.md
---
name: my-skill
description: When this skill should activate
---
# My Skill
## When to Activate
[Trigger conditions]
## Process
[Steps to follow]
Run /improve-claude-config for major configuration updates.
GitHub Repository
Related Skills
algorithmic-art
MetaThis Claude Skill creates original algorithmic art using p5.js with seeded randomness and interactive parameters. It generates .md files for algorithmic philosophies, plus .html and .js files for interactive generative art implementations. Use it when developers need to create flow fields, particle systems, or other computational art while avoiding copyright issues.
subagent-driven-development
DevelopmentThis skill executes implementation plans by dispatching a fresh subagent for each independent task, with code review between tasks. It enables fast iteration while maintaining quality gates through this review process. Use it when working on mostly independent tasks within the same session to ensure continuous progress with built-in quality checks.
executing-plans
DesignUse the executing-plans skill when you have a complete implementation plan to execute in controlled batches with review checkpoints. It loads and critically reviews the plan, then executes tasks in small batches (default 3 tasks) while reporting progress between each batch for architect review. This ensures systematic implementation with built-in quality control checkpoints.
cost-optimization
OtherThis Claude Skill helps developers optimize cloud costs through resource rightsizing, tagging strategies, and spending analysis. It provides a framework for reducing cloud expenses and implementing cost governance across AWS, Azure, and GCP. Use it when you need to analyze infrastructure costs, right-size resources, or meet budget constraints.