Google developer style as default house style
mai · confidence high · status active
tags: content communication style humanizer
Context
On 19 August 2026 Dwayne asked MAI to build a skill from the Google developer documentation style guide and use it for all communication. A standing humanizer rule already covers Dwayne-facing replies, dwaynehelena.com, and the Tech Leaders Brief.
Decision
Use google-developer-style as the default writing style for all written communication. Apply it before humanizer. Project-specific rules still win: Telegram compact, title-first, no invented facts, and Dwayne's direct engineering voice.
The live skill is ~/.openclaw/workspace/skills/google-developer-style/SKILL.md (applied proposal google-developer-style-20260818-90400a0285). The standing preference is in ~/.openclaw/workspace/USER.md.
Why
One sourced style guide keeps replies, docs, and authored content consistent. Google's own precedence puts project-specific style first, so compact Telegram and humanizer do not get overwritten.
Rollback
Dwayne can revoke the standing request or reject the proposal. Supersede this decision rather than deleting it.
Log
- 2026-08-19 09:07 GMT+10: Dwayne replied
apply. Proposal applied. Frontmatter valid. Word list present., mai. - 2026-08-19: decision recorded from the Telegram request. Proposal created and scanned clean. Workshop apply expired without a decision.