i18n-inlang-localization

Automate machine translation for missing i18n messages by using the inlang CLI to detect untranslated strings and generate translations. This skill manages the workflow, validating project configurations and filling gaps without manual string entry.

Paraglide JS integrates with React and SSR frameworks by generating tree-shakeable, type-safe message functions. This ensures compile-time safety for localized strings, preventing runtime errors from missing translation keys in server-rendered components.

Yes, you can use inlang for URL localization and complex routing in TypeScript applications. This skill supports configuring localized URLs and complex routing patterns, ensuring consistent multi-language navigation across your web application.

The best way to validate localization configurations in CI/CD is using the inlang CLI for automated linting and project validation. This skill integrates into your pipeline to catch missing translations and configuration errors before deployment.

Paraglide JS works best when you initialize a new project configuration. This skill provides a dedicated slash-command workflow to initialize the setup, machine translate missing messages in your directory, and generate type-safe message files.