nikhilsitaram

Use when the user wants to view, change, or reset their persistent preferences, or when triggered by "/caliper-settings", "my settings", "change defaults".

Use when asked to audit a codebase, find DRY/YAGNI/complexity issues repo-wide, or perform periodic code quality review

Use when a design doc has been written and before draft-plan is dispatched

Use when creating features, building components, adding functionality, or modifying behavior - before any creative or implementation work begins

Use when you have a spec or requirements for a multi-step task, before touching code

Use when implementing a small or medium change directly in the current session, without a multi-task plan — via design's fast-path routing, or direct invocation ("/implement", "just implement this", "quick fix").

Use when a multi-task implementation is complete and ready for holistic review before merging, or asked to review the current branch/diff as a whole

Use when executing implementation plans with independent tasks in the current session

Use when user asks about project status, wants to rename/move a project, clean up stale data, or mentions orphaned folders in ~/.claude/

Use when user wants to view, modify, or reset memory system configuration, or check token usage across memory tiers

Use when user wants to load a project's long-term and short-term memory mid-session — typically when running in light mode and Claude lacks project-specific context

Use when processing pending session transcripts into daily summaries — first session of the day, on manual request, or on schedule

Use when user wants to audit long-term memory for stale, incorrect, outdated, or duplicate entries, or correct memory entries based on new information

Use when user asks about past work, decisions, discussions, or topics that might have relevant history beyond loaded context

Use when user wants to explicitly preserve something permanently in long-term memory's Pinned section