From b39633d9d482b6510e5626e0c5441ad211508a6e Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Fri, 12 Jun 2026 18:14:19 -0500 Subject: chore: refresh .claude rules and hooks to rulesets canonical The startup language-bundle sync repaired drift in these rulesets-owned files. Committing them at canonical so future syncs stay no-ops. --- .claude/rules/elisp.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to '.claude/rules/elisp.md') diff --git a/.claude/rules/elisp.md b/.claude/rules/elisp.md index e641058..ea9bdc2 100644 --- a/.claude/rules/elisp.md +++ b/.claude/rules/elisp.md @@ -72,4 +72,4 @@ Then `(require 'foo-config)` in `init.el` (or a config aggregator). - A PostToolUse hook runs `check-parens` and `byte-compile-file` on every `.el` save - If it blocks, read the error — don't retry blindly -- Prefer Write over repeated Edits for nontrivial new code; incremental edits accumulate subtle paren mismatches +- Edit cohesively, then verify parens/byte-compile right away. For nontrivial Elisp, land a function as one complete, coherent change rather than dribbling it in over many tiny partial edits — incremental fragments accumulate subtle paren mismatches. Run the paren-balance and byte-compile checks immediately after editing, whatever editing mechanism the environment uses. -- cgit v1.2.3