メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
Use when creating expert agents. Generates agent.md with frontmatter, hooks, required sections, and skill references.
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.
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.
Code quality validation with linters, SOLID principles, DRY detection, error detection, and architecture compliance across all languages.
Auto-review skill for expert agents. After coding, expert applies elicitation techniques to self-correct before sniper validation. Inspired by BMAD-METHOD.
| 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. |
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 config