Comprehensive UX/UI design guide for Chrome Extensions, optimized for Manifest V3. Contains 42 rules across 8 categories, prioritized by impact to guide extension UI development and code review.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionchrome-extension-uiExecute the skills CLI command in your project's root directory to begin installation:
Fetches chrome-extension-ui from pproenca/dot-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate chrome-extension-ui. Access via /chrome-extension-ui in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
95
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
95
stars
Comprehensive UX/UI design guide for Chrome Extensions, optimized for Manifest V3. Contains 42 rules across 8 categories, prioritized by impact to guide extension UI development and code review.
Reference these guidelines when:
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Component Selection | CRITICAL | comp- |
| 2 | Accessibility & Navigation | CRITICAL | access- |
| 3 | Popup Design | HIGH | popup- |
| 4 | Side Panel UX | HIGH | panel- |
| 5 | Content Script UI | MEDIUM-HIGH | inject- |
| 6 | Visual Feedback | MEDIUM | feedback- |
| 7 | Options & Settings | MEDIUM | options- |
| 8 | Icons & Branding | LOW-MEDIUM | brand- |
comp-popup-vs-sidepanel - Choose Side Panel for Persistent Taskscomp-content-script-ui - Use Content Scripts for In-Page UIcomp-single-purpose - Design for Single Purposecomp-minimal-permissions - Request Minimal Permissionscomp-action-tooltip - Provide Descriptive Action Tooltipsaccess-keyboard-navigation - Enable Complete Keyboard Navigationaccess-focus-visible - Maintain Visible Focus Indicatorsaccess-aria-labels - Use ARIA Labels for Icon-Only Buttonsaccess-color-contrast - Ensure Sufficient Color Contrastaccess-focus-trap - Avoid Keyboard Focus Trapsaccess-semantic-html - Use Semantic HTML Elementspopup-size-constraints - Design Within Popup Size Limitspopup-instant-render - Render Popup Content Instantlypopup-primary-action - Make the Primary Action Obviouspopup-auto-close - Handle Popup Auto-Close Gracefullypopup-external-js - Keep JavaScript in External Filespopup-dynamic-switch - Use Dynamic Popups for State-Based UIpanel-non-distracting - Design Non-Distracting Side Panelspanel-tab-vs-window - Choose Tab-Specific vs Window-Wide Panelspanel-responsive-width - Design for Variable Panel Widthspanel-page-context - Sync Panel Content with Page Contextpanel-lazy-sections - Lazy Load Panel Sectionsinject-shadow-dom - Use Shadow DOM for Style Isolationinject-z-index - Use Maximum Z-Index for Overlaysinject-document-ready - Inject UI After DOM Readyinject-unique-ids - Use Unique IDs to Prevent Conflictsinject-cleanup - Clean Up Injected Elements on Removalfeedback-loading-states - Show Loading States for Async Operationsfeedback-error-messages - Write Actionable Error Messagesfeedback-badge-status - Use Badge for At-a-Glance Statusfeedback-success-confirmation - Confirm Successful Actionsfeedback-notifications - Use Notifications Sparinglyfeedback-progress-indication - Show Progress for Long Operationsoptions-embedded-page - Use Embedded Options for Simple Settingsoptions-sync-storage - Sync Settings Across Devicesoptions-auto-save - Auto-Save Settings on Changeoptions-sensible-defaults - Provide Sensible Default Settingsbrand-icon-sizes - Provide All Required Icon Sizesbrand-distinctive-icon - Design a Distinctive Toolbar Iconbrand-badge-text - Keep Badge Text Under 4 Charactersbrand-consistent-styling - Maintain Consistent Visual Stylebrand-web-store-assets - Create Quality Web Store AssetsRead individual reference files for detailed explanations and code examples:
| File | Description |
|---|---|
| references/_sections.md | Category definitions and ordering |
| assets/templates/_template.md | Template for new rules |
| metadata.json | Version and reference information |
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
pproenca/dot-skills
pproenca/dot-skills
anthropics/claude-code
mblode/agent-skills
github/awesome-copilot
sickn33/antigravity-awesome-skills
chrome-extension-ui reduced setup friction for our internal harness; good balance of opinion and flexibility.
chrome-extension-ui has been reliable in day-to-day use. Documentation quality is above average for community skills.
chrome-extension-ui fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added chrome-extension-ui from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
chrome-extension-ui fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Keeps context tight: chrome-extension-ui is the kind of skill you can hand to a new teammate without a long onboarding doc.
chrome-extension-ui has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in chrome-extension-ui — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: chrome-extension-ui is focused, and the summary matches what you get after install.
I recommend chrome-extension-ui for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 34