본문으로 건너뛰기
cccskills
무료GitHub에 공개

dream

Memory consolidation pass: orient on existing memories, gather signal from logs/transcripts, merge updates into topic files, prune index. Use on 'dream', 'consolidate memory', 'clean up memories', 'prune memories', 'memory maintenance', or when memories feel stale.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(1)

  • SKILL.md3.1 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Dream: Memory Consolidation

You are performing a dream — a reflective pass over your memory files. Synthesize what you've learned recently into durable, well-organized memories so that future sessions can orient quickly.

Memory directory: ${MEMORY_DIR} ${MEMORY_DIR_CONTEXT}

Session transcripts: ${TRANSCRIPTS_DIR} (large JSONL files — grep narrowly, don't read whole files)


Phase 1 — Orient

  • ls the memory directory to see what already exists
  • Read ${INDEX_FILE} to understand the current index
  • Skim existing topic files so you improve them rather than creating duplicates
  • If logs/ or sessions/ subdirectories exist (assistant-mode layout), review recent entries there

Phase 2 — Gather recent signal

Look for new information worth persisting. Sources in rough priority order:

  1. Daily logs (logs/YYYY/MM/YYYY-MM-DD.md) if present — these are the append-only stream
  2. Existing memories that drifted — facts that contradict something you see in the codebase now
  3. Transcript search — if you need specific context (e.g., "what was the error message from yesterday's build failure?"), grep the JSONL transcripts for narrow terms: grep -rn "<narrow term>" ${TRANSCRIPTS_DIR}/ --include="*.jsonl" | tail -50

Don't exhaustively read transcripts. Look only for things you already suspect matter.

Phase 3 — Consolidate

For each thing worth remembering, write or update a memory file at the top level of the memory directory. Use the memory file format and type conventions from your system prompt's auto-memory section — it's the source of truth for what to save, how to structure it, and what NOT to save.

Focus on:

  • Merging new signal into existing topic files rather than creating near-duplicates
  • Converting relative dates ("yesterday", "last week") to absolute dates so they remain interpretable after time passes
  • Deleting contradicted facts — if today's investigation disproves an old memory, fix it at the source

Phase 4 — Prune and index

Update ${INDEX_FILE} so it stays under ${INDEX_MAX_LINES} lines AND under ~25KB. It's an index, not a dump — each entry should be one line under ~150 characters: - [Title](file.md) — one-line hook. Never write memory content directly into it.

  • Remove pointers to memories that are now stale, wrong, or superseded
  • Demote verbose entries: if an index line is over ~200 chars, it's carrying content that belongs in the topic file — shorten the line, move the detail
  • Add pointers to newly important memories
  • Resolve contradictions — if two files disagree, fix the wrong one

Return a brief summary of what you consolidated, updated, or pruned. If nothing changed (memories are already tight), say so.${ADDITIONAL_CONTEXT?`

Additional context

${ADDITIONAL_CONTEXT}`:""}

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Aplica el branding de Vambe a PPTX, DOCX, XLSX y HTML. Usa al crear presentaciones, Word, Excel o páginas con identidad visual de Vambe, o si pide "hacerlo bonito" / "estilo Vambe".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

sebastianbreguel/dotfiles32026년 10월 8일 업데이트

Read this skill before the first step that uses the built-in browser, the browser pane inside the Claude desktop app (also called the in-app browser, the browser pane, Claude's browser, or "your own browser"), whose tools are named mcp__Claude_Browser__* when the session runs in the desktop app and mcp__remote-devices__Claude_Browser__* when a cloud session is linked to the person's computer; before those tools are turned on there may be a single enable__mcp__remote-devices__Claude_Browser tool instead. It covers the pane's persistent sign-ins, tabs and preview_start, reading pages as text, site approvals, what the pane cannot open, and what to do when it cannot be reached. It is not for Claude in Chrome (mcp__claude-in-chrome__* tools), which has its own skill, and it does not decide which browser to use.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

sebastianbreguel/dotfiles32026년 10월 8일 업데이트

Read this skill before the first step that uses Claude in Chrome, the browser extension whose tools are named mcp__claude-in-chrome__* (also called Chrome, the browser extension, or the external browser) and which acts in the person's real Chrome with their own sign-ins; before those tools are turned on there may be a single enable__mcp__claude-in-chrome tool instead. It covers loading the tools in one ToolSearch call, checking the person's open tabs and working in a new tab, site permissions, GIF recordings, console logs, dialogs to avoid, and when to stop and ask. It is not for the built-in browser (mcp__Claude_Browser__* or mcp__remote-devices__Claude_Browser__* tools), which has its own skill, and it does not decide which browser to use.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

sebastianbreguel/dotfiles32026년 10월 8일 업데이트

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

sebastianbreguel/dotfiles32026년 10월 8일 업데이트

Read this skill before the first step of any request to do something in an app on the person's own computer (Notes, Finder, System Settings, any desktop app), to look at their screen, or for "computer use". Computer use (desktop control) lets Claude take screenshots of the person's desktop and control it with clicks, typing and scrolling through the Claude desktop app; its tools are named mcp__computer-use__* when the session runs in the desktop app and mcp__remote-devices__computer_* when a cloud session is linked to the person's computer; before computer use is turned on for a conversation there may be no such tools, only an enable__mcp__remote-devices__computer tool, which turns it on. It covers turning it on, picking the right tool, the access flow, and the safety rules for tiered apps, links and financial actions. It is not for websites, which go through Claude in Chrome or the built-in browser and their own skills.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

sebastianbreguel/dotfiles32026년 10월 8일 업데이트

Use this skill when the user's prompt requires (1) researching a topic across multiple sources, comparing options or alternatives, analyzing trends or history, understanding markets or industries, or reviewing literature or studies and (2) synthesizing that research into a comprehensive, narrative report. If you're planning to search the web or internal knowledge bases, consider using this skill. This skill coordinates research subagents, so use it only when you have a tool for spawning subagents (the Agent or Task tool); otherwise, research the question directly.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

sebastianbreguel/dotfiles32026년 10월 8일 업데이트

sebastianbreguel의 스킬 모두 보기

이 스킬의 문제 신고