Skip to content

Vibe Coding

Build with the Maverick AI SDK by describing what you want to an AI coding assistant. Two things make that work well: the SDK documentation MCP, which gives your assistant the SDK's guides, API reference and samples to search, and three skills, which teach it how to start a project, where everything lives, and how to use the API.

Both work with Claude Code and Codex, and the MCP works with any client that supports MCP servers.

Connect the documentation MCP

Add a Streamable HTTP server named mav2sdkdocs in your AI client's MCP settings:

https://mav2sdk-docs-mcp-905366563913.us-central1.run.app/mcp

It provides searchable guides, API references and Android, iOS and KMP samples - the same content as this portal, in a form your assistant can query while it writes code.

claude mcp add --transport http mav2sdkdocs https://mav2sdk-docs-mcp-905366563913.us-central1.run.app/mcp

Add a Streamable HTTP MCP server named mav2sdkdocs with the URL above in the client's MCP settings, then start a new session.

Note

Installing a skill does not connect the MCP. Connect it separately; the skills use it when it is there and fall back to the public documentation when it is not.

Install the skills

Skill Use it to
evs-mav2-sdk-quickstart Generate a Compose Multiplatform app (Android + iOS from one codebase, the default) or native Android/iOS apps, wired to the latest published SDK release, with your first HUD screen ready to build.
evs-mav2-sdk-assistant Find the SDK, platform packages, documentation, samples, developer keys and simulator setup.
evs-mav2-sdk-api-guide Connect glasses, draw text and controls, and use SDK services - input, resources, display, sensors, camera, audio and AR.

The skills are in the skills/ folder of the SDK repository. Copy a skill's folder into your client's skills directory and start a new session:

mkdir -p ~/.claude/skills
cp -R evs-mav2-sdk-quickstart ~/.claude/skills/

mkdir -p ~/.codex/skills
cp -R evs-mav2-sdk-quickstart ~/.codex/skills/

# Claude Code
New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null
Copy-Item -Recurse evs-mav2-sdk-quickstart "$HOME\.claude\skills\"
# Codex
New-Item -ItemType Directory -Force "$HOME\.codex\skills" | Out-Null
Copy-Item -Recurse evs-mav2-sdk-quickstart "$HOME\.codex\skills\"

Repeat for the other two. All three are meant for everyday SDK development, not only for a first project.

Try it

Ask your assistant in plain words, naming the skill:

Use $evs-mav2-sdk-quickstart to create a project named HelloGlasses for Android and iOS in ~/dev.

Use $evs-mav2-sdk-assistant to find the iOS SDK, docs and samples.

Use $evs-mav2-sdk-api-guide to connect my Android app and draw a text button on the glasses.

The quickstart skill ships with a Python generator (Python 3.10+). You can run it directly, with no AI client at all:

python3 evs-mav2-sdk-quickstart/scripts/new_mav2_project.py --name HelloGlasses --out ~/dev

py evs-mav2-sdk-quickstart\scripts\new_mav2_project.py --name HelloGlasses --out $HOME\dev

On Windows you can build and run the Android app; the iOS app needs a Mac with Xcode.

What you still provide

The generator creates the project; a few things are yours:

  • Developer key - an sdk.key for your app's package or bundle ID. Request one, and see API Keys.
  • GitHub token - with read:packages, for the SDK's Maven package. Needed for Android and for Compose Multiplatform (both platforms); a native iOS project uses the Swift Package, which needs none.
  • iOS - Xcode on a Mac, and a signing team for a phone build.

With no glasses at hand, run your app against the Glasses Simulator. It is a development tool - rendering can differ from the hardware - so validate the final experience on real glasses.