Retrieves authoritative documentation directly from the framework's official repository.
## When to Use
**Called during i18n_checklist Steps 1-13.**
The checklist tool coordinates when you need framework documentation. Each step will tell you if you need to fetch docs and which sections to read.
If you're implementing i18n: Let the checklist guide you. Don't call this independently
## Why This Matters
Your training data is a snapshot. Framework APIs evolve. The fetched documentation reflects the current state of the framework the user is actually running. Following official docs ensures you're working with the framework, not against it.
## How to Use
**Two-Phase Workflow:**
1. **Discovery** - Call with action="index" to see available sections
2. **Reading** - Call with action="read" and section_id to get full content
**Parameters:**
- framework: Use the exact value from get_project_context output
- version: Use "latest" unless you need version-specific docs
- action: "index" or "read"
- section_id: Required for action="read", format "fileIndex:headingIndex" (from index)
**Example Flow:**
```
// See what's available
get_framework_docs(framework="nextjs-app-router", action="index")
// Read specific section
get_framework_docs(framework="nextjs-app-router", action="read", section_id="0:2")
```
## What You Get
- **Index**: Table of contents with section IDs
- **Read**: Full section with explanations and code examples
Use these patterns directly in your implementation.
Connector