But if you feel writing should have standards, then you might to need to write those standards yourself. Which is not a bad idea at all - you just need to approach it as a journey of discovery - which standards are helpfull, and which are not. It's not something that can be got exactly right from the beginning.
Github's issue reporting functionality fills in automatically content hints.
Maybe you could start from headline template with content hints, and evolve that as need arises?
Some standards come to mind: Microsoft's Style Guide (https://docs.microsoft.com/en-us/style-guide/welcome/) and Strunk&White's "Elements of style"
But if you feel writing should have standards, then you might to need to write those standards yourself. Which is not a bad idea at all - you just need to approach it as a journey of discovery - which standards are helpfull, and which are not. It's not something that can be got exactly right from the beginning.
Github's issue reporting functionality fills in automatically content hints.
Maybe you could start from headline template with content hints, and evolve that as need arises?