Before making any changes to your code, you need to see the big picture. This tool helps you find every file that matters for your task. It maps out dependencies, tests, and similar patterns so you know exactly what to touch.
Think of it as a checklist for code changes. You search your project for related files. You note which ones need updates and which ones might break. You also look at existing patterns to follow. This way you avoid surprises and keep your codebase healthy.
The result is a simple table that shows what to modify, what depends on it, and what tests to check. It also flags risks like breaking changes or database updates. Once you review this map, you are ready to code safely.
Global
mkdir -p ~/.claude/skills/context-mapProject
mkdir -p .claude/skills/context-mapSource Repository
Improve Codebase Architecturemattpocock/skills
Scan your codebase for architecture improvements with visual reports and pick one to refactor
Web Design Guidelinesvercel-labs/agent-skills
Review your UI code for compliance with web interface guidelines
Caveman Reviewjuliusbrussee/caveman
Ultra-compressed one-line code review comments that cut noise
Zoom Outmattpocock/skills
Get a big picture view of your code with a simple map of modules and callers
Codebase Designmattpocock/skills
Create deep modules with tiny interfaces and lots of hidden logic for testability
Requesting Code Reviewobra/superpowers
Catch code issues early with focused automated reviews before every merge
Request Refactor Planmattpocock/skills
Plan safe code refactors with tiny commits and clear GitHub issues
Receiving Code Reviewobra/superpowers
Think first, then code. Verify feedback before making changes. Stay objective