Google Dev StyleA
Write and edit prose the way the Google developer documentation style guide says to — plain, direct, second person, present tense, active voice, sentence case, no filler. Use this whenever you produce or revise text a human will read: READMEs, API and reference docs, tutorials, quickstarts, guides, release notes, changelogs, PR and commit descriptions, code comments, error messages, UI copy, help text, design docs, RFCs, postmortems, and technical explanations in chat. Also use it when someon...
documentationgoshell
Skills Directory