Captures the user's project architecture to inform i18n implementation strategy.
## When to Use
**Called during i18n_checklist Step 1.**
The checklist tool will tell you when to call this. If you're implementing i18n:
1. Call i18n_checklist(step_number=1, done=false) FIRST
2. The checklist will instruct you to call THIS tool
3. Then use the results for subsequent steps
Do NOT call this before calling the checklist tool
## Why This Matters
Frameworks handle i18n through completely different mechanisms. The same outcome (locale-aware routing) requires different code for Next.js vs TanStack Start vs React Router. Without accurate detection, you'll implement patterns that don't work.
## How to Use
1. Examine the user's project files (package.json, directories, config files)
2. Identify framework markers and version
3. Construct a detectionResults object matching the schema
4. Call this tool with your findings
5. Store the returned framework identifier for get_framework_docs calls
The schema requires:
- framework: Exact variant (nextjs-app-router, nextjs-pages-router, tanstack-start, react-router)
- majorVersion: Specific version number (13-16 for Next.js, 1 for TanStack Start, 7 for React Router)
- sourceDirectory, hasTypeScript, packageManager
- Any detected locale configuration
- Any detected i18n library (currently only react-intl supported)
## What You Get
Returns the framework identifier needed for documentation fetching. The 'framework' field in the response is the exact string you'll use with get_framework_docs.