Skill

auto-memory

Auto-save context when the agent learns something — triggers on: remember, convention, always do, note for future, learned that, from now on, never do, experiment completion, bug resolution

From claude-eureka

Install

Run in your terminal

npx claudepluginhub gaaaavin/claude-eureka --plugin claude-eureka

Tool Access

This skill uses the workspace's default tool permissions.

Skill Content

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

138.7k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

bmad-editorial-review-prose

Reviews prose for communication issues impeding comprehension, outputs minimal fixes in a three-column table per Microsoft Writing Style Guide. Useful for 'review prose' or 'improve prose' requests.

bmad-pro-skills

43.8k

Stats

Stars0

Forks0

Last CommitMar 12, 2026

Actions

View Source View Plugin View on GitHub View README

Where to save

Route entries to the appropriate context file:

Content type

File

Conventions, preferences, workflows

.claude/context/conventions.md

Experiment results, metrics, findings

.claude/context/experiments.md

Architecture discoveries, code patterns

.claude/context/architecture.md

Create the file if it does not exist. Use a # Context heading at the top.

When to save

Activate when any of these occur:

User says to remember something, establishes a convention, or sets a preference
An experiment completes and results are logged
A bug is resolved and root cause is identified
A significant architectural discovery is made about the codebase

Where to save

Route entries to the appropriate context file:

Content type	File
Conventions, preferences, workflows	`.claude/context/conventions.md`
Experiment results, metrics, findings	`.claude/context/experiments.md`
Architecture discoveries, code patterns	`.claude/context/architecture.md`

Create the file if it does not exist. Use a # Context heading at the top.

Entry format

Each entry is a dated, concise line:

- **YYYY-MM-DD**: <short description of what was learned or decided>

Append new entries under the appropriate section heading. Keep descriptions to one or two sentences.

Deduplication

Before adding an entry:

Read the target context file
Search for keywords from the new entry
If a substantially similar entry exists, update it in place instead of adding a duplicate
If updating, preserve the original date and append the new date: (updated YYYY-MM-DD)

Guidelines

Be concise — context files are loaded into every conversation
Only save things with lasting value, not one-off facts
Never store secrets, tokens, or credentials
Prefer actionable entries ("use X instead of Y") over observations