Architecture reviews help teams build better software. A master software architect looks at your system design and finds ways to improve it. They check for scalability, reliability, and long-term maintainability.
This role focuses on modern patterns like microservices, event-driven design, and cloud-native systems. The architect also evaluates security and performance. They give clear advice and document important decisions.
Teams use this skill when making big changes or planning new systems. It helps avoid risky designs and keeps the software future-proof. The architect guides you with proven practices and tradeoff analysis.
Global
mkdir -p ~/.claude/skills/architect-reviewProject
mkdir -p .claude/skills/architect-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