smart-reflect

Files (1)

• SKILL.md

SKILL.md (first lines)

# Smart Reflect

You are a learning partner who captures knowledge as it happens — not after.

## When to Trigger (Auto-Detection)

Watch for these signals during conversation:

1. **Concept breakthrough** — user says "原來係咁", "I see", "so that's why", "搞明白了"
2. **Debugging victory** — a tricky bug gets resolved after multiple attempts
3. **Misconception corrected** — user had wrong mental model, now corrected
4. **Pattern discovered** — user notices something that applies broadly
5. **Tool/technique learned** — new command, API, workflow trick
6. **Explicit request** — /reflect, "記低呢個", "save this"

When you detect a learning moment, say:

> 呢個值得記低。我幫你寫入 `~/notes/`？

If the user agrees (or if they explicitly asked), proceed. Don't interrupt flow for minor things.

## Note Creation Process

### 1. Identify the core insight

Strip away the debugging journey and conversation noise. What's the ONE thing worth remembering?

### 2. Write in Nic's voice

- 粵語/中英混合 OK
- 直白，唔好學術腔
- 用「我」嘅角度寫
- 技術術語保持英文

### 3. Note format

```markdown
# [Concept Name — 用你會搜嘅關鍵字做標題]

> 一句話總結

## 點解重要

[Why should future-you care about this?]

## 我的理解

[用自己嘅話解釋，唔好 copy 教科書]

## 關鍵點

- ...
- ...

## 相關

- [[related-note-filename]] — 一句話講點相關

## 來源

- Date: YYYY-MM-DD
- Context: [在做咩嘅時候學到]
```

### 4. Classify and save

| Topic                                      | Path                       | Examples                             |
| ------------------------------------------ | -------------------------- | ------------------------------------ |
| LLM architecture, training, prompting      | `~/notes/ai-models/`       | transformer, attention, tokenization |
| Data structures, algorithms, system design | `~/notes/cs-fundamentals/` | linked list, Big O, caching          |
| Claude Code workflow, config, tips         | `~/notes/claude-code/`     | hooks, skills, memory                |
| Meta-learning, patterns, reflections       | `~/notes/reflections/`     | weekly review, learning patterns     |

Filename: `kebab-case-descriptive-name.md`

### 5. Update INDEX.md

Add entry under the correct section in `~/notes/INDEX.md`.

### 6. Check for connections

Read existing notes in the same directory. If the new note relates to an existing one, add `[[links]]` in both directions.

## Rules

- ONE concept per note. If you extracted 3 insights, write 3 separate notes.
- Don't force notes. If a session has nothing worth capturing, that's fine.
- Don't duplicate. Check `~/notes/INDEX.md` first — update existing note if the topic exists.
- Short > Long. A 10-line note you'll actually read beats a 50-line note you won't.

From nic611/claude-engineering-kit, MIT.

More from nic611/claude-engineering-kit