This guide helps you write code that is correct, safe, and easy to maintain. Correctness comes first. A crash is better than corrupt data. Always handle errors and check assumptions with assertions.
For Rust programmers, the skill teaches patterns like making illegal states unrepresentable and using enums instead of strings. It also shows how to write clear comments that explain why something is done, not just what the code does.
Over-engineering is avoided by only adding what is needed. The skill covers index mutations, understanding the async IO model, and cleaning up unused code. It is useful for anyone who wants to build reliable software.
Global
mkdir -p ~/.claude/skills/code-qualityProject
mkdir -p .claude/skills/code-qualitySource 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