brain

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Brain

Persistent memory across sessions. Obsidian vault at

brain/

The brain is the foundation of the entire workflow — every agent, skill, and session reads it. Low-quality or speculative content degrades everything downstream. Before adding anything, ask: "Does this genuinely improve how the system operates?" If the answer isn't a clear yes, don't write it.

跨会话的持久化记忆。Obsidian库位于

brain/

目录。

Brain是整个工作流的基础——所有Agent、Skill和会话都会读取它。低质量或推测性内容会影响下游所有环节。在添加任何内容之前，请先问自己："这是否真的能改善系统的运行方式？"如果答案不是明确的"是"，就不要写入。

Before Writing

写入前准备

Read

brain/index.md

first. Then read the relevant entrypoint for your topic:

```
brain/principles.md
```
for principle updates
```
brain/plans/index.md
```
for plan-related notes

For directories without a dedicated index file yet (

brain/codebase/

brain/audits/

), scan nearby files directly and edit an existing note when possible.

请先阅读

brain/index.md

。然后阅读与你的主题相关的入口文件：

若要更新原则，请查看
```
brain/principles.md
```
若要添加计划相关笔记，请查看
```
brain/plans/index.md
```

对于尚未有专用索引文件的目录（如

brain/codebase/

、

brain/audits/

），请直接浏览附近的文件，并尽可能编辑现有笔记。

Structure

结构

brain/
├── index.md              ← root entry point, links to everything
├── principles.md         ← index for principles/
├── todos.md              ← product backlog
├── vision.md             ← elevator pitch + link to architecture
├── architecture.md       ← full technical reference
├── principles/           ← engineering and design principles
├── codebase/             ← project-specific knowledge and gotchas
├── plans/                ← numbered feature plans (02-arrow-bindings/, etc.)
└── audits/               ← design and quality audits (date-prefixed filenames, e.g. 2026-02-20-quality-audit.md)

Rules:

One topic per file.
```
brain/codebase/noodle-spawn-gotchas.md
```
, not a mega-file.

Maintain existing index entrypoints:

brain/index.md

brain/principles.md

brain/plans/index.md

If you introduce a new top-level category, add an index-style entrypoint for it (links only, no inlined content).
```
brain/index.md
```
is the root. Every brain file must be reachable from it.
File names: lowercase, hyphenated.
```
worktree-gotchas.md
```
.
Plan directories: prefixed with the todo ID from
```
brain/todos.md
```
.
```
02-arrow-bindings/
```
with
```
overview.md
```
and
```
phase-N-*.md
```
inside.

brain/
├── index.md              ← 根入口文件，链接到所有内容
├── principles.md         ← principles/目录的索引
├── todos.md              ← 产品待办事项列表
├── vision.md             ← 电梯游说文案 + 架构链接
├── architecture.md       ← 完整技术参考文档
├── principles/           ← 工程与设计原则
├── codebase/             ← 项目专属知识与注意事项
├── plans/                ← 编号的功能计划（如02-arrow-bindings/等）
└── audits/               ← 设计与质量审计（文件名以日期为前缀，例如2026-02-20-quality-audit.md）

规则：

每个文件对应一个主题。例如使用
```
brain/codebase/noodle-spawn-gotchas.md
```
，而非大文件。

维护现有索引入口文件：

brain/index.md

、

brain/principles.md

、

brain/plans/index.md

。

若新增顶级分类，请为其添加索引式入口文件（仅包含链接，无内嵌内容）。
```
brain/index.md
```
是根入口，所有Brain文件必须能从这里访问到。
文件名：小写，连字符分隔。例如
```
worktree-gotchas.md
```
。
计划目录：以
```
brain/todos.md
```
中的待办事项ID为前缀。例如
```
02-arrow-bindings/
```
目录下包含
```
overview.md
```
和
```
phase-N-*.md
```
文件。

Wikilinks

维基链接

Format:

[[section/file-name]]

. Resolution order: same directory, then relative path, then vault root. Heading anchors (

[[file#heading]]

) are stripped during resolution.

格式：

[[section/file-name]]

。解析顺序：同一目录 → 相对路径 → 库根目录。解析时会移除标题锚点（

[[file#heading]]

）。

Writing Style

写作风格

Bullets over prose. No preamble.
Plain markdown with
```
# Title
```
. No Obsidian frontmatter.
Keep notes under ~50 lines. Split if longer.

优先使用项目符号，而非散文式叙述。无需开场白。
使用纯Markdown格式，仅保留
```
# 标题
```
。不要添加Obsidian前置元数据。
笔记长度控制在约50行以内，过长请拆分。

After Writing

写入后操作

Update

brain/index.md

for any files you added or removed. Also update the relevant entrypoint (

brain/principles.md

brain/delegation.md

, or

brain/plans/index.md

) when applicable. Keep indexes link-only and scannable.

若添加或删除了文件，请更新

brain/index.md

。同时，若适用，请更新相关入口文件（

brain/principles.md

、

brain/delegation.md

或

brain/plans/index.md

）。索引文件仅保留链接，确保易读易扫描。

Durability Test

耐久性测试

Ask: "Would I include this in a prompt for a different task?"

Yes → write to
```
brain/
```
. It's durable knowledge.
No, it's plan-specific → update the plan's phase doc instead.
No, it's a skill issue → update the skill file directly.
No, it needs follow-up work → file a todo with the
```
todo
```
skill.

请自问："我会在其他任务的提示词中包含这段内容吗？"

是 → 写入
```
brain/
```
目录。这是持久性知识。
否，仅针对特定计划 → 请更新该计划的阶段文档。
否，属于Skill问题 → 直接更新Skill文件。
否，需要后续工作 → 使用
```
todo
```
Skill创建待办事项。

Maintenance

维护

Delete outdated or subsumed notes.
Delete random-named files in
```
brain/plans/
```
— stale plan-mode artifacts.
Merge overlapping notes before adding new ones.

删除过时或已被替代的笔记。
删除
```
brain/plans/
```
目录下的随机命名文件——这些是过期的计划模式产物。
在添加新笔记前，合并重叠的内容。