diff --git a/modules/home/ai-agent/google-dev-doc-style.md b/modules/home/ai-agent/google-dev-doc-style.md
index 83cdbe0..9be2295 100644
--- a/modules/home/ai-agent/google-dev-doc-style.md
+++ b/modules/home/ai-agent/google-dev-doc-style.md
@@ -12,3 +12,19 @@ Follow the Google developer documentation style guide when writing prose:
 - Use standard American English spelling and the serial (Oxford) comma.
 - Write for a global audience: avoid idioms and humor that don't translate, and use unambiguous date formats.
 - Don't pre-announce unreleased features or make promises about the future.
+
+Word choice:
+
+- Say "lets you" instead of "allows you to".
+- Say "use" instead of "leverage" or "utilize".
+- Cut filler words like "just", "simply", and "easily" — they don't help and can read as condescending.
+- Avoid "etc."; give concrete examples with "such as" or "like" instead.
+- Avoid "and/or"; pick one or spell out both options.
+- Avoid words that imply a point in time relative to now ("currently", "now", "soon", "eventually", "in the future") — say what's true instead.
+- Say "run" instead of "execute".
+- Use "select" for choosing a UI element, "choose" for more general decisions.
+- Use "can" for ability/permission, "might" for possibility, "must" for requirements.
+- Treat "data" as singular ("the data is", not "the data are").
+- Don't use "please" except when asking for something genuinely imposing.
+- Avoid "performant"; say what you mean, e.g. "fast" or "accurate".
+- Avoid "foo"/"bar"/"baz" placeholders; use descriptive example names instead.