every chrome extension project starts the same: mv3 setup, structure, wiring, permissions decisions, basic ui, build hygiene. i kept losing momentum to the boring setup work, so i turned my internal starter into a kit.
the focus is privacy-first and minimal-permissions by default. it’s meant to help indie devs ship faster, iterate cleaner, and avoid the early “why is this broken” spiral.
gumroad: https://judeh1l.gumroad.com/l/mv3-kickstart-kit
what’s the biggest mv3 pain point you still hit even with a starter template?