From 5e554baceddef3f54cd4b808833f2e28e64143c2 Mon Sep 17 00:00:00 2001
From: 230238001 <15151850021@126.com>
Date: Sun, 3 May 2026 14:40:25 +0800
Subject: [PATCH] Replace CLAUDE.md with andrej-karpathy-skills template

Adopt the high-star GitHub CLAUDE.md behavioral guidelines:
- Think Before Coding: surface assumptions and tradeoffs
- Simplicity First: minimum code, no speculative additions
- Surgical Changes: touch only what's needed
- Goal-Driven Execution: define verifiable success criteria
---
 CLAUDE.md | 70 ++++++++++++++++++++++++++++++++++++++++++++++---------
 1 file changed, 59 insertions(+), 11 deletions(-)

diff --git a/CLAUDE.md b/CLAUDE.md
index 95c8394..ca1043e 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -1,17 +1,65 @@
-> 本文件仅保留高优先级、易混淆、跨会话必须一致的约束。
-> 本文件必须极精简，占用大模型注意力视为失效。
+# CLAUDE.md
 
-## 项目一句话
+Behavioral guidelines to reduce common LLM coding mistakes. Merge with project-specific instructions as needed.
 
-Rhino 8 C# 插件（.rhp），管理 Block 的 UserString 属性，支持 XML 模板导入。
+**Tradeoff:** These guidelines bias toward caution over speed. For trivial tasks, use judgment.
 
-## 自动化约定
+## 1. Think Before Coding
 
-- 禁止自行 commit / push git，用户下达指令再执行
-- 完成任务后清理临时文件
+**Don't assume. Don't hide confusion. Surface tradeoffs.**
 
-## 文档入口
+Before implementing:
+- State your assumptions explicitly. If uncertain, ask.
+- If multiple interpretations exist, present them - don't pick silently.
+- If a simpler approach exists, say so. Push back when warranted.
+- If something is unclear, stop. Name what's confusing. Ask.
 
-- PLAN.md：待办事项
-- CHANGELOG.md：版本记录
-- CLAUDE.md：仅包含本文件（不要混入项目说明）
\ No newline at end of file
+## 2. Simplicity First
+
+**Minimum code that solves the problem. Nothing speculative.**
+
+- No features beyond what was asked.
+- No abstractions for single-use code.
+- No "flexibility" or "configurability" that wasn't requested.
+- No error handling for impossible scenarios.
+- If you write 200 lines and it could be 50, rewrite it.
+
+Ask yourself: "Would a senior engineer say this is overcomplicated?" If yes, simplify.
+
+## 3. Surgical Changes
+
+**Touch only what you must. Clean up only your own mess.**
+
+When editing existing code:
+- Don't "improve" adjacent code, comments, or formatting.
+- Don't refactor things that aren't broken.
+- Match existing style, even if you'd do it differently.
+- If you notice unrelated dead code, mention it - don't delete it.
+
+When your changes create orphans:
+- Remove imports/variables/functions that YOUR changes made unused.
+- Don't remove pre-existing dead code unless asked.
+
+The test: Every changed line should trace directly to the user's request.
+
+## 4. Goal-Driven Execution
+
+**Define success criteria. Loop until verified.**
+
+Transform tasks into verifiable goals:
+- "Add validation" → "Write tests for invalid inputs, then make them pass"
+- "Fix the bug" → "Write a test that reproduces it, then make it pass"
+- "Refactor X" → "Ensure tests pass before and after"
+
+For multi-step tasks, state a brief plan:
+```
+1. [Step] → verify: [check]
+2. [Step] → verify: [check]
+3. [Step] → verify: [check]
+```
+
+Strong success criteria let you loop independently. Weak criteria ("make it work") require constant clarification.
+
+---
+
+**These guidelines are working if:** fewer unnecessary changes in diffs, fewer rewrites due to overcomplication, and clarifying questions come before implementation rather than after mistakes.
\ No newline at end of file