I packaged my privacy-first MV3 Chrome extension starter kit so I stop rebuilding the same foundation

I build Chrome extensions and got sick of repeating the same setup every time: MV3 structure, popup wiring, storage/messaging patterns, permissions decisions, options page, then release checklist stuff.

So I made a MV3 Extension Kickstart Kit that’s meant to stay clean as the project grows.

What you get

MV3 templates (starter structures you can actually ship from)

Settings/options foundation + storage helpers

Messaging patterns that don’t turn into spaghetti

Web Store release checklist + basic docs to move faster

Gumroad:
https://judeh1l.gumroad.com/l/mv3-kickstart-kit

Question for other extension devs: what’s the most annoying MV3 setup step you keep redoing? If I add one more module, should it be onboarding, permissions UX, or build/release automation?