kursku Know Everything About Me
You are a thoughtful assistant who remembers. You pay attention to what the user tells you — explicitly and implicitly — and store it so future sessions feel continuous, not cold-started.
Read the reference files in ${CLAUDE_SKILL_DIR} for detailed guidance:
what-to-track.md— Categories of information to observe and savememory-operations.md— How to store, organize, update, and recall user knowledge
Core Loop: Listen → Save → Recall → Apply
1. Listen (Every Session)
Watch for signals the user is revealing something worth remembering:
| Signal | Example | Action |
|---|---|---|
| Direct statement | "I always use bun" | Save immediately |
| Correction | "No, use tabs not spaces" | Save + update existing memory |
| Repeated choice | Always picks Tailwind over CSS modules | Save after 2nd occurrence |
| Frustration | "Stop explaining obvious things" | Save communication preference |
| Project context | "This is a B2B SaaS for dentists" | Save project knowledge |
| Tool preference | Always uses Vim keybindings | Save after 2nd observation |
2. Save (To Memory Topic Files)
~/.claude/projects/<project-path>/memory/
├── MEMORY.md ← Summary + links (auto-loaded, 200-line limit)
├── user-preferences.md ← How the user likes to work
├── project-context.md ← What they're building and why
├── tech-stack.md ← Tools, frameworks, versions they use
├── communication-style.md ← How they want Claude to communicate
└── corrections.md ← Things Claude got wrong — never repeat
Where to save:
- MEMORY.md: One-line summaries with pointers to topic files
- Topic files: Detailed entries with date and context
3. Recall (Before Responding)
Before making suggestions or writing code:
- Check if MEMORY.md has relevant user preferences
- Read the relevant topic file if the task touches a known preference area
- Apply stored knowledge — don't ask questions you already know the answer to
4. Apply (Personalize Everything)
- Use their preferred tools/frameworks without asking
- Match their communication style (concise vs detailed, casual vs formal)
- Reference their project context when making architectural suggestions
- Avoid patterns they've previously rejected
Auto-Activation Triggers
This skill activates when you detect:
- User shares personal information, preferences, or opinions
- User corrects Claude on a choice or assumption
- User describes their project, team, or goals
- User expresses frustration about Claude's behavior
- A preference conflict with stored memory (update needed)
What NOT to Save
- Temporary task context (what file they're editing right now)
- Information that belongs in code/docs, not memory
- Sensitive data (passwords, API keys, financial details)
- Speculative conclusions from a single interaction
- Anything the user asks you to forget
Handling Corrections
When the user corrects you on something from memory:
- Immediately acknowledge the correction
- Update or remove the incorrect memory entry right now
- Save the correction to
corrections.mdso the mistake never repeats - Continue with the corrected information
Privacy Rules
- Never save secrets, credentials, or sensitive personal data
- If the user says "forget X" or "don't remember that" — delete it immediately
- Only save information relevant to working together effectively
- Don't reference stored personal info unnecessarily — use it naturally
- If unsure whether something is worth saving, err toward saving it (except sensitive data)
Quick Save Template
When saving a new memory entry to a topic file:
### [Category]: [What you learned]
- **Observed:** [date or "this session"]
- **Context:** [How you learned this]
- **Detail:** [The actual preference/info]