migrate-to-addfox
Migrate to Addfox
Use this skill when moving an existing extension codebase to Addfox.
When to use
- Migrating from
wxt.config.tstoaddfox.config.ts - Migrating from Plasmo
contents/,popup.tsx,options.tsx - Migrating from Vite + custom manifest workflows
- Porting entry layout into Addfox
app/reserved folders
Migration workflow
- Keep behavior first, refactor later.
- Create
addfox.config.tswith minimal working manifest. - Map source entries to
app/background,app/content,app/popup,app/options. - Run
addfox buildafter each major step. - Validate extension loading in browser before optimization.
More from addfox/skills
addfox-best-practices
Best practices for building browser extensions with the Addfox framework. Use when developing extensions with Addfox, configuring manifest/entry/permissions, or when discussing MV3, cross-browser support, framework/styling choices, messaging, and content UI injection.
21addfox-debugging
Debug Addfox build and runtime issues, including terminal failures, manifest errors, extension loading issues, and context messaging problems.
18extension-functions-best-practices
Best practices for implementing browser extension features across 13 categories. Reference this skill when developing video, audio, image, translation, download, userscript, AI (including Chrome built-in AI / Gemini Nano), ad-blocker, theme, email, game, password manager, or Web3 wallet features.
18addfox-testing
Test Addfox extensions with Rstest for unit/component tests and Playwright for end-to-end extension loading.
17convert-web-pages-to-browser-extensions
Convert any frontend webpage into a browser extension entry page with an HTML entry. Supports popup, options, sidepanel, devtools, newtab, bookmarks override, history override, and custom entries. Use when the user asks to migrate or adapt an existing web page into extension UI.
7