Back to Details

eureka

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Eureka

顿悟时刻

Capture technical breakthroughs and transform them into actionable, reusable knowledge assets while context is fresh.
捕捉技术突破并在记忆清晰时将其转化为可落地、可复用的知识资产。

Process

流程

1. Capture the Breakthrough

1. 记录突破内容

When invoked, immediately gather the essential details:
  • What was the problem? The specific challenge or blocker faced.
  • What was the insight? The key realization that unlocked the solution.
  • What changed? Concrete before/after differences (metrics, behavior, code).
  • Is there a minimal working example? Request one if not provided.
Ask clarifying questions if any of these are unclear, but act fast — capture while context is fresh.
被触发时，立即收集核心细节：
  • 问题是什么？ 所面临的具体挑战或障碍。
  • 洞见是什么？ 解锁解决方案的核心认知。
  • 有哪些变化？ 具体的前后差异（指标、表现、代码）。
  • 是否有最小可行示例？ 如果未提供，请用户补充。
如果有信息不明确，可提出澄清问题，但需尽快行动——趁记忆清晰时完成记录。

2. Create the Breakthrough File

2. 创建突破记录文件

Create a structured markdown file at 
breakthroughs/YYYY-MM-DD-[brief-name].md
using today's date and a concise kebab-case name derived from the breakthrough.
Use this template:
markdown
undefined
在
breakthroughs/YYYY-MM-DD-[brief-name].md
路径下创建结构化的Markdown文件，文件名采用当天日期和由突破内容提炼的简洁短横线命名格式（kebab-case）。
使用以下模板：
markdown
undefined

[Descriptive Title]

[Descriptive Title]

Date: YYYY-MM-DD Tags: [relevant, searchable, tags]
Date: YYYY-MM-DD Tags: [relevant, searchable, tags]

One-Line Summary

One-Line Summary

A single sentence capturing the core insight.
A single sentence capturing the core insight.

The Problem

The Problem

What was the challenge? What wasn't working? Include specific error messages, performance numbers, or behavioral descriptions.
What was the challenge? What wasn't working? Include specific error messages, performance numbers, or behavioral descriptions.

The Insight

The Insight

The key realization or discovery. What made this non-obvious? Why did previous approaches fail?
The key realization or discovery. What made this non-obvious? Why did previous approaches fail?

Implementation

Implementation

Minimal working code demonstrating the solution:
```[language]
Minimal working code demonstrating the solution:
undefined

concrete code example

concrete code example

```
undefined

Impact

Impact

MetricBeforeAfter
[relevant metric][value][value]
MetricBeforeAfter
[relevant metric][value][value]

Reusable Pattern

Reusable Pattern

Abstract the specific solution into a general principle that can be applied elsewhere:
  • When you see: [symptom or situation]
  • Consider: [the general approach]
  • Because: [why it works]
Abstract the specific solution into a general principle that can be applied elsewhere:
  • When you see: [symptom or situation]
  • Consider: [the general approach]
  • Because: [why it works]

Related Resources

Related Resources

  • Links to relevant documentation, issues, or discussions
undefined
  • Links to relevant documentation, issues, or discussions
undefined

3. Update the Index

3. 更新索引文件

Update 
breakthroughs/INDEX.md
with a new entry. If the index file does not exist, create it with this structure:
markdown
undefined
更新
breakthroughs/INDEX.md
文件，添加新条目。若索引文件不存在，需按以下结构创建：
markdown
undefined

Breakthrough Index

Breakthrough Index

DateTitleTagsLink
YYYY-MM-DD[Title][tags][link to file]

Append the new entry to the table, keeping entries in reverse chronological order (newest first).
DateTitleTagsLink
YYYY-MM-DD[Title][tags][link to file]

将新条目添加到表格末尾，保持条目按倒序排列（最新的在前）。

4. Extract Reusable Patterns

4. 提炼可复用模式

After documenting, help the user identify:
  • Is this pattern applicable to other parts of the codebase?
  • Could this become a lint rule, test, or automated check?
  • Should this be shared with the team?
完成记录后，协助用户梳理：
  • 该模式是否适用于代码库的其他部分？
  • 是否可将其转化为lint规则、测试或自动化检查？
  • 是否应与团队成员共享？

Key Principles

核心原则

  • Act fast: Capture insights while context is fresh — don't over-polish on first pass.
  • Be specific: Include concrete metrics, error messages, and code. Vague breakthroughs are not reusable.
  • Think reusable: Always extract the generalizable pattern from the specific solution.
  • Stay searchable: Use consistent tags and clear titles so breakthroughs can be found later.
  • 快速行动：趁记忆清晰时捕捉洞见——初稿无需过度打磨。
  • 具体明确：包含具体指标、错误信息和代码内容。模糊的突破记录不具备复用价值。
  • 复用思维：始终从具体解决方案中提炼可推广的通用模式。
  • 便于搜索：使用统一的标签和清晰的标题，确保后续可快速找到突破记录。

Your Task

你的任务

Document the breakthrough based on what the user describes:
  1. If the description is clear, proceed directly to creating the breakthrough file
  2. If details are missing, ask focused clarifying questions first
  3. Create the file, update the index, and highlight the reusable pattern
根据用户描述的内容记录突破：
  1. 如果描述清晰，直接创建突破记录文件
  2. 如果信息缺失，先提出针对性的澄清问题
  3. 创建文件、更新索引，并突出可复用模式