Skill

astro-i18n

Use when implementing internationalization in Astro, configuring i18n routing, setting up locale strategies, using getRelativeLocaleUrl/getAbsoluteLocaleUrl, handling Astro.currentLocale, or adding hreflang tags with sitemap.

From fuse-astro

Install

Run in your terminal

npx claudepluginhub fusengine/agents --plugin fuse-astro

Tool Access

This skill uses the workspace's default tool permissions.

Supporting Assets

View in Repository

references/content-translation.md

references/fallback.md

references/helper-functions.md

references/routing-config.md

references/sitemap-hreflang.md

references/strategies.md

references/templates/i18n-config.md

references/templates/language-switcher.md

references/templates/locale-page.md

Skill Content

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

138.6k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

evaluation-methodology

1 file

Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.

plugin-eval

32.9k

Stats

Parent Repo Stars4

Parent Repo Forks0

Last CommitMar 17, 2026

Actions

View Source View Plugin View on GitHub View README

Astro i18n

Agent Workflow (MANDATORY)

Before ANY implementation, use TeamCreate to spawn 3 agents:

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