update writing style rules: avoid all dashes, prefer periods & ampersands

CLAUDE.md

@@ -136,13 +136,12 @@ Git operations can be destructive to uncommitted work. Always preserve user's wo
 - Example: "disrupt wheels & foster open collaboration" not "disrupt wheels and foster open collaboration"
 - This creates a more casual, punchy writing style that matches the brand voice
 
-**Grammar: NEVER use em-dashes (—)**
-- Do not use em-dashes in any writing (posts, cover letters, documentation)
-- Instead of em-dashes, prefer splitting into two separate sentences
-- Alternative: use commas or periods for sentence breaks
-- Example to avoid: "The opportunity to work—learning from experienced operators while contributing—combines technical challenge"
-- Correct approach: "The opportunity to work with experienced operators while contributing combines technical challenge." Or split into two sentences: "The opportunity to work combines technical challenge. Learning from experienced operators while contributing enhances the experience."
-- This creates clearer, more direct writing
+**Grammar: Avoid dashes (em-dashes —, en-dashes –, hyphens used as dashes)**
+- Do not use em-dashes or en-dashes in any writing (posts, cover letters, documentation)
+- Hyphens only for compound words (e.g., "open-source"), never as sentence punctuation
+- Prefer full stop periods. Split into two sentences instead of connecting with dashes
+- Commas work too, but periods stay preferred
+- Only use a dash if it truly makes more sense than a period or comma
 
 **Grammar: Avoid "the" in posts**
 - Never use "the" when "a" works instead