# Verbaly

> i18n that feels like no setup: you write natural text in your code and the compiler extracts it into stable keys, type-safe params and per-locale catalogs. The runtime is ~3KB gzip with zero dependencies, and the whole cycle (init, write, extract, translate, review, check, render) lives in one tool.

Current version: 0.45.0 (npm: verbaly, MIT). Quick start: `npx verbaly init`, add the bundler plugin or framework integration (@verbaly/vite, @verbaly/react, @verbaly/vue, @verbaly/svelte, @verbaly/sveltekit, @verbaly/nuxt, @verbaly/next, @verbaly/astro, @verbaly/unplugin), write ``t`Hello ${name}` `` and run `npx verbaly extract`. Missing translations fail the build, and so do broken ones (a dropped placeholder, a lost tag, a flattened plural block); machine translations stay drafts until a human reviews them.

For coding agents: the MCP server `@verbaly/mcp` exposes the cycle as six tools (verbaly_doctor, verbaly_wrap, verbaly_extract, verbaly_status, verbaly_missing, verbaly_translate), each answering with structured output as well as text (`claude mcp add verbaly -- npx -y @verbaly/mcp`); an installable Agent Skill lives in the repository under skills/verbaly. Both are documented at https://verbaly-web.vercel.app/docs/guide/agents. Machine translations are always drafts and no agent tool can approve them.

## Start

- [What is Verbaly?](https://verbaly-web.vercel.app/docs/init/what-is): The idea in five minutes: write text in your code, the compiler does the rest
- [Getting started](https://verbaly-web.vercel.app/docs/init/start): Install, init and first translated text
- [Packages](https://verbaly-web.vercel.app/docs/init/packages): Every package in one page: runtime, CLI, bundler plugins, framework integrations and the MCP server

## Integrations

- [Plain HTML](https://verbaly-web.vercel.app/docs/frameworks/dom): Plain HTML with data-verbaly attributes, no framework
- [Vite](https://verbaly-web.vercel.app/docs/frameworks/vite): The Vite plugin: live extraction, virtual modules, build gate
- [React](https://verbaly-web.vercel.app/docs/frameworks/react): React hooks and Trans, plus Next.js App Router at #next
- [Next.js](https://verbaly-web.vercel.app/docs/frameworks/react#next): React hooks and Trans, plus Next.js App Router at #next
- [Vue](https://verbaly-web.vercel.app/docs/frameworks/vue): Vue composables and Trans, plus Nuxt at #nuxt
- [Nuxt](https://verbaly-web.vercel.app/docs/frameworks/vue#nuxt): Vue composables and Trans, plus Nuxt at #nuxt
- [Svelte](https://verbaly-web.vercel.app/docs/frameworks/svelte): Svelte 5 stores and Trans, plus SvelteKit at #sveltekit
- [Astro](https://verbaly-web.vercel.app/docs/frameworks/astro): Astro integration: extraction from .astro files and per-locale SSG

## Guides

- [Message format](https://verbaly-web.vercel.app/docs/guide/format): Message syntax: params, formats, plurals, rich text, escapes, ICU
- [URL strategy](https://verbaly-web.vercel.app/docs/guide/urls): Should the language live in the URL: the two strategies, what each costs in SEO, and what works on a SPA, a server and a static site
- [Server-side](https://verbaly-web.vercel.app/docs/guide/server): SSR and SSG: per-request locale, hydration without flashes, render
- [Translators & TMS](https://verbaly-web.vercel.app/docs/guide/translators): The human loop: export/import (XLIFF, CSV, PO), machine translation with review, mobile delivery
- [Coding agents](https://verbaly-web.vercel.app/docs/guide/agents): The agent channel: the MCP server and its six tools, the installable Agent Skill, and this index
- [Migrate from i18next](https://verbaly-web.vercel.app/docs/guide/migrate): Migrate from i18next step by step

## Reference

- [Runtime API](https://verbaly-web.vercel.app/docs/reference/api): Runtime API: createVerbaly, t, locale helpers, bindDom
- [CLI](https://verbaly-web.vercel.app/docs/reference/cli): Every CLI command and flag, plus the config file
- [Devtools](https://verbaly-web.vercel.app/docs/reference/devtools): The opt-in devtools overlay

## More

- [Changelog](https://verbaly-web.vercel.app/changelog): what each release added
- [GitHub](https://github.com/AronSoto/verbaly): source, issues and full release notes
- [npm](https://www.npmjs.com/package/verbaly): the published package