Agent skill · software engineering · aiskillstore
kaizen
Guide for continuous improvement, error proofing, and standardization. Use this skill when the user wants to improve code quality, refactor, or discuss process improvements.
Why this skill is useful
Codifies incremental improvement practices and refactoring standards that the AI could infer but now doesn't have to guess.
What it needs
About 10k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Kaizen: Continuous Improvement Overview Small improvements, continuously. Error-proof by design. Follow what works. Build only what's needed. Core principle: Many small improvements beat one big change. Prevent errors at design time, not with fixes. When to Use Always applied for: Code implementation and refactoring Architecture and design decisions Process and workflow improvements Error handling and validation Philosophy: Quality through incremental progress and prevention, not perfection through massive effort. The Four Pillars 1. Continuous Improvement (Kaizen) Small, frequent improvements compound into major gains. Principles Incremental over revolutionary: Make smallest viable change that improves quality One improvement at a time Verify each change before next Build momentum through small wins Always leave code better: Fix small issues as you encounter them Refactor while you work (within scope) Update outdated comments Remove dead code when you see it Iterative refinement: First version: make it work Second pass: make it clear Third pass: make it efficient Don't try all three at once <Good> Each step is complete, tested, and working </Good> <Bad> Overwhelming, error-prone, hard to verify </Bad> In Practice When implementing features: 1. Start with simplest version that works 2. Add one improvement (error handling, validation, etc.) 3. Test and verify 4. Repeat if time permits 5. Don't try to make it perfect immediately When refactoring: Fix one smell at a time Commit after each improvement Keep tests passing throughout Stop when "good enough" (diminishing returns) When reviewing code: Suggest incremental improvements (not rewrites) Prioritize: critical → important → nice-to-have Focus on highest-impact changes first Accept "better than before" even if not perfect 2. Poka-Yoke (Error Proofing) Design systems that prevent errors at compile/design time, not runtime. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/kaizen