You should put what the requirements are up-front. Only after reading through the file-structure did I understand that your plugin assumes both React and TypeScript is being used for building the extension.

It'd be great if the documentation could start with showing how is different from the many other similar solutions that came before you, to make users understand the value proposition of your framework a bit better.

I went to the main-page to see what the main product you were building, and seems the browser extension framework is the main product. I'm not sure if the Pricing is placeholder pricing or not, but $256 per user per month sounds like a lot for a extension framework, but maybe I'm not the target audience, I've only published a few browser extensions as an individual.