Migrate existing browser extension projects from WXT, Plasmo, Extension.js, or no-framework (vanilla) to the Addfox framework. Use when the user wants to migrate an extension to Addfox or asks about converting from WXT/Plasmo/Extension.js/vanilla to addfox.
Use this skill when:
Migrate WXT, Plasmo, Extension.js, or vanilla (no-framework) browser extension projects to Addfox with minimal behavior change and clear verification.
@addfox/core behavior as source of truth.addfox dev / addfox build succeed.Detect source framework
package.json dependencies and config files:wxt.config.ts, wxt.config.js, wxt.config.mjs, dependency wxtpackage.json with plasmo dependency, package.json "manifest" or plasmo-specific structure@crxjs/vite-plugin or similarmanifest.json + ad-hoc build or no buildApply framework-specific migration
Validate
addfox dev and confirm extension loads in browser.addfox build and confirm .addfox/extension.zip (or configured output) is produced.Cleanup and summarize
addfox.config.ts (or .js/.mjs) at project root; defineConfig from addfox.app/ (or configured appDir); entry discovery or explicit entry in config.manifest_version: 3; entry paths use framework placeholders where needed (e.g. [addfox.content] for content scripts).addfox (and optionally webextension-polyfill for cross-browser); remove WXT/Plasmo/CRXJS-specific packages after migration is verified.