remember
The Remember skill helps teams extract and organize useful knowledge discovered during work sessions by reviewing findings and distributing them to appropriate memory surfaces. Use this when discovering project facts that should outlive the current conversation, temporary working notes needed for upcoming turns, operator preferences worth preserving, or when identifying duplicate or conflicting information that needs cleanup. It routes durable team knowledge to project memory, active context to notepad, and instructions to docs while preventing information from getting buried in chat history.
git clone --depth 1 https://github.com/Yeachan-Heo/oh-my-claudecode /tmp/remember && cp -r /tmp/remember/skills/remember ~/.claude/skills/rememberSKILL.md
# Remember Use this skill when the user wants to preserve or organize useful knowledge discovered during a session. ## Goal Promote durable, reusable knowledge into the right memory surface instead of leaving it buried in chat history. ## Memory surfaces - **Project memory** — durable team/project knowledge - **Notepad priority** — short high-signal context for the next turns - **Notepad working** — temporary active-session notes - **Docs / AGENTS / CLAUDE files** — durable instructions and conventions when they truly belong there ## Workflow 1. Gather the relevant session findings. 2. Classify each item: - durable project fact - temporary working note - operator preference or instruction - duplicate / stale / conflicting information 3. Propose the best destination for each item. 4. Write or update only the appropriate memory surface. 5. Call out duplicates or conflicts that should be cleaned up. ## Rules - Do not dump everything into one store. - Prefer project memory for durable team knowledge. - Prefer notepad for short-lived working context. - Keep entries concise and actionable. - If something is uncertain, mark it as uncertain rather than storing it as fact. ## Output - What was stored - Where it was stored - Any duplicates/conflicts found
Pre-planning consultant for requirements analysis (Opus)
Strategic Architecture & Debugging Advisor (Opus, READ-ONLY)
Expert code review specialist with severity-rated feedback, logic defect detection, SOLID principle checks, style, performance, and quality strategy
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.
Work plan and code review expert — thorough, structured, multi-perspective (Opus)
Root-cause analysis, regression isolation, stack trace analysis, build/compilation error resolution
UI/UX Designer-Developer for stunning interfaces (Sonnet)
External Documentation & Reference Specialist