Some code is written to impress other developers instead of solving real problems. This skill helps you spot that kind of code. It looks at codebases, architectures, and pull requests for things that add complexity without helping users.
You might have seen over-engineered systems that use fancy patterns for simple tasks. Or a team choosing a hot new framework when a simpler tool works fine. This skill catches those choices. It calls them vanity engineering.
Use this review to keep your projects simple and focused. It asks what your users actually need. Then it checks if the code matches those needs. If not, it suggests cutting the extra stuff.
Global
mkdir -p ~/.claude/skills/vanity-engineering-reviewProject
mkdir -p .claude/skills/vanity-engineering-reviewSource 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