Linked Issue

Closes #

Description

Adds a new Vibecoding documentation page (docs/vibecoding.mdx) — a single entry point for developers who want to use AI coding tools (Claude Code, Cursor, Windsurf) with Mem0's memory
layer.

Inspired by Honcho's vibecoding page, this page covers:

• Agent Skills — npx skills add command to teach coding assistants the Mem0 API
• LLM-friendly docs — link to llms.txt for instant context in any AI tool
• Claude Code Plugin — step-by-step setup for the OpenMemory plugin with persistent memory across sessions
• MCP Server Setup — tabbed setup for OpenMemory Hosted and Mem0 Platform MCP (Claude Desktop, Cursor, Windsurf)
• Universal Starter Prompt — a copy-pasteable prompt with verified URLs, code snippets, and architecture overview
• Go Deeper — card links to quickstarts, cookbooks, and API reference

Navigation changes in docs.json add the page to the Mem0 Platform, Open Source, and OpenMemory sidebar tabs under Getting Started.

All URLs and code snippets have been verified against the live docs and current codebase (mem0/client/main.py, mem0/memory/main.py, mem0-ts/src/client/mem0.ts).

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Refactor (no functional changes)
• Documentation update

Breaking Changes

N/A

Test Coverage

• I added/updated unit tests
• I added/updated integration tests
• I tested manually (describe below)
• No tests needed (explain why)

Manual testing:

• Verified all 7 external URLs resolve (docs.mem0.ai/*, github.com/mem0ai/mem0)
• Verified all code snippets match actual SDK method signatures (Python Platform MemoryClient, Python OSS Memory, TypeScript MemoryClient)
• Verified Mintlify components (<Steps>, <Tabs>, <CodeGroup>, <CardGroup>, <Card>, <Accordion>) match patterns used in existing docs
• Verified docs.json navigation changes place the page in Platform, Open Source, and OpenMemory tabs

Checklist

• My code follows the project's style guidelines
• I have performed a self-review of my code
• I have added tests that prove my fix/feature works
• New and existing tests pass locally
• I have updated documentation if needed