Communitygithub.com

記住

回顧可重複使用的專案知識,並決定哪些內容應存入專案記憶、記事本或持久化文件。

記住 是什麼?

「記住」技能旨在幫助使用者將會話過程中發現的有用知識,以結構化方式保存到最合適的記憶空間,避免這些知識被埋沒在對話歷史中。它支援多種記憶層級,包括持久化的專案記憶(適用於團隊或專案層級的知識)、記事本優先級(提供給後續回合的高信號短上下文)、記事本工作區(暫存當前會話筆記),以及 Docs/AGENTS/CLAUDE 文件(歸檔真正的持久化指令與慣例)。使用者只需提供會話中的相關發現,技能會自動對每項內容進行分類(例如:持久化專案事實、暫存工作筆記、操作者偏好或指令、重複/過時/衝突資訊),並建議最佳存放位置,最後執行寫入或更新操作,同時標記需要清理的重複或衝突項目。此技能適用於任何需要長期管理 AI 助手知識的情境,常見於 Claude Code、Cursor、Codex 等開發工具。

相容平台✓Claude Code~Codex CLI~Cursor
npx skills add https://github.com/Yeachan-Heo/oh-my-claudecode/tree/main/skills/remember

在你喜歡的 AI 中提問

開啟一個已預先載入此 Agent Skill 的新對話。

說明文件

記住 是做什麼的?

當使用者希望將會話期間發現的有用知識保存或整理時,請使用此技能。

目標

將持久且可重複使用的知識推送到正確的記憶空間,避免它們被埋沒在對話歷史中。

記憶空間

  • 專案記憶 — 持久的團隊/專案知識
  • 記事本優先級 — 提供給後續回合的高信號短上下文
  • 記事本工作區 — 暫存當前有效的工作階段筆記
  • Docs/AGENTS/CLAUDE 檔案 — 真正屬於持久化指令和慣例時存放於此

工作流程

  1. 收集相關的工作階段發現。
  2. 對每項內容進行分類:
    • 持久的專案事實
    • 暫存的工作筆記
    • 操作者偏好或指令
    • 重複/過時/衝突的資訊
  3. 為每項內容提議最佳存放位置。
  4. 僅寫入或更新合適的記憶空間。
  5. 標記應清理的重複或衝突項目。

規則

  • 不要將所有東西都傾倒進一個儲存空間。
  • 持久的團隊知識優先使用專案記憶。
  • 短暫的工作上下文優先使用記事本。
  • 保持條目簡潔且可操作。
  • 如果不確定某件事,將其標記為不確定,而不是當作事實儲存。

輸出

  • 儲存了什麼
  • 儲存在哪裡
  • 找到的任何重複/衝突

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

agent-doc-discipline

Writing-time discipline for documents agents consume (the five surfaces, specs, tickets, .omc/skills/) — every rule checkable and carrying a why, steps before reference, one meaning in one home, no restating what the environment already says. Mandatory at drydock seed generation and the launch C5 sediment pass; opt-in for any other agent-facing doc edit. The companion of minimal-code-discipline: that one disciplines code, this one disciplines papers.

ai-slop-cleaner

Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode

ask

Process-first advisor routing for Claude, Codex, Gemini, Antigravity, Grok, or Cursor via `omc ask`, with artifact capture and no raw CLI assembly

ask-navigator

Shipyard

autopilot

Full autonomous execution from idea to working code

autoresearch

Stateful single-mission improvement loop with strict evaluator contract, markdown decision logs, and max-runtime stop behavior

cancel

Cancel any active OMC mode (autopilot, ralph, ultragoal, swarm, ultrapilot, pipeline, team) and clean up retired legacy state

configure-notifications

Configure notification integrations (Telegram, Discord, Slack) via natural language

debug

Diagnose the current OMC session or repo state using logs, traces, state, and focused reproduction

deepinit

Deep codebase initialization with hierarchical AGENTS.md documentation

deep-interview

Socratic deep interview with mathematical ambiguity gating before explicit execution approval

drydock

Lay the keel of the shipyard harness in any repo — the 4-pillar shared environment (Context, Rules, Tools, Standards) across 5 surfaces (CLAUDE.md, skills, design-system, mcp/cli, shared context) so that every human and agent inherits the same design language and anyone can ship. Run once per repo; re-run with --check to audit drift.

execute

Carry an approved task through to working, verified code

external-context

Invoke parallel document-specialist agents for external web searches and documentation lookup

graph

Deterministic orchestration graph runtime - declarative DAG pipelines with journal-based crash recovery

harbor

Harbor intake for external work — the captain only handles unresolved decisions. Sweeps incoming issues and PRs, verifies every claim before disposition, reuses every decision already made, and hands the maintainer a docket whose pending items each carry one question with options, recommendation, impact and evidence. Agent-autonomous for facts and for actions covered by standing authorization; signed for every new judgment. Never merges.

hud

Configure HUD display options (layout, presets, display elements)

launch

Shipyard

loft

Loft the shape before cutting steel — answer a design question that prose cannot settle by building a throwaway artifact: a pure logic module in a clickable shell, or structurally different UI variants behind one route. The captain reacts to the artifact; the answer folds into the decision; the artifact never docks. Use when a design question stalls in words, when a navigator map carries a loft ticket, or when a spec discussion reaches

minimal-code-discipline

YAGNI-ladder coding discipline for writing changes — existence-first, reuse before writing, dependency ladder, shortest correct diff, with non-negotiables that must never be minimized away

相關技能