explain

# Learn Quest Concept Explanation

The user has requested a learning explanation.

## Available Tools

You can and SHOULD use these tools during explanation:

| Tool | When to Use |
|------|-------------|
| **WebSearch** | Frameworks, libraries, version-specific, best practices, trends |
| **Grep/Glob** | User asks about "my code", "this project", "our implementation" |
| **Read** | Need to show specific file content from user's codebase |

## Search Decision Rule

**"Would this be the same 10 years ago and 10 years from now?"**

**YES → Explain directly (no search):**
- Data structures (Array, Tree, Graph, Hash Table)
- Algorithms (Sorting, BFS/DFS, Binary Search, Recursion)
- CS fundamentals (Big O, Memory, Process vs Thread, TCP/IP)
- Language basics (Closure, Hoisting, Inheritance, Polymorphism)
- Design patterns (Singleton, Factory, Observer, MVC)

**NO → Search first:**
- Framework/library features (React, Next.js, Vue, etc.)
- Version-specific changes ("React 19", "TypeScript 5.x")
- Best practices, trends ("2025 recommended pattern")
- Tools (Vite, Turbopack, Bun)
- Anything with version numbers or years

## Configuration Check

Read settings from `~/.learn-quest/config.json` or `./.learn-quest/config.json`:
- **level**: bronze/silver/gold/platinum/diamond
- **language**: en/ko
- **features.quiz**: true/false

If config file doesn't exist, use defaults: level=silver, language=en, quiz=false

## Handling Ambiguous Requests

When the request is vague or could mean multiple things:

1. Make your best guess based on context
2. Provide the explanation
3. End with: "If you meant something else, let me know!" (or Korean equivalent based on language setting)

Example:
- User: "explain hooks"
- Ambiguous: React hooks? Git hooks? Lifecycle hooks?
- Action: Assume React hooks (most common), explain, then ask if they meant something else

## Mode Detection

### Mode A: With argument (`/learn-quest:explain <concept>`)

Examples:
- `/learn-quest:explain React hooks`
- `/l