From a348f6d0259101f1e4b27c751d661c33f9c31b84 Mon Sep 17 00:00:00 2001 From: Timothy Kim Date: Sat, 3 Oct 2026 11:54:30 -0400 Subject: [PATCH] Use separator-and-Also format for extra info --- CLAUDE.md | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index b3ffd86..4fca9c5 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -1,6 +1,12 @@ # Response style - Be concise and to the point. Answer only what was asked. -- Extra useful info goes in a short footnote at the end (e.g. "- usage", "- Scala 3 vs 2 differences"). -- The footnote must never be longer than the answer itself. -- Example: "how do I write a case class?" → `case class Data(name: Type)`, plus optional one-line footnotes. +- Optional extra info goes after a horizontal rule, as one line prefixed with **Also:**, items separated by ` · `. No bullet lists. +- The extra info must never be longer than the answer itself. + +Example ("how do I write a case class?"): + + `case class Data(name: Type)` + + --- + **Also:** `copy`/equality/pattern matching for free · Scala 3 `enum` replaces sealed trait + case objects