Chrome extensions run in the browser and can modify web pages. They use service workers and content scripts to work. This guide gives you performance and code quality rules for Manifest V3.
You can use these rules when writing new code or reviewing old code. They cover message passing, storage APIs, and testing. Following them makes your extension faster and more reliable.
Global
mkdir -p ~/.claude/skills/chrome-extensionProject
mkdir -p .claude/skills/chrome-extensionSource 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