Skip to main content

brain

Read/write brain files (Obsidian vault at brain/). Use for any task that persists knowledge — reflection, planning, or direct edits. Triggers after debugging sessions, mistakes, corrections, architectural decisions, or any insight worth preserving across sessions. Use on 'add to brain', 'remember this', 'write a note', or brain/ modifications.

설치로 이동

소스 정보

저장소
poteto/noodle
최근 소스 활동
2026년 3월 19일 04:43
감지된 SKILL.md 언어
영어
스타
281
포크
16

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
brain
description
Read/write brain files (Obsidian vault at brain/). Use for any task that persists knowledge — reflection, planning, or direct edits. Triggers after debugging sessions, mistakes, corrections, architectural decisions, or any insight worth preserving across sessions. Use on 'add to brain', 'remember this', 'write a note', or brain/ modifications.
# 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. ## 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. ## 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. ## Wikilinks Format: `[[section/file-name]]`. Resolution order: same directory, then relative path, then vault root. Heading anchors (`[[file#heading]]`) are stripped during resolution. ## Writing Style - Bullets over prose. No preamble. - Plain markdown with `# Title`. No Obsidian frontmatter. - Keep notes under ~50 lines. Split if longer. ## 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. ## 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. ## Maintenance - Delete outdated or subsumed notes. - Delete random-named files in `brain/plans/` — stale plan-mode artifacts. - Merge overlapping notes before adding new ones.
GitHub에서 보기