kaizenlisted

Apply four design-time guardrails to every code decision: incremental improvement, error-proofing, standardization, and avoid over-engineering. Use when the user is about to write code, refactor, or handle errors and wants to avoid over-engineering or apply YAGNI.
Git-Fg/taches-principled · ★ 0 · AI & Automation · score 76

Install: claude install-skill Git-Fg/taches-principled

## Routing Guidance - IMMEDIATELY before writing code — these constraints apply to every decision. - FIRST when tempted to add abstractions, speculate about future needs, or fix everything in one pass. - DO NOT use when implementing trivial one-liners — use for architectural decisions, refactoring, and non-trivial implementation choices. - CONTRAST with ideation: that explores WHAT to build; kaizen shapes HOW to build it. - CONTRAST with plan-do-check-act: that tests changes; kaizen prevents bad patterns from entering the codebase. - CONTRAST with ddd: kaizen is a lightweight filter of 4 design-time constraints applied to every code change; ddd is a detailed analysis methodology with 4 modes (ARCHITECTURE, QUALITY, TRANSPARENCY, API) invoked when structural issues need a deep review. Run kaizen continuously; invoke ddd when a specific structural question surfaces. ## What This Skill Changes **Default behavior:** Claude makes code decisions on intuition — adds abstractions for anticipated flexibility, fixes multiple issues at once, handles errors after they occur, and introduces new patterns without checking existing conventions. **With this skill:** Every code decision gets filtered through four design-time constraints. Abstractions require concrete current need (YAGNI/JIT). Fixes land one at a time, verified between each. Errors are prevented at design time through type systems and validation layers. New patterns require team consensus before entering the codebase. **Wh