Hi @khanxmetu, thanks for raising this.
My only real concern here is whether the command palette is sufficiently stable to get tied to Django’s long-release cycle and stability guarantees? That is, are we confident that we’re not going to need to make numerous/rapid adjustments to it once we get people using it? The answer might be Yes there, but how battle tested is this? (I don’t know, hence asking.)
If we’re not confident then one approach would be to promote the package but still keep it separate, in order to allow continued iteration.
One idea there would be pip extras. This would be new for us, but I think we’ll likely need to do something similar for the db-tasks backend, which faces the same challenge. What goes for one could go for all. In general, it would be nice to have some story here, even if pip extras isn’t it.
Additionally, we want a combobox widget …
Can I point to this: Usage Guide - django-tomselect documentation by @jacklinke
… yet to decide which shortcuts should be set as default …
I’m imagining some config file? 
(TOML or something?)
I’d offer a small set of defaults and a how-to on adding your own.
The jump to model example is probably the most obvious.
But those points are secondary to the stability question.