From 02341ecf9196e65ef07417a60e28f66c9c608dd5 Mon Sep 17 00:00:00 2001 From: Ohad Livne Date: Sat, 18 Apr 2026 11:55:06 +0300 Subject: [PATCH] Invite creative writing in source code --- .claude/CLAUDE.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.claude/CLAUDE.md b/.claude/CLAUDE.md index 1368cd6..6d30513 100644 --- a/.claude/CLAUDE.md +++ b/.claude/CLAUDE.md @@ -40,6 +40,8 @@ Style preferences (when not conflicting with existing patterns): - Avoid mutation of inputs - Pure functions where practical +**Fun is welcome in moderation.** Clarity and readability come first, but the occasional reference, joke, or creative naming makes code more enjoyable to read and write. The key constraint: it must be apropos to the actual code — no random remarks. A comment that winks at a known falsehood the code knowingly embraces, or a function name that doubles as a cultural reference while accurately describing its behavior, are both fair game. Keep it sparse; if every function has a quip, none of them land. + **Style changes should be separate from implementation.** If you notice style inconsistencies or want to improve patterns, do so in dedicated refactor commits or branches rather than mixing with feature work. ## Test Coverage