next-intl-skill

Name: next-intl-skill
Availability: InStock
Author: finstreet

Generate and apply German translation keys in de.json for next-intl projects.

1|Updated Oct 13, 2025

Search Tags:#codebase #localization #i18n #translations #next-intl #de.json

Ready to run

npx skills add https://github.com/finstreet/fe-claude-plugins --skill next-intl-skill

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: next-intl-skill
Source: https://github.com/finstreet/fe-claude-plugins/tree/main/plugins/automation/skills/next-intl
Command: npx skills add https://github.com/finstreet/fe-claude-plugins --skill next-intl-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers and content teams manage translations in Next.js projects using next-intl. It ensures text in the codebase uses proper translation keys, keeps de.json updated, and streamlines localization workflows to reduce manual toil.

Core Features & Use Cases

Translation key validation: Verify that all displayed text uses translation keys and that keys exist in the de.json files.
Centralized management: Update German translations in a single place to keep consistency across the app.
Use Case: When adding a new screen, generate required translation keys and populate de.json accordingly.

Quick Start

Provide a German translation for a new button label in the next-intl system by editing the de.json file and running a validation pass to ensure keys exist and references are correct.

Frequently Asked Questions about next-intl-skill

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

FAQPage Schema

How do I manage translations for a Next.js project using next-intl?▼

next-intl automates translation management by enabling you to define translation keys in your codebase and maintain centralized JSON files like de.json for German text. This ensures consistent localization across forms, pages, modals, and other components while reducing manual translation toil.

How do I generate and apply German translations in de.json for new screens?▼

Generate required translation keys based on reference documentation and feature specs, then populate de.json with German translations following prescribed response templates. Run validation to verify all keys exist and references are correct across your codebase.

Can I validate that all displayed text uses translation keys in next-intl?▼

Yes, translation key validation ensures every user-facing text references a proper key and that the corresponding entry exists in your de.json file. This prevents untranslated strings and maintains consistency across your Next.js application.

What's the workflow for keeping German translations synchronized across a Next.js codebase?▼

Read general-information and feature reference files, consult response templates, then output consistent translation keys and JSON structures to de.json. This centralized workflow keeps all German translations in one place and streamlines updates across forms, lists, pages, and task groups.

Do I need to manually maintain translation keys when adding new UI components?▼

No, next-intl automation generates translation keys and populates de.json based on reference documentation, reducing manual overhead. You define the component text once and the system outputs the proper key-value structure for downstream use.

What file format does next-intl use for storing translations?▼

next-intl uses JSON files like de.json to store translation key-value pairs. This structured format enables consistent management of German and other language translations across your Next.js project.