---
description: Search all memory systems — code structure (TotalRecall) + session history (Gemini Memory)
argument-hint: <what you're looking for>
---

Search across ALL memory systems to find: $ARGUMENTS

You have two memory systems available. Use BOTH in parallel for a comprehensive answer.

## Step 1: Search both systems simultaneously

**Gemini Memory** (session history, decisions, architecture reasoning):
- Call `gemini_memory_retrieve_context` with the project name derived from the current working directory (last folder segment, lowercased, spaces to hyphens)
- Query: "$ARGUMENTS"
- max_output_tokens: 5000

**TotalRecall** (code structure across all 42+ indexed projects):
- Call `recall_code_search` with query: "$ARGUMENTS"
- If you need relationship info (what calls what, imports, inheritance), also call `recall_code_graph`
- If you need to compare across projects, call `recall_code_cross_repo`

Call both systems in parallel — do NOT wait for one before calling the other.

## Step 2: Synthesize the results

Combine findings from both systems into a single, actionable answer:

1. **From Gemini Memory**: Past decisions, discussions, debugging history, architecture reasoning
2. **From TotalRecall**: Actual code locations, file paths, function signatures, cross-project patterns

Present the combined answer as:

### What I found

[Summary combining both sources — be specific about file paths, function names, and decisions]

### From session history (Gemini Memory)
[Relevant past conversations and decisions, if any]

### From code structure (TotalRecall)
[Matching code, files, patterns across projects, if any]

### Recommendation
[If the user is looking for guidance, recommend based on both historical context and current code state]

## Keeping the index fresh

After you make significant changes to a project (new files, major refactors, new modules), re-index so TotalRecall stays current:

- Call `recall_reindex_current` with the project path and name
- Example: `recall_reindex_current(project_path="E:\\Vibe_Coding\\SightLine", project_name="SightLine")`
- This takes 30-120 seconds depending on project size
- Do this at natural breakpoints (after completing a feature, before committing)
- Do NOT do this after every small edit — only after substantial changes

## Important rules

- Search BOTH systems, even if you think only one is relevant
- If one system returns nothing, that's fine — report what the other found
- Be specific: include file paths, function names, project names
- If TotalRecall finds code in another project that could be reused, say so
- If Gemini Memory has a past decision that's relevant, surface it
- Do NOT ask the user which system to search — search both automatically