Bjørn Johansen5 min readintermediate
One style guide for everything Claude Code writes
Summary
A detailed walkthrough of forking the nbj‑write‑clearly Claude Code skill to enforce the Google Developer Documentation style guide across all developer‑facing prose (docs, comments, commit messages, review feedback). The fork expands the trigger set, vendors the 70‑page guide offline via a Bun sync script, and adds a layered approach (global CLAUDE.md rules, on‑demand skill, per‑agent preloaded…
- Google’s developer documentation style guide can be turned into a reusable Claude Code skill.
- The original skill only handled docs; the fork expands coverage to code comments, commit messages, review feedback, changelogs, etc.
- Offline copies of the 70‑page guide avoid lossy summarization and network latency; a simple `bun run sync‑offline` script refreshes the snapshots.
- Layered enforcement: a minimal rule set in `CLAUDE.md` for every session, the full skill loads on demand, and agents can preload the skill via front‑matter.
Consistent, concise technical prose reduces ambiguity in code reviews, commit histories, and documentation, improving developer velocity and reducing miscommunication. Embedding the style guide directly into the LLM workflow ensures the guidance is applied uniformly without relying on network calls…
6/10
