wxt-browser-extensions▌
pproenca/dot-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Comprehensive performance optimization guide for WXT browser extension development. Contains 49 rules across 8 categories, prioritized by impact to guide automated refactoring and code generation. Updated for WXT v0.20+.
Community WXT Browser Extensions Best Practices
Comprehensive performance optimization guide for WXT browser extension development. Contains 49 rules across 8 categories, prioritized by impact to guide automated refactoring and code generation. Updated for WXT v0.20+.
When to Apply
Reference these guidelines when:
- Writing new WXT browser extension code
- Implementing service worker background scripts
- Injecting content scripts into web pages
- Setting up messaging between extension contexts
- Configuring manifest permissions and resources
Rule Categories by Priority
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Service Worker Lifecycle | CRITICAL | svc- |
| 2 | Content Script Injection | CRITICAL | inject- |
| 3 | Messaging Architecture | HIGH | msg- |
| 4 | Storage Patterns | HIGH | store- |
| 5 | Bundle Optimization | MEDIUM-HIGH | bundle- |
| 6 | Manifest Configuration | MEDIUM | manifest- |
| 7 | UI Performance | MEDIUM | ui- |
| 8 | TypeScript Patterns | LOW-MEDIUM | ts- |
Quick Reference
1. Service Worker Lifecycle (CRITICAL)
svc-register-listeners-synchronously- Register listeners synchronously to prevent missed eventssvc-avoid-global-state- Use storage instead of in-memory statesvc-keep-alive-patterns- Keep service worker alive for long operationssvc-handle-install-update- Handle install and update lifecycle eventssvc-offscreen-documents- Use offscreen documents for DOM operationssvc-declarative-net-request- Use declarative rules for network blocking
2. Content Script Injection (CRITICAL)
inject-use-main-function- Place runtime code inside main() functioninject-choose-correct-world- Select ISOLATED or MAIN world appropriatelyinject-run-at-timing- Configure appropriate runAt timinginject-use-ctx-invalidated- Handle context invalidation on updateinject-dynamic-registration- Use runtime registration for conditional injectioninject-all-frames- Configure allFrames for iframe handlinginject-spa-navigation- Handle SPA navigation with wxt:locationchange
3. Messaging Architecture (HIGH)
msg-type-safe-messaging- Use @webext-core/messaging for type-safe protocolsmsg-return-true-for-async- Return true for async message handlers (raw API)msg-use-tabs-sendmessage- Use tabs.sendMessage for content scriptsmsg-use-ports-for-streams- Use ports for streaming communicationmsg-handle-no-receiver- Handle missing message receiversmsg-avoid-circular-messages- Prevent circular message loops
4. Storage Patterns (HIGH)
store-use-define-item- Use storage.defineItem for type-safe accessstore-choose-storage-area- Select appropriate storage areastore-batch-operations- Group related data into single defineItemstore-watch-for-changes- Use watch() for reactive updatesstore-handle-quota-errors- Handle storage quota errorsstore-versioned-migrations- Use versioning for schema migrations
5. Bundle Optimization (MEDIUM-HIGH)
bundle-split-entrypoints- Split code by entrypointbundle-analyze-size- Analyze and monitor bundle sizebundle-tree-shake-icons- Use direct imports for icon librariesbundle-externalize-wasm- Load WASM dynamicallybundle-minify-content-scripts- Minimize content script size
6. Manifest Configuration (MEDIUM)
manifest-minimal-permissions- Request minimal permissionsmanifest-use-optional-permissions- Use optional permissions progressivelymanifest-web-accessible-resources- Scope web accessible resourcesmanifest-content-security-policy- Configure CSP correctlymanifest-cross-browser-compatibility- Support multiple browsers
7. UI Performance (MEDIUM)
ui-use-shadow-dom- Use Shadow DOM for injected UIui-defer-rendering- Defer popup rendering until neededui-cleanup-on-unmount- Clean up UI on unmountui-sidepanel-persistence- Preserve sidepanel stateui-position-fixed-iframe- Use iframe for complex UIui-avoid-layout-thrashing- Batch DOM reads and writes
8. TypeScript Patterns (LOW-MEDIUM)
ts-use-imports-module- Use #imports virtual module and auto-importsts-use-browser-not-chrome- Use browser namespace over chromets-type-entrypoint-options- Type entrypoint options explicitlyts-augment-browser-types- Augment types for missing APIsts-strict-null-checks- Enable strict null checksts-import-meta-env- Use import.meta for build infots-avoid-any- Avoid any type in handlersts-path-aliases- Use path aliases for imports
How to Use
Read individual reference files for detailed explanations and code examples:
- Section definitions - Category structure and impact levels
- Rule template - Template for adding new rules
Reference Files
| File | Description |
|---|---|
| references/_sections.md | Category definitions and ordering |
| assets/templates/_template.md | Template for new rules |
| metadata.json | Version and reference information |
How to use wxt-browser-extensions on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add wxt-browser-extensions
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches wxt-browser-extensions from GitHub repository pproenca/dot-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate wxt-browser-extensions. Access the skill through slash commands (e.g., /wxt-browser-extensions) or your agent's skill management interface.
Security & Verification Notice
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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.4★★★★★51 reviews- ★★★★★Kaira Iyer· Dec 24, 2024
wxt-browser-extensions has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Advait Thomas· Dec 24, 2024
wxt-browser-extensions reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Zara Rahman· Dec 16, 2024
Registry listing for wxt-browser-extensions matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Dhruvi Jain· Dec 4, 2024
wxt-browser-extensions fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Oshnikdeep· Nov 23, 2024
Registry listing for wxt-browser-extensions matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Anika Ghosh· Nov 19, 2024
Keeps context tight: wxt-browser-extensions is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Advait Mensah· Nov 15, 2024
We added wxt-browser-extensions from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Anika Thomas· Nov 7, 2024
wxt-browser-extensions fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Tariq Diallo· Oct 26, 2024
We added wxt-browser-extensions from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Ganesh Mohane· Oct 14, 2024
wxt-browser-extensions reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 51