When you write code or update a project, you need to make sure it follows the plan. The plan is often written in special documents called specs. This skill helps you compare your work against those specs. It finds any differences between what was promised and what was built.
You set up specs for things like product features, security rules, or technical design. The skill reads the spec documents and the actual code changes. It lists every place where the code does not match the spec. Then it asks you what to do. You can fix the code to match the spec or update the spec to match the code.
This skill saves you from missing important details. It makes sure everyone agrees on what the final result should be. Teams that use clear specs benefit the most from this careful check.
Global
mkdir -p ~/.claude/skills/validate-changes-match-specsProject
mkdir -p .claude/skills/validate-changes-match-specsSource Repository
Web Design Guidelinesvercel-labs/agent-skills
Review your UI code for compliance with web interface guidelines
Improve Codebase Architecturemattpocock/skills
Scan your codebase for architecture improvements with visual reports and pick one to refactor
Zoom Outmattpocock/skills
Get a big picture view of your code with a simple map of modules and callers
Caveman Reviewjuliusbrussee/caveman
Ultra-compressed one-line code review comments that cut noise
Requesting Code Reviewobra/superpowers
Catch code issues early with focused automated reviews before every merge
Receiving Code Reviewobra/superpowers
Think first, then code. Verify feedback before making changes. Stay objective
Auditpbakaus/impeccable
Audit your code for accessibility performance theming and anti-patterns
Request Refactor Planmattpocock/skills
Plan safe code refactors with tiny commits and clear GitHub issues