incluud Astro Documentation Lookup
When to Use
- User asks about Astro features, APIs, or configuration
- Need to verify correct syntax or usage patterns
- Looking up integration setup (Tailwind, MDX, adapters, etc.)
- Checking deployment or adapter documentation
- Answering "how do I..." questions about Astro
Instructions
Identify the topic from the user's question (e.g., "content collections", "view transitions", "SSR adapters")
Search the documentation using the Astro Docs MCP:
Use the search_astro_docs tool with relevant keywordsReview results and select the most relevant documentation sections
Synthesize the answer by:
- Providing a concise explanation
- Including relevant code examples from the docs
- Linking to the full documentation when helpful
Verify accuracy - If the MCP returns no results, try:
- Alternative search terms
- Breaking down complex queries
- Searching for related concepts
Search Tips
- Use specific terms: "content collections schema" vs just "collections"
- Include version-specific terms if relevant: "Astro 6 content layer" or "upgrade to v6"
- Search for error messages directly when debugging
- Look for integration names: "astro tailwind integration"
- For major upgrades, search the upgrade guide before relying on feature pages alone
Example Queries
| User Question | Search Terms |
|---|---|
| "How do I add Tailwind?" | tailwind integration setup |
| "What are content collections?" | content collections |
| "How do I deploy to Vercel?" | vercel adapter deployment |
| "View transitions not working" | view transitions troubleshooting |
| "How do I migrate content collections to Astro 6?" | upgrade to v6 content collections |
Response Format
When answering documentation questions:
- Brief answer - One or two sentences summarizing the solution
- Code example - Working snippet demonstrating the concept
- Key details - Important caveats or options to consider
- Further reading - Link to relevant docs section if complex topic