browser-extension-dev

Plugin browser-extension-dev from marketplace arustydev in aRustyDev/agents. Commands read from the repo's manifest — 1 month ago.

Skills (9)

• browser-store-apis

  Reference for browser extension store APIs for querying extension info, checking compatibility, and tracking submission status

• cross-browser-compatibility

  Browser API differences, polyfills, and feature detection for Firefox, Chrome, Safari, and Edge extensions

• extension-anti-patterns

  Common mistakes, performance pitfalls, and store rejection reasons in browser extension development

• extension-security

  Comprehensive security guide for browser extensions covering CSP, permissions, secure messaging, sandboxing, and threat mitigation

• extension-store-submission

  Complete guides for submitting browser extensions to Chrome Web Store, Firefox Add-ons, Safari App Store, and Edge Add-ons

• manifest-v3-reference

  Complete reference for Manifest V3 browser extension development with cross-browser compatibility and migration guidance

• wasm-architecture-decision

  Decision framework for WebAssembly usage in browser extensions including loading patterns, architecture, and performance considerations

• wasm-extension-integration

  Guide for integrating WebAssembly modules into browser extensions using wasm-pack, wasm-bindgen, and cross-browser loading

• wxt-framework-patterns

  Comprehensive WXT browser extension framework patterns, security hardening rules, and cross-browser configuration

Slash commands (3)

• /browser-extension-dev:add-wasm-module

  Add a WebAssembly module to a browser extension project with Rust scaffolding, wasm-pack build configuration, and cross-browser loading code.

• /browser-extension-dev:create-extension

  Scaffold a new cross-browser extension using WXT framework

• /browser-extension-dev:validate-extension

  Validate browser extension for manifest issues, CSP violations, and cross-browser compatibility

Subagents (4)

• extension-architect

  Design browser extension architecture including component structure, WASM decisions, cross-browser strategy, and manifest configuration

• extension-debugger

  Debug cross-browser extension issues, analyze errors, and suggest compatibility fixes

• store-submission-reviewer

  Pre-review browser extensions for store compliance before submission to Chrome Web Store, Firefox Add-ons, and Safari App Store

• wasm-integration-advisor

  Evaluate WebAssembly suitability for browser extension features and architect module boundaries. Provides data-driven recommendations with performance analysis.

MCP servers (4)

• playwright

  runs: npx -y @playwright/mcp@latest

• puppeteer

  runs: npx -y @modelcontextprotocol/server-puppeteer

• wasm-bindgen

  runs: cargo run --manifest-path ${HOME}/.local/share/mcp/wasm-bindgen-mcp/Cargo.toml -- --target-dir .output/wasm

• browser-store-api

  runs: npx -y @anthropic-ai/mcp-browser-store-api

Hooks (3)

• PostToolUse

  bash -c 'FILE="$TOOL_INPUT_FILE_PATH"; case "$FILE" in */manifest.json) DIR=$(dirname "$FILE"); if command -v web-ext >/dev/null 2>&1; then web-ext lint --source-dir "$DIR" --warnings-as-errors=false

• PostToolUse

  bash -c 'FILE="$TOOL_INPUT_FILE_PATH"; case "$FILE" in */entrypoints/*.ts|*/entrypoints/*.tsx|*/entrypoints/*.js|*/entrypoints/*.jsx) if command -v biome >/dev/null 2>&1; then biome check "$FILE" 2>&1

• PostToolUse

  bash -c 'FILE="$TOOL_INPUT_FILE_PATH"; case "$FILE" in */wasm/*/*.rs) WASM_DIR=$(echo "$FILE" | sed "s|/src/.*||" | sed "s|/tests/.*||"); if [ -f "$WASM_DIR/Cargo.toml" ] && command -v wasm-pack >/dev

Similar plugins