plugins/astro-expert/skills/astro-i18n/SKILL.md
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.
npx skillsauth add fusengine/agents astro-i18nInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Before ANY implementation, use TeamCreate to spawn 3 agents:
astro:i18n API and sitemap integrationAfter implementation, run fuse-ai-pilot:sniper for validation.
defaultLocale and routing strategiesgetRelativeLocaleUrl()Astro.currentLocale in components and pageshreflang alternate links via @astrojs/sitemapAstro's built-in i18n system provides:
src/pages/[locale]/astro:i18n| 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 |
| Template | When to Use | |----------|-------------| | i18n-config.md | Full i18n configuration | | locale-page.md | Page component with locale awareness | | language-switcher.md | Language switcher component |
getRelativeLocaleUrl() — never hardcode locale prefixes in linksAstro.currentLocale — read locale in components, not from URL manuallysrc/content/[type]/[locale]/@astrojs/sitemap with i18n option for SEOfallback to prevent 404s for missing translationsAstro.currentLocale)getRelativeLocaleUrl without configuring site in Astro configtesting
Copy self-audit and ban-lists — filler verbs/hype adjectives, slop placeholder names, fake-precise numbers, Title Case headlines, humor in error copy ('Oops!'), em-dash crutch, one copy register per page.
development
Logged-in web apps — dashboards, auth flows, settings, onboarding, data tables, command palettes, modals, toasts. Register `product`: density and glance-speed over marketing polish, no hero/CTA-tricks, every data surface covers empty/loading/error explicitly, tables and dataviz follow preattentive-processing rules.
development
Marketing sites, landing pages, campaign pages — register `brand` (design IS the product). Structure comes from the register's POV + a macrostructure pick, never from copying an inspiration site's section flow. Hero discipline, deviated section order, asymmetric grids, and a silhouette lookalike-test gate before ship.
development
Token-strategy core — OKLCH color rules, neutral tinting, accent-commitment levels, type scale, 8pt spacing grid, touch targets, and the canonical output format of design-system.md (the file the harness gates on). This is routing step 1 of design-method/SKILL.md — read it before design-web/design-webapp/design-ios/design-android, before picking or auditing a single color/type/spacing value.