A Chrome extension needs a clear and easy to use interface. This guide helps you build popups, side panels, and other UI parts. It covers Manifest V3 rules and best practices.
You will find tips for making your extension accessible and keyboard friendly. The guide also shows how to handle loading states and errors. Anyone creating a browser extension can benefit from these rules.
There are 42 rules split into eight categories. Each one is ranked by how important it is. This makes it simple to focus on the most critical parts first.
Global
mkdir -p ~/.claude/skills/chrome-extension-uiProject
mkdir -p .claude/skills/chrome-extension-uiSource Repository
Frontend Designanthropics/skills
Create striking frontend interfaces with bold design and polished code every time
Vercel React Best Practicesvercel-labs/agent-skills
Optimize React and Next.js apps using proven Vercel performance guidelines
Design Taste Frontendleonxlnx/taste-skill
Enforce premium frontend design with metric-based rules and smart component architecture
Vercel Composition Patternsvercel-labs/agent-skills
Clean React components with composition instead of boolean props
Shadcnshadcn/ui
Manage shadcn UI components easily with CLI commands and clear styling rules
Impeccablepbakaus/impeccable
Polish your frontend interfaces with expert design critique and code
Minimalist Uileonxlnx/taste-skill
Build warm minimal web interfaces with editorial typography and flat bento grids
Industrial Brutalist Uileonxlnx/taste-skill
Raw mechanical UIs fusing Swiss print with military terminal aesthetics and high data density