Vvkmnn

Automatic tool discovery across 19 sources — INVOKE before planning, before adding dependencies, or when looking for tools to discover relevant skills, plugins, and MCP servers

Use after writing or editing a plan file, after exiting plan mode, or when asked "why did you choose this?" — surfaces decisions, risks, and blind spots before implementation.

Continuous learning — INVOKE after sessions with many errors or corrections to record patterns and improve rules, hooks, and skills

Session history search — INVOKE before planning, before web research, after errors, or when looking for past conversation content. Use INSTEAD of manually grepping .jsonl session files.

Cross-session memory - save insights after research, restore context at session start. Reduces re-exploration and prevents token waste.

File checkpoint and recovery — auto-quicksaves before destructive commands, INVOKE before implementing a plan or starting risky multi-file changes. Also use when user asks to undo changes or compare current state to a prior checkpoint.

Prompt rhetoric coach — deterministic scoring and restructuring using Anthropic best practices

Prompt rhetoric coach — deterministic scoring and restructuring using Anthropic best practices

Continuous learning — hooks observe failures and prompt reflection, sibling synergy deepens analysis with history and tool discovery

Automatic history search — checks past sessions before web research, planning, and debugging, siblings deepen coverage

Automatic tool discovery across 17 sources — hooks search before planning and after errors, siblings avoid redundant searches

Context preservation with cross-session memory — hooks prompt compaction at high-impact moments, siblings enrich what gets saved

File checkpoint and recovery — auto-quicksaves before destructive commands, manual checkpoints for safe rollback

Use before WebSearch to check if you already have the answer, when stuck on an error to find past fixes, or when entering a familiar project to recall past sessions and file changes.

Cross-session memory — save insights after research, restore prior context before planning or research. Restore first, compact second.

Use when about to make risky changes — refactors, migrations, destructive bash commands, schema changes, or experimental approaches that might need reverting. Checkpoint project state for safe rollback.

Use when user asks "what exists for X?", before implementing custom MCP servers or plugins from scratch, or when browsing available tools — searches 19 sources and 15,000+ skills, plugins, and MCP servers in one query.

Use when dispatching subagents with non-trivial prompts, writing system prompts or skill descriptions, or when any prompt feels vague — scores 7 quality dimensions, auto-selects from 11 techniques, and rewrites with before/after scores.

Use after tool failures or user corrections to record patterns, and when accumulated observations need clustering into rule/hook/skill recommendations. Builds project-specific knowledge that persists across sessions.

Use after writing or editing plan files to surface reasoning as a scannable inline abstract. Extracts decisions, tradeoffs, and assumptions so the user can correct Claude's reasoning at a glance.