How do I install the Astro I18N skill?

Run npx skillmds@latest add fusengine/astro-i18n in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Astro I18N safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Astro I18N?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Astro I18N free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Astro I18N?

fusengine (@fusengine) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Astro I18N by fusengine — Agent Skill

Name: Astro I18N
Rating: 4.5 (4 reviews)
Author: fusengine

File contents

Also covers translating Content Collections per locale and adding hreflang alternate links via @astrojs/sitemap's i18n option for SEO. Does not cover general SEO meta tags beyond hreflang (astro-seo) or the Content Layer API itself (astro-content) — this skill focuses specifically on locale routing and URL generation.

Astro i18n

Agent Workflow (MANDATORY)

Before ANY implementation, spawn 3 agents in parallel, one Agent call each with a name:

fuse-ai-pilot:explore-codebase - Analyze existing routing, content collections, and locale files
fuse-ai-pilot:research-expert - Verify latest Astro i18n docs via Context7/Exa
mcp__context7__query-docs - Check astro:i18n API and sitemap integration

After implementation, run fuse-ai-pilot:sniper for validation.

Overview

When to Use

Building multilingual Astro sites with locale-prefixed URLs
Configuring defaultLocale and routing strategies
Generating locale-aware links with getRelativeLocaleUrl()
Reading Astro.currentLocale in components and pages
Adding hreflang alternate links via @astrojs/sitemap
Translating content using Content Collections per locale

Built-in i18n (Astro 3.5+)

Astro's built-in i18n system provides:

File-based locale routing via src/pages/[locale]/
Routing strategies for URL prefix behavior
URL helper functions from astro:i18n
Middleware-based routing logic
Fallback locale configuration

Reference Guide

Concepts

Topic	Reference	When to Consult
Routing config	routing-config.md	Setup and config options
Strategies	strategies.md	prefix-always vs prefix-other-locales
Helper functions	helper-functions.md	getRelativeLocaleUrl and all helpers
Content translation	content-translation.md	Translating content collections
Sitemap hreflang	sitemap-hreflang.md	SEO alternate links
Fallback	fallback.md	Missing translation fallback

Templates

Template	When to Use
i18n-config.md	Full i18n configuration
locale-page.md	Page component with locale awareness
language-switcher.md	Language switcher component

Best Practices

Use getRelativeLocaleUrl() — never hardcode locale prefixes in links
Astro.currentLocale — read locale in components, not from URL manually
Content Collections per locale — organize translated content in src/content/[type]/[locale]/
Sitemap hreflang — always configure @astrojs/sitemap with i18n option for SEO
Fallback locales — configure fallback to prevent 404s for missing translations

Forbidden

Hardcoding locale strings in URL paths
Parsing the URL manually to detect locale (use Astro.currentLocale)
Skipping hreflang configuration for SEO-sensitive sites
Using getRelativeLocaleUrl without configuring site in Astro config

---name: astro-i18ndescription: Use when implementing i18n in Astro — locale routing strategies, getRelativeLocaleUrl/getAbsoluteLocaleUrl, Astro.currentLocale, or hreflang with sitemap.---<objective>Implements Astro's built-in i18n system (Astro 3.5+): file-based locale routing under `src/pages/[locale]/`, `defaultLocale` and routing-strategy configuration (prefix-always vs prefix-other-locales), URL helper functions from `astro:i18n` (`getRelativeLocaleUrl`, `getAbsoluteLocaleUrl`), reading `Astro.currentLocale` in components, and fallback-locale configuration to avoid 404s on missing translations.Also covers translating Content Collections per locale and adding `hreflang` alternate links via `@astrojs/sitemap`'s `i18n` option for SEO. Does not cover general SEO meta tags beyond hreflang (astro-seo) or the Content Layer API itself (astro-content) — this skill focuses specifically on locale routing and URL generation.</objective># Astro i18n## Agent Workflow (MANDATORY)Before ANY implementation, spawn 3 agents in parallel, one `Agent` call each with a `name`:1. **fuse-ai-pilot:explore-codebase** - Analyze existing routing, content collections, and locale files2. **fuse-ai-pilot:research-expert** - Verify latest Astro i18n docs via Context7/Exa3. **mcp__context7__query-docs** - Check `astro:i18n` API and sitemap integrationAfter implementation, run **fuse-ai-pilot:sniper** for validation.---## Overview### When to Use- Building multilingual Astro sites with locale-prefixed URLs- Configuring `defaultLocale` and routing strategies- Generating locale-aware links with `getRelativeLocaleUrl()`- Reading `Astro.currentLocale` in components and pages- Adding `hreflang` alternate links via `@astrojs/sitemap`- Translating content using Content Collections per locale### Built-in i18n (Astro 3.5+)Astro's built-in i18n system provides:- File-based locale routing via `src/pages/[locale]/`- Routing strategies for URL prefix behavior- URL helper functions from `astro:i18n`- Middleware-based routing logic- Fallback locale configuration---## Reference Guide### Concepts| Topic | Reference | When to Consult ||-------|-----------|-----------------|| Routing config | [routing-config.md](references/routing-config.md) | Setup and config options || Strategies | [strategies.md](references/strategies.md) | prefix-always vs prefix-other-locales || Helper functions | [helper-functions.md](references/helper-functions.md) | getRelativeLocaleUrl and all helpers || Content translation | [content-translation.md](references/content-translation.md) | Translating content collections || Sitemap hreflang | [sitemap-hreflang.md](references/sitemap-hreflang.md) | SEO alternate links || Fallback | [fallback.md](references/fallback.md) | Missing translation fallback |### Templates| Template | When to Use ||----------|-------------|| [i18n-config.md](references/templates/i18n-config.md) | Full i18n configuration || [locale-page.md](references/templates/locale-page.md) | Page component with locale awareness || [language-switcher.md](references/templates/language-switcher.md) | Language switcher component |---## Best Practices1. **Use `getRelativeLocaleUrl()`** — never hardcode locale prefixes in links2. **`Astro.currentLocale`** — read locale in components, not from URL manually3. **Content Collections per locale** — organize translated content in `src/content/[type]/[locale]/`4. **Sitemap hreflang** — always configure `@astrojs/sitemap` with `i18n` option for SEO5. **Fallback locales** — configure `fallback` to prevent 404s for missing translations---## Forbidden- Hardcoding locale strings in URL paths- Parsing the URL manually to detect locale (use `Astro.currentLocale`)- Skipping hreflang configuration for SEO-sensitive sites- Using `getRelativeLocaleUrl` without configuring `site` in Astro config

Frequently asked questions

Astro I18N