I can specify some kind of naming convention for all of the other types but not fields and constants.
A selection from any of the usual ones would be fine
camelCase
_underscoreCamelCase (preferred and the convention I see most often as it disambiguates between arguments and locals)
PascalCase
snake_case
ALL_UPPER
etc…
Fields and constants would not be held to the same rule, each would have its own. Like how the Java rules are done. Just because MSFT couldnt agree well enough to publish a guideline doesnt mean that other teams couldnt agree.