원클릭으로
remember
Use when making a decision, choosing a convention, or learning a lesson that should persist across sessions.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Use when making a decision, choosing a convention, or learning a lesson that should persist across sessions.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when you need a comprehensive code audit covering security, performance, architecture, and dependencies before a release, major refactor, or compliance review.
Use when you want to iteratively build a feature using a PRD as source of truth, with progress tracking and fresh-context iterations - the Autopilot technique for autonomous development.
Use when starting a complex feature, exploring unclear requirements, or needing to challenge assumptions before committing to a design - before /plan.
Use when you need a comprehensive code review combining architecture, security, and test perspectives - especially before merging, releasing, or after major changes.
Use when creating marketing copy for landing pages, email campaigns, product descriptions, or social media - with A/B variants and conversion-focused frameworks.
Use when optimizing landing pages, signup flows, checkout processes, or any user-facing page for higher conversion rates - before A/B testing.
| name | remember |
| description | Use when making a decision, choosing a convention, or learning a lesson that should persist across sessions. |
| user-invocable | true |
| argument-hint | [what to remember] |
| allowed-tools | Read, Write, Glob |
Save decisions, preferences, and lessons that persist across sessions using Claude Code's native auto-memory system.
Input: $ARGUMENTS
Detect type of memory:
project (e.g., "Use X instead of Y because Z")feedback (e.g., "Always use single quotes")feedback (e.g., "Never use any types")feedback (e.g., "Prefer composition over inheritance")feedback (e.g., "API changed and broke app. Solution: version contracts")project (e.g., "Merge freeze starts March 5")reference (e.g., "Bugs tracked in Linear project INGEST")Write a markdown file to the memory directory with frontmatter:
---
name: [kebab-case-topic-name]
description: [one-line description for relevance matching]
type: [project | feedback | reference]
---
[Memory content]
**Why:** [reason or context]
**How to apply:** [when/where this applies]
Memory directory: .claude/projects/<project-hash>/memory/
Add an entry to MEMORY.md in the memory directory. Keep it concise - just a link and brief description.
Before creating a new file, check if a memory on the same topic already exists. If yes, UPDATE the existing file instead of creating a duplicate.
──── /remember ────
Saved to project memory
Type: [Decision | Preference | Pattern | Lesson | Context | Reference]
Topic: [topic]
Content: [what was saved]
This will be recalled in future sessions via MEMORY.md.
/remember Use Zustand for state management because it's simpler than Redux
Output:
Saved to project memory
Type: Decision (project)
Topic: State Management
Content: Use Zustand instead of Redux
Reason: Simpler API, less boilerplate
/remember Always use single quotes in this project
/remember Never use any types in TypeScript
/remember The API changed format and broke parsing. Solution: Always create adapters with versioned contracts.