Index of every page on this site: llms.txt
All skills
github avatar

/next-intl-add-language

@f10fdb8 official
by githubgithub/awesome-copilot41k stars
5,399
Run it yourself

Add new language to a Next.js + next-intl application

Use this Skill: https://skilld.dev/gh/github/awesome-copilot/next-intl-add-language

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈19 tokens for metadata: the name and description. ≈161 when used: this file.

How this Skill uses context

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈78 characters, or 1.0%.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

This is a guide to add a new language to a Next.js project using next-intl for internationalization,

  • For i18n, the application uses next-intl.
  • All translations are in the directory ./messages.
  • The UI component is src/components/language-toggle.tsx.
  • Routing and middleware configuration are handled in:
    • src/i18n/routing.ts
    • src/middleware.ts

When adding a new language:

  • Translate all the content of en.json to the new language. The goal is to have all the JSON entries in the new language for a complete translation.
  • Add the path in routing.ts and middleware.ts.
  • Add the language to language-toggle.tsx.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning2mo5 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill provides standard instructions for adding a new language to a Next.js application using the next-intl library. It does not contain any executable code, network operations, or access to sensitive files.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • Runlayer8mo

    1/1 file flagged

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at f10fdb8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 9 months ago

README badge

README badge for github/awesome-copilot/next-intl-add-language

Adds a new language to a Next.js application using next-intl by creating translation files, updating routing configuration, and adding the language to the UI toggle component. Targets projects already using next-intl for internationalization with translations stored in a `./messages` directory.

Generated from the current SKILL.md.

Does this skill work with any i18n library or just next-intl?
Just next-intl. The skill assumes your Next.js project uses next-intl for internationalization and modifies next-intl-specific files like routing.ts and middleware.ts.
Where do I store the translation files?
All translations go in the ./messages directory. You translate en.json as a template and create a new language file in the same location.
What files do I need to update to add a new language?
Three files: routing.ts (add the locale path), middleware.ts (update middleware configuration), and language-toggle.tsx (add the language to the UI toggle). You also create a new translation JSON file in ./messages.

Generated from the current SKILL.md. These answers refresh after source changes.