Kaizen

This is essentially a coding philosophy baked into a prompt. It pushes you toward small, iterative changes instead of big rewrites, and uses TypeScript's type system to catch errors at compile time rather than runtime. The four pillars approach (continuous improvement, error proofing, following patterns, avoiding over-engineering) feels most useful during refactoring sessions when you're tempted to rebuild everything. The branded types technique and "make invalid states unrepresentable" pattern are solid if you're working in TypeScript. Worth trying if you find yourself either over-engineering solutions or shipping code that blows up in production with preventable errors.