diff --git a/modules/home/ai-agent/default.nix b/modules/home/ai-agent/default.nix
index ea2e7ce..94ec1ef 100644
--- a/modules/home/ai-agent/default.nix
+++ b/modules/home/ai-agent/default.nix
@@ -36,7 +36,7 @@ let
           hooks = [
             {
               type = "command";
-              command = "cat ${./google-dev-doc-style.md}";
+              command = "cat ${./style.md}";
             }
           ];
         }
diff --git a/modules/home/ai-agent/google-dev-doc-style.md b/modules/home/ai-agent/style.md
similarity index 74%
rename from modules/home/ai-agent/google-dev-doc-style.md
rename to modules/home/ai-agent/style.md
index 9be2295..d45ce22 100644
--- a/modules/home/ai-agent/google-dev-doc-style.md
+++ b/modules/home/ai-agent/style.md
@@ -28,3 +28,9 @@ Word choice:
 - 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.
+
+Writing code:
+
+- Be lazy. Write the smallest amount of code that solves the problem — don't add abstractions, options, or handling for cases that don't exist yet.
+- Look for and reuse existing abstractions, helpers, and patterns in the codebase before writing new ones.
+- Never write code or comments that depend on this conversation to be understood. A comment is for someone reading the file in three months with no memory of this chat — it must not reference "the fix", "as discussed", "the bug we found", issue numbers, or anything else that only makes sense in context. If a comment needs the conversation to make sense, delete or rewrite it.