create style guide for file formatting

[WesLSmith]

This ticket is a request for style guideliens to be put into the readme while waiting on improved linting functionality from spyglass.

Looking for guidance on newlines, function ordering, tag quoting best practices, and anything else we may need to update in a PR.

[TheAfroOfDoom]

• always have one blank new line at end of file
• no trailing whitespace
• a comment should be on the line above a command iff it is relevant to said command
• trailing backslashes should always have a space before them
• header comments meant to describe a function's purpose should have a double prefix ##