# Google Markdown Style > Applies Google Markdown style for formatting, naming, and conventions. Use when writing or reviewing Markdown, .md files, README docs, or technical writing. - Skill: `peterish8/google-markdown-style` (Agent Skill) - Install (CLI): `npx skillmds@latest add peterish8/google-markdown-style` - Raw SKILL.md: https://api.skillmd.com/api/skills/peterish8/google-markdown-style/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Docs & Writing - Author: peterish8 (https://skillmd.com/u/peterish8) - Updated: 2026-09-21 - Page: https://skillmd.com/skills/peterish8/google-markdown-style --- # Google Markdown Style (Quick Reference) Source: [https://google.github.io/styleguide/docguide/style.html](https://google.github.io/styleguide/docguide/style.html) ## When to load the detailed skill Read [google-markdown-style-detailed](../google-markdown-style-detailed/SKILL.md) when you need: - Section-by-section rules, examples, or edge cases - PR review with non-trivial style questions - Resolving conflicts between local habits and Google style The detailed skill is linked here so agents can load it automatically alongside this quick reference. ## Core rules - Prefer readable plain Markdown over HTML. - One H1 per document; use ATX headings (`#`). - 80-character line limit for prose; fenced code blocks with language tags. - Use reference links for long URLs; define references after first use. - Capitalize product names correctly; sentence case for headings unless title case is established. - Delete stale docs frequently; small accurate docs beat sprawling outdated ones. ## Quick checklist - Match Google Markdown naming and formatting conventions - Keep code readable; prefer consistency within the file and package - Run language-appropriate linters/formatters when available - Document non-obvious behavior with brief, accurate comments - Defer to the official guide when this skill is silent ## Official guide