Skip to content
TrustedSkillsbeta
Back to all skills

I18N Frontend Implementer

Checked
patricio0312rev·vlatest·frontend·MIT

Automatically translates and implements internationalization (i18n) for frontend components based on provided translation files.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add patricio0312rev/skills --skill i18n-frontend-implementer -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

patricio0312rev

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned patricio0312rev/skills at 79ea6af485.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
79ea6af485
Manifest
frontend/i18n-frontend-implementer/SKILL.md
Scanned
1 file, 41 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill automates the implementation of internationalization (i18n) for frontend components using libraries like next-intl or react-i18next. It facilitates translating and integrating text content within applications, enabling support for multiple languages. The skill guides users through core setup steps including library installation, dictionary creation, provider configuration, and the use of translation keys with hierarchical namespaces.

When to use it

  • You're building a new frontend application and want to design it with internationalization in mind from the start.
  • You have an existing frontend application that needs to support multiple languages.
  • You need to translate text content within your application, including handling plurals and formatting dates/numbers according to locale-specific rules.
  • You're looking for a structured approach to managing translations using hierarchical namespaces.

Key capabilities

  • Supports internationalization with next-intl or react-i18next.
  • Provides guidance on setting up translation dictionaries (e.g., locales/en.json, locales/es.json).
  • Facilitates the use of hierarchical namespaces for organizing translations.
  • Enables pluralization support within translations.
  • Supports date, number, and currency formatting based on locale.

Example prompts

  • "Implement i18n using next-intl."
  • "Show me how to translate 'Home' to Spanish in my application."
  • "How do I handle pluralization in my translations?"

Tips & gotchas

  • The skill assumes you have a basic understanding of frontend development and the chosen internationalization library (e.g., next-intl or react-i18next).
  • Follow best practices such as using namespaces, extracting all text to translation files, and supporting RTL languages for comprehensive i18n support.