docs-search

# AI Maestro Documentation Search

## CRITICAL: AUTOMATIC BEHAVIOR - READ THIS FIRST

**THIS IS NOT OPTIONAL. THIS IS YOUR DEFAULT BEHAVIOR.**

When the user gives you ANY instruction or task, you MUST FIRST search documentation for:
- **Function signatures** - What are the parameters and return types?
- **Class documentation** - What methods and properties exist?
- **API documentation** - How should this endpoint work?
- **Code comments** - What did the author intend?

**DO NOT:**
- Start implementing before checking documentation
- Assume you know the function signature without checking
- Skip doc search because "it's a simple task"
- Wait for the user to ask you to check docs

**ALWAYS:**
- Search docs IMMEDIATELY when you receive a task
- Search for terms and concepts the user mentions
- Check documentation before calling unfamiliar functions
- Look for patterns before creating new components

### The Rule: Receive Instruction → Search Docs → Then Proceed

```
1. User asks you to do something
2. IMMEDIATELY search docs for relevant context
3. NOW you know the correct signatures and patterns
4. NOW you can implement correctly the first time
```

**Example - User asks to modify a service:**
```bash
# IMMEDIATELY run:
docs-search.sh "PaymentService"
docs-find-by-type.sh class
```

**Example - User mentions a function:**
```bash
# IMMEDIATELY run:
docs-search.sh "validateUser"
docs-search.sh --keyword "authenticate"
```

---

## Available Commands

All commands auto-detect your agent ID from the tmux session.

### Search Commands
| Command | Description |
|---------|-------------|
| `docs-search.sh <query>` | Semantic search through documentation |
| `docs-search.sh --keyword <term>` | Keyword/exact match search |
| `docs-find-by-type.sh <type>` | Find docs by type (function, class, module, etc.) |
| `docs-get.sh <doc-id>` | Get full document with all sections |
| `docs-list.sh` | List all indexed documents |
| `docs-stats.sh` | Get documentation index statistics |