Coding standards are good. This important in software projects with more than one member to make sure that source code is easily readable by any member. But it is a boring task to put together a coding standard document, even if there are many examples available on the net.
But here is a saviour. Just click on this link and follow a few instructions and a coding standard document is generated for your project.
The generated coding standard document will contain only purely stylistic rules such as names and indentations, usage of goto etc.
Many coding standard documents are littered with useful guidelines on how to avoid common pitfalls. These guidelines are obvious and are better described in various books such as Effective C++ and Effective Java. Such guidelines should be followed in any project and should not need to be mentioned in a coding standard document. Instead, a coding standard document shall describe how things are written in each project, laying the law to avoid time consuming debates on how many columns to indent within a brace block.