Addfox Best Practices

Use this skill when working on Addfox extension architecture, configuration, and runtime integration.

When to use

Use this skill when you need to:

• Configure addfox.config.ts (manifest, entry, plugins, rsbuild, appDir, outDir)
• Design entry strategy for background, content, popup, options, and custom entries
• Decide permissions and host patterns for least-privilege access
• Target both Chromium and Firefox with browser-specific manifest sections
• Implement content UI and messaging between extension contexts

Quick references

Best-practice checklist

• Prefer file-based reserved entries first; use entry only when customization is required.
• Keep manifest source paths clear and let Addfox resolve build output paths.
• Minimize permissions and host scope; avoid <all_urls> unless absolutely necessary.
• Keep background logic event-driven for MV3 service worker lifecycle.
• Use typed message contracts across contexts to reduce runtime mismatch.

Related docs

• reference.md
• rules/entry.md
• rules/manifest-fields.md