spacholski1225/cc-config

technical-blog-post-generator

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

code-archaeology

Systematic techniques for reading and understanding unfamiliar legacy code without documentation

dependency-mapping

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

writing-plans

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

reverse-engineering-documentation

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

gardening-skills-wiki

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

writing-skills

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

characterization-testing

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

strangler-fig-pattern

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

getting-started-with-agent-skills

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