Run any Skill in Manus with one click

astro-i18n

Stars0

Forks0

UpdatedMay 10, 2026 at 10:30

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

fusengine

fusengine/codex-agent

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

10 files

SKILL.md

readonly

name	astro-i18n
description	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.

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

More from this repository

same repository

impeccable

fusengine/codex-agent

Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, or colorize a frontend interface. Covers websites, landing pages, dashboards, product UI, components, forms, onboarding, empty states. Handles UX review, hierarchy, accessibility, responsive behavior, theming, typography, layout, color, motion, UX copy, design tokens. Also bolder/quieter redesigns, live browser iteration, ambitious visual effects.

2026-05-100

agent-creator

fusengine/codex-agent

Use when creating expert agents. Generates agent.md with frontmatter, hooks, required sections, and skill references.

2026-05-100

apex-methodology

fusengine/codex-agent

Systematic development workflow: Analyze → Plan → Execute → eLicit → eXamine. Use for ANY development task: features, bug fixes, refactoring, hotfixes. Triggers: "implement", "create", "build", "fix", "add feature", "refactor", "develop". Auto-detects project type (Laravel, Next.js, React, Swift) and loads framework-specific references. Enforces: files <100 lines, interfaces separated, SOLID principles, expert self-review, sniper validation.

2026-05-100

brainstorming

fusengine/codex-agent

Use when user requests creative work - creating features, building components, adding functionality, or modifying behavior. Activates BEFORE APEX Analyze phase to refine requirements through structured questioning.

2026-05-100

code-quality

fusengine/codex-agent

Code quality validation with linters, SOLID principles, DRY detection, error detection, and architecture compliance across all languages.

2026-05-100

elicitation

fusengine/codex-agent

Auto-review skill for expert agents. After coding, expert applies elicitation techniques to self-correct before sniper validation. Inspired by BMAD-METHOD.

2026-05-100

name	astro-i18n
description	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.

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