fantasia-i18n

Organize Vue i18n locale modules and TypeScript message schemas.

401|56|Updated Jan 30, 2021
One-click install
npx skills add https://github.com/vishiri/fantasia-archive --skill fantasia-i18n
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fantasia-i18n
Source: https://github.com/vishiri/fantasia-archive/tree/main/.cursor/skills/fantasia-i18n
Command: npx skills add https://github.com/vishiri/fantasia-archive --skill fantasia-i18n

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manages vue-i18n messages and locale structure for Fantasia Archive. Use when adding or changing user-facing strings, locale files under src/i18n, or markdown-backed documents wired into i18n.

Core Features & Use Cases

  • Centralized locale registry and merges each locale module.
  • TypeScript augmentation for global i18n message schema in src/boot/i18n.ts.
  • Markdown documents integrated into i18n workflow via special hooks.
  • Clear organization for en-US and other locales, including component/dialog strings.
  • Storybook-friendly mocks/imports to avoid markdown coupling in Storybook stories.

Quick Start

Update locale files under src/i18n to add or modify translations, then run the build/lint tasks to validate integration.

Frequently Asked Questions about fantasia-i18n

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I organize Vue i18n translations for multiple locales?

Organize Vue i18n translations by maintaining locale files under the src/i18n directory and merging each locale module through a centralized registry to ensure consistent user-facing strings across the application.

How do I integrate markdown-backed documents into the Vue i18n workflow?

Integrate markdown-backed documents into the Vue i18n workflow by using special hooks that wire markdown content into the localization structure, while leveraging Storybook-friendly mocks to avoid markdown coupling in stories.

Does vue-i18n require TypeScript augmentation for global message schemas?

Vue-i18n requires TypeScript augmentation in src/boot/i18n.ts to define the global i18n message schema, ensuring type-safe translations and proper locale module exports across en-US and other locales.

What is the best way to manage locale menus and dialogs in a Vue localization setup?

Manage locale menus and dialogs by centralizing component and dialog strings within structured locale modules, ensuring clear organization for en-US and other locales throughout the Vue localization setup.

Why are my Storybook stories breaking when importing markdown translations?

Storybook stories break from markdown coupling because the markdown imports create hard dependencies; use Storybook-friendly mocks and imports to decouple the markdown content and avoid integration errors.

Do I need vue-i18n v9 to set up TypeScript augmentation for locale modules?

Setting up TypeScript augmentation for locale modules requires vue-i18n v9, along with proper configuration in src/boot/i18n.ts, to correctly merge locale registry exports and validate global message schemas.