local_vimrc VS lh-vim-lib

Other approaches are available as well. For instance, autocommands in the .vimrc are possible as well, but every time you move around that directory you'd have to update the autocommand.

Regarding project management, .exrc is enough as long we're working on simple project where everything is in the same directory. On real project I've ended up needing and writing much, much more.

buffer wise, from a local vimrc for instance, with let b:tag_options = { 'no_auto': 0}

snake is one of the possible naming policies. Several are hard-coded: snake, UpperCamelCase, lowerCamelCase, SCREAMING_SNAKE_CASE. Other can be configured (in local vimrc plugins for instance), and then used where we can expect it to make sense: member variables, local variables, static variables, types, getter...

I'm not sure about the new plugin advertised, but 'exrc' is restricted to the current directory. Its settings won't be applied to subdirectories -- unlike to what other localvimrc plugins do

and it seems it depends now on lh-vim-lib (to be able to set dictionaries: :let b:dict.key.subkey.whatever = 42: https://github.com/LucHermitte/lh-vim-lib (install it with your plugin manager)

Note that if it's just for setting a few standard options, editorconfig will be enough for most of us. It won't work if you want to define different mappings, or if you want to change the path to your snippets (actually editorconfig plugin could be hijacked to set vim variables)

here an UI alternative to confirm() and another that implement comboboxes: https://github.com/LucHermitte/lh-vim-lib/blob/master/autoload/lh/ui.vim (the code is very old, but it works search for getchar())

Regarding project management, .exrc is enough as long we're working on simple project where everything is in the same directory. On real project I've ended up needing and writing much, much more.

or in your .editorconfig file (if you have any) as lh-vim-lib also registers an extension to set vim variables from editorconfig file -- it's definitively not meant to be used this way, but well it's possible.

I have things on the same topic in my vimscript library: I provide a queue object into which I register related tasks that cannot be safely parallelized.