cc-config

Transform markdown notes into engaging technical blog posts for both programmers and non-technical readers

Systematic techniques for reading and understanding unfamiliar legacy code without documentation

Map dependencies and coupling in legacy codebase to understand what breaks when you change something and identify refactoring risks

Create detailed implementation plans with bite-sized tasks for engineers with zero codebase context

Creating documentation from legacy code when none exists, focusing on what future maintainers need to know

Maintain skills wiki health - check links, naming, cross-references, and coverage

TDD for process documentation - test with subagents before writing, iterate until bulletproof

Create tests that describe what legacy code actually does (not what it should do) as safety net before refactoring

Safely replace legacy system piece by piece by building new implementation around it, routing traffic gradually, like a strangler fig tree

Skills for legacy code analysis, explanation, and safe refactoring - mandatory workflows and search tools