nuxt-i18n
Nuxt i18n internationalization module for locale routing, lazy-loaded translations, SEO, browser detection, and multi-domain setups. Use when working with @nuxtjs/i18n, locale switching, translated routes, or i18n composables.
Best use case
nuxt-i18n is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Nuxt i18n internationalization module for locale routing, lazy-loaded translations, SEO, browser detection, and multi-domain setups. Use when working with @nuxtjs/i18n, locale switching, translated routes, or i18n composables.
Teams using nuxt-i18n should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/nuxt-i18n/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How nuxt-i18n Compares
| Feature / Agent | nuxt-i18n | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Nuxt i18n internationalization module for locale routing, lazy-loaded translations, SEO, browser detection, and multi-domain setups. Use when working with @nuxtjs/i18n, locale switching, translated routes, or i18n composables.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
Nuxt i18n is an internationalization module for Nuxt powered by Vue i18n. It provides locale-based routing, lazy-loaded translations, browser language detection, SEO metadata, and multi-domain locale support. > The skill is based on @nuxtjs/i18n v10.x, generated at 2026-03-28. ## Core | Topic | Description | Reference | |-------|-------------|-----------| | Configuration | Module setup, locales, Vue I18n config, key options | [core-configuration](references/core-configuration.md) | | Routing | Strategies, custom route paths, ignoring localized routes | [core-routing](references/core-routing.md) | ## Features | Topic | Description | Reference | |-------|-------------|-----------| | Detection & Switching | Browser detection, lang switcher, locale fallback, cookies | [features-detection-switching](references/features-detection-switching.md) | | SEO | useLocaleHead, hreflang, canonical links, OpenGraph | [features-seo](references/features-seo.md) | | Lazy Loading | Lazy-loaded translations, multiple files, dynamic API loading | [features-lazy-loading](references/features-lazy-loading.md) | | Per-Component | i18n custom blocks in SFCs, local scope translations | [features-per-component](references/features-per-component.md) | ## Advanced | Topic | Description | Reference | |-------|-------------|-----------| | Domains | Different domains, multi-domain locales, runtime env vars | [advanced-domains](references/advanced-domains.md) | | Server & Hooks | Server-side translations, runtime hooks, module integration, layers | [advanced-server-hooks](references/advanced-server-hooks.md) | ## API | Topic | Description | Reference | |-------|-------------|-----------| | API Reference | Composables, components, helper functions, instance properties | [api-reference](references/api-reference.md) | ## Full Documentation For details beyond these references, fetch the complete official documentation: - **llms.txt** (overview): https://i18n.nuxtjs.org/llms.txt - **llms-full.txt** (full docs): https://i18n.nuxtjs.org/llms-full.txt
Related Skills
nuxt
Nuxt full-stack Vue framework with SSR, auto-imports, and file-based routing. Use when working with Nuxt apps, server routes, useFetch, middleware, or hybrid rendering.
nuxt-ui
Build UIs with @nuxt/ui v4 — 125+ accessible Vue components with Tailwind CSS theming. Use when creating interfaces, customizing themes to match a brand, building forms, or composing layouts like dashboards, docs sites, and chat interfaces.
nuxt-seo
Nuxt SEO meta-module with robots, sitemap, og-image, schema-org. Use when configuring SEO, generating sitemaps, creating OG images, or adding structured data.
use-zod
Answer questions about the Zod schema validation library and help build schemas, parsers, refinements, transforms, codecs, and error formatters. Use when developers: (1) ask about Zod APIs like `z.object`, `z.string`, `z.array`, `z.union`, `z.discriminatedUnion`, `parse`, `safeParse`, `z.infer`; (2) define request/response/form schemas in TypeScript; (3) handle `ZodError` or customize error messages; (4) migrate between Zod v3 and v4 (entry-point split, `formatError` → `treeifyError`/`prettifyError`, unified `error` param replacing `message`/`errorMap`). Triggers on: "zod", "z.object", "z.string", "z.array", "z.union", "z.infer", "z.input", "z.output", "ZodError", "$ZodError", "safeParse", "parseAsync", "z.codec", "treeifyError", "prettifyError", "flattenError", "discriminatedUnion", "zod/v4", "zod/v3", "zod/mini", "z.coerce", "superRefine".
workflow
Creates durable, resumable workflows using Vercel's Workflow SDK. Use when building workflows that need to survive restarts, pause for external events, retry on failure, or coordinate multi-step operations over time. Triggers on mentions of "workflow", "durable functions", "resumable", "workflow sdk", "queue", "event", "push", "subscribe", or step-based orchestration.
wpds
Use when building UIs leveraging the WordPress Design System (WPDS) and its components, tokens, patterns, etc.
wp-wpcli-and-ops
Use when working with WP-CLI (wp) for WordPress operations: safe search-replace, db export/import, plugin/theme/user/content management, cron, cache flushing, multisite, and scripting/automation with wp-cli.yml.
wp-rest-api
Use when building, extending, or debugging WordPress REST API endpoints/routes: register_rest_route, WP_REST_Controller/controller classes, schema/argument validation, permission_callback/authentication, response shaping, register_rest_field/register_meta, or exposing CPTs/taxonomies via show_in_rest.
wp-project-triage
Use when you need a deterministic inspection of a WordPress repository (plugin/theme/block theme/WP core/Gutenberg/full site) including tooling/tests/version hints, and a structured JSON report to guide workflows and guardrails.
wp-plugin-development
Use when developing WordPress plugins: architecture and hooks, activation/deactivation/uninstall, admin UI and Settings API, data storage, cron/tasks, security (nonces/capabilities/sanitization/escaping), and release packaging.
wp-playground
Use for WordPress Playground workflows: fast disposable WP instances in the browser or locally via @wp-playground/cli (server, run-blueprint, build-snapshot), auto-mounting plugins/themes, switching WP/PHP versions, blueprints, and debugging (Xdebug).
wp-phpstan
Use when configuring, running, or fixing PHPStan static analysis in WordPress projects (plugins/themes/sites): phpstan.neon setup, baselines, WordPress-specific typing, and handling third-party plugin classes.