create `standard-readme` layout

I’m going to major standardizing and my flow would soon be totally automated, crazy and awesome. I’m using the “standards” - standard, semantic releasing with standard-version (which is almost the same as semantic-release), and wanna have standard readmes too.

offtopic: What I imagine:

1. generate-repo - creates repo on github, labels, sync travis/coveralls site? etc, init and possibly first commit
2. generate project - creates any templates
3. writing the modules
4. verb
5. git add --all -> git cz (commit using commitizen) -> (standard-version, not always), git push (–follow-tags, if standard-version), (npm publish, if standard-version)

[jonschlinkert]

I just looked. I have zero interest in supporting that. I tried commenting in the one discussion and the response(s) to my comment were childish, and it seemed like they were actively discouraging others from commenting. Someone even commented that they didn’t like my style of readmes. That’s fine, but given that I have more of them, more experience writing them, and more tools for creating them than any other GitHub user to my knowledge, I would have at least hoped to be a part of the discussion.

I even commented that my decisions are based on data, and someone had a problem with that. It was lame. I have 300 million downloads a month to guide my decisions, not to mention the clicks that we track. It’s absurd for someone to not want insight from that.

[jonschlinkert]

so it also would be great if you fix them a bit to be compliant.

How about if we fix the spec instead