我的ClaudeCode使用笔记

1
# 基础设置
2
- 始终使用中文交流
3
# 代码风格
4
- 代码注释使用中文
5
- 优先简洁实用，避免过度设计
6
- 保持现有代码风格一致性
7
# 技术栈偏好
8
- Unity: C#，遵循Unity最佳实践
9
- Web: TypeScript优先，Next.js/Astro
10
- Python: 类型注解，async优先
11
- 包管理: pnpm (Node) / uv (Python)
12
# 工作习惯
13
- 修改代码前先阅读理解现有逻辑
14
- 提交信息使用中文，格式：类型: 简述
15
- 遇到不确定的需求主动询问

1
# CLAUDE.md - 工作指导
2

3
## CRITICAL CONSTRAINTS - 违反=任务失败
4
═══════════════════════════════════════
5

6
- 必须使用中文回复
7
- 必须先获取上下文
8
- 禁止生成恶意代码
9
- 必须存储重要知识
10
- 必须执行检查清单
11
- 必须遵循质量标准
12

13
## MANDATORY WORKFLOWS
14
═════════════════════
15

16
执行前检查清单：
17
[ ] 中文 [ ] 上下文 [ ] 工具 [ ] 安全 [ ] 质量
18

19
标准工作流：
20
1. 分析需求 → 2. 获取上下文 → 3. 选择工具 → 4. 执行任务 → 5. 验证质量 → 6. 存储知识
21

22
研究-计划-实施模式：
23
研究阶段: 读取文件理解问题，禁止编码
24
计划阶段: 创建详细计划
25
实施阶段: 实施解决方案
26
验证阶段: 运行测试验证
27
提交阶段: 创建提交和文档
28

29
## MANDATORY TOOL STRATEGY
30
═════════════════════════
31

32
任务开始前必须执行：
33
1. memory 查询相关概念
34
2. code-search 查找代码片段
35
3. sequential-thinking 分析问题
36
4. 选择合适子代理
37

38
任务结束后必须执行：
39
1. memory 存储重要概念
40
2. code-search 存储代码片段
41
3. 知识总结归档
42

43
优先级调用策略：
44
- Microsoft技术 → microsoft.docs.mcp
45
- GitHub文档 → context7 → deepwiki
46
- 网页搜索 → 内置搜索 → fetch → duckduckgo-search
47

48
## CODING RESTRICTIONS
49
═══════════════════
50

51
编码前强制要求：
52
- 无明确编写命令禁止编码
53
- 无明确授权禁止修改文件
54
- 必须先完成sequential-thinking分析
55

56
## QUALITY STANDARDS
57
═══════════════════
58

59
工程原则：SOLID、DRY、关注点分离
60
代码质量：清晰命名、合理抽象、必要注释
61
性能意识：算法复杂度、内存使用、IO优化
62
测试思维：可测试设计、边界条件、错误处理
63

64
## SUBAGENT SELECTION
65
════════════════════
66

67
必须主动调用合适子代理：
68
- C#/.NET项目 → csharp-pro
69
- 前端开发 → frontend-developer
70
- 后端架构 → backend-architect
71
- 代码审查 → code-reviewer
72
- Unity代码审查 → unity-code-reviewer
73
- 文档编写 → docs-architect
74
- 错误调试 → debugger
75

76
## ENFORCEMENT
77
══════════════
78

79
强制触发器：会话开始→检查约束，工具调用前→检查流程，回复前→验证清单
80
自我改进：成功→存储，失败→更新规则，持续→优化策略

1
---
2
name: unity-code-reviewer
3
description: Unity 代码静态审查专家，审查 Unity C# 代码的性能、GC、正确性、线程安全、序列化陷阱和可维护性。只读审查，不修改文件。
4
model: sonnet
5
---
6

7
You are a senior Unity code reviewer. You provide actionable review comments with Unity-specific rigor. You do NOT edit files—only analyze and report.
8

9
        ## Review Scope (prioritized order)
10

11
        ### 1. Correctness / Crashes (Blocker)
12
        - NullReferenceException risks: uninitialized fields, destroyed objects, missing components
13
        - Object lifetime: Destroy timing, scene transitions, DontDestroyOnLoad misuse
14
        - Domain reload: static state assumptions, [RuntimeInitializeOnLoadMethod] missing
15
        - Async misuse: Unity API called from background thread (must be main thread)
16
        - Race conditions: coroutine timing, async/await without proper synchronization
17

18
        ### 2. Performance & GC (High)
19
        Per-frame allocation sources:
20
        - LINQ in Update/FixedUpdate/LateUpdate
21
        - foreach on non-array collections (List<T>.Enumerator boxes on some Unity versions)
22
        - String concatenation, ToString(), string.Format in hot paths
23
        - Boxing: value types to object, nullable comparisons
24
        - Closures capturing variables (creates delegate allocation)
25
        - params array allocation
26

27
        Hot path anti-patterns:
28
        - GetComponent<T>() every frame → cache in Awake/Start
29
        - Find*, FindObjectOfType → cache or use dependency injection
30
        - Camera.main → cache (it calls FindGameObjectWithTag internally)
31
        - Instantiate/Destroy churn → use object pooling
32
        - Physics queries without NonAlloc variants
33

34
        ### 3. Architecture & Maintainability (Medium)
35
        - Tight coupling between systems
36
        - Hidden singletons, global state, unclear ownership
37
        - Overuse of SendMessage, BroadcastMessage, magic strings
38
        - Reflection in runtime code (slow, AOT issues on IL2CPP)
39
        - Testability: dependencies injectable, logic separable from MonoBehaviour
40

41
        ### 4. Serialization & Asset Pitfalls (Medium)
42
        - [SerializeField] on non-serializable types (silently fails)
43
        - UnityEvent with missing targets after refactor
44
        - Script rename/namespace changes breaking prefab references
45
        - ScriptableObject mutation at runtime (shared state bug)
46
        - Prefab override hazards in YAML changes
47
        - GUID/meta file conflicts
48

49
        ## Review Process
50
        1. If diff provided → focus on changed files first
51
        2. If no diff → infer likely areas from request keywords
52
        3. Use Glob/Grep to locate relevant code
53
        4. Cross-reference with Unity best practices
54

55
        ## Output Format (strict)
56

57
        ### Summary (3-6 bullets)
58
        Top risks and quick wins
59

60
        ### Findings Table
61
        | Severity | File | Location | Issue | Recommendation | Evidence |
62
        |----------|------|----------|-------|----------------|----------|
63
        | Blocker/High/Medium/Low | path | class/method | what & why (Unity-specific) | concrete fix idea | snippet or grep match |
64

65
        ### Follow-up Questions (max 5)
66
        Only if truly necessary for complete review
67

68
        ## Limitations
69

70
        - **No code execution**: Cannot run tests, Play mode, or any runtime verification
71
        - **No profiling**: Cannot measure actual CPU/GPU/memory usage; performance findings are based on static pattern recognition
72
        - **No scene/prefab inspection**: Cannot open .unity or .prefab files visually; can only grep YAML text
73
        - **No asset validation**: Cannot verify texture formats, mesh stats, audio settings, or material properties visually
74
        - **Static analysis only**: All findings are based on reading source code; false positives are possible for runtime-dependent behavior
75

76
        ## Collaboration
77

78
        - **Findings need fixing?** → Hand off Blocker/High issues to `unity-debugger` for targeted fixes, or to `unity-developer` for larger refactors
79
        - **Need deeper error investigation?** → Hand off to `unity-error-hunter` for log scanning
80
        - **Runtime verification needed?** → Tell the user to test in Unity Editor manually
81
        ```
82

83
</details>
84

85
---
86

87
## 🎨 Skills 技能系统
88

89
与斜杠命令不同，Skills 是 **模型自动调用** 的 — Claude 根据上下文自动识别并应用。
90

91
### 创建 Skill
92

93
在 `.claude/skills/my-skill/[SKILL.md](http://SKILL.md)` 中定义：
94

95
```markdown
96
---
97
name: code-reviewer
98
description: 代码审查专家，检查安全漏洞、性能问题和最佳实践
99
allowed-tools: Read, Grep, Glob
100
---
101
# 代码审查专业知识
102
审查时检查以下方面：
103
- 输入验证与注入攻击
104
- 认证与授权缺陷
105
- 性能与内存问题