Process file changes and update CLAUDE.md memory sections. Use when the memory-updater agent needs to analyze dirty files, update AUTO-MANAGED sections, verify content removal, or detect stale commands. Invoked after file edits to keep project memory in sync.
Updates CLAUDE.md memory sections by analyzing file changes and verifying content accuracy against the codebase.
/plugin marketplace add severity1/claude-code-auto-memory/plugin install auto-memory@severity1-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Process changed files and update relevant CLAUDE.md sections following official guidelines.
MANDATORY: All rules below must be followed exactly. Violations produce incorrect CLAUDE.md content.
@../shared/references/guidelines.md
Parse context: Read context provided by memory-updater agent:
Categorize changes: Map files to CLAUDE.md sections using the tables in "Section Names" below. Match changed files to their update triggers.
Analyze impact: Determine what needs updating:
Verify and update content: Before modifying documented content, verify accuracy:
Key distinction - conventions vs patterns:
conventions: Explicit rules humans decided (naming, imports, formatting)patterns: Implicit patterns AI detected from recurring code structuresRemoval verification:
Stale command detection:
python pytest | Actually worked: python -m pytest → Updatenpm test | Actually worked: npm run test → Updatepytest tests/ | Actually worked: uv run pytest → UpdateExamples:
@decorator removed → search grep -r "@decorator" src/async/await style removed → search for async function or awaitutils/ directory deleted → verify no utils/ references remainnpm run dev removed from package.json → verify script is goneUpdate CLAUDE.md: Modify relevant sections:
Validate: Ensure updates follow guidelines:
CLAUDE.md uses HTML comment markers for selective updates:
<!-- AUTO-MANAGED: section-name -->
Content that will be automatically updated
<!-- END AUTO-MANAGED -->
<!-- MANUAL -->
Content that will never be touched
<!-- END MANUAL -->
| Section | Purpose | Update Triggers |
|---|---|---|
project-description | Project overview | README changes, major refactors |
build-commands | Build, test, lint commands | package.json, Makefile, pyproject.toml |
architecture | Directory structure, components | New dirs, renamed files, structural changes |
conventions | Naming, imports, code standards | Pattern changes in source files |
patterns | AI-detected coding patterns | Repeated patterns across files |
git-insights | Decisions from git history | Significant commits |
best-practices | From official Claude Code docs | Manual updates only |
| Section | Purpose | Update Triggers |
|---|---|---|
module-description | Module purpose | Module README, major changes |
architecture | Module structure | File changes within module |
conventions | Module-specific conventions | Pattern changes in module |
dependencies | Key module dependencies | Import changes, package updates |
@path/to/file) for detailed specsReturn a brief summary:
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.