Fix CodeGroup tabs syntax and simplify chat guide

- Replace Tabs.Container/Tabs.Content with CodeGroup component
- Use OpenAI SDK for chat interface examples
- Remove best practices, security, and use cases sections from guide
- Keep only essential setup and usage information

Author: tpayet

CLAUDE.md

@@ -0,0 +1,73 @@
+# CLAUDE.md
+
+This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+
+## Project Overview
+
+This is the official **Meilisearch Documentation** repository - a content-only repository for the documentation website of Meilisearch, an open-source search engine API. The documentation is built with Mintlify, written in MDX format, and deployed on Vercel.
+
+**Important**: This is a content-only repository. Local development is NOT possible as the website code lives elsewhere.
+
+## Common Development Commands
+
+```bash
+# Markdown linting
+npm run marklint       # Check markdown files for style issues
+npm run marklint:fix   # Auto-fix markdown issues
+
+# Prose linting with Vale
+npm run proselint      # Check prose quality and style
+```
+
+## Architecture and Structure
+
+### Content Organization
+- `/learn/` - Learning resources and conceptual guides
+- `/guides/` - Implementation guides for various technologies
+- `/reference/` - API reference documentation
+- `/snippets/samples/` - Reusable code samples (included via MDX)
+- `/assets/` - Images and datasets organized by feature/guide
+
+### Key Configuration Files
+- `docs.json` - Mintlify configuration (theme, navigation, search)
+- `.markdownlint.jsonc` - Markdown linting rules
+- `.vale/` - Prose style guidelines and custom vocabulary
+- `docs-scraper.config.json` - Meilisearch indexing configuration with OpenAI embeddings
+
+### Documentation Features
+- **Search**: Self-indexed using Meilisearch with semantic search via OpenAI embeddings
+- **Theme**: Dark/light mode support with custom branding
+- **Navigation**: Hierarchical structure defined in docs.json
+- **Code Samples**: Modular snippets system for consistent examples across languages
+
+## Writing Guidelines
+
+### Content Format
+- All documentation files use **MDX** format (Markdown with JSX support)
+- Code samples are stored separately in `/snippets/samples/` and included via MDX
+- Images must use **raw GitHub URLs** (not relative paths):
+  ```markdown
+  ![Description](https://raw.githubusercontent.com/meilisearch/documentation/main/assets/images/guide-name/image.png)
+  ```
+
+### Style Rules
+- **Capitalization**: Sentence-style for headings (except proper nouns like AWS, Docker)
+- **Spelling**: British English preferred
+- **Grammar**: Oxford comma usage
+- **Bold/Italics**: Use `*` for bold, `_` for italics
+- **First Person**: Avoid "I", "me", "my" unless in FAQs
+- **Accessibility**: Write for non-native English speakers
+
+### Contributing Process
+1. Check existing issues before creating new ones
+2. PRs should solve existing issues or fix small errors
+3. All code samples must run without errors
+4. Updates may require changes to multiple related pages
+5. Response required within 7 days for PR feedback
+
+## Important Notes
+
+- This repository contains **only content** - no build system or local preview
+- Changes are reviewed for accuracy, clarity, and code functionality
+- The documentation philosophy emphasizes being Efficient, Accessible, Thorough, and Open source
+- Vale prose linting enforces consistent style and terminology