More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    LocForge Extract Lite: i18n for React

    1

    Extracts hardcoded React strings into react-i18next keys and manages en.json locale files.

    Free

    Security scanned
    LocForge Extract Lite: i18n for React

    LocForge Extract Lite: i18n for React

    Example session with this skill installed

    Extract all hardcoded strings from my components in /src/components and generate the en.json file. Use react-i18next conventions.

    • Read your context and instructions
    • Compiled the locforge extract lite
    • Generated the UI component

    I have scanned the /src/components directory. I identified 18 candidate strings across 4 files. I have replaced these strings with t() calls and updated your en.json file, ensuring all keys are sorted and existing translations are preserved.

    Localization Extraction Report

    FileStrings ExtractedStatusNotes
    src/components/Header.tsx3SuccessReplaced Nav links
    src/components/LoginForm.jsx8SuccessHandled placeholders and labels
    src/components/UserDashboard.tsx5SuccessHandled dynamic interpolation
    src/components/Footer.tsx2SuccessReplaced copyright text

    Skipped Strings:

    • console.log("Auth initialized"): Technical log.
    • data-testid="submit-btn": Testing attribute.
    • className="flex p-4": CSS class.

    Updated en.json

    {
      "auth": {
        "login": "Log In",
        "password_placeholder": "Enter your password",
        "username_label": "Username"
      },
      "common": {
        "cancel": "Cancel",
        "save": "Save"
      },
      "dashboard": {
        "welcome_user": "Welcome back, {{name}}!",
        "items_count_one": "{{count}} item",
        "items_count_other": "{{count}} items"
      },
      "navigation": {
        "home": "Home",
        "settings": "Settings"
      }
    }
    

    Next steps

    1. Review the generated keys in en.json to ensure the naming matches your preference.
    2. Verify the {{name}} interpolation in UserDashboard.tsx functions correctly with your data.
    3. To translate en.json, use LocForge: Translate src/locales/en.json into Spanish.

    Header.tsx

    TSX · React component

    Generated

    Example file from a real run - the skill writes it into your workspace.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Manual internationalization is a slow, error-prone process that clutters React components with hardcoded strings. This skill automates the extraction of UI text into react-i18next structures, ensuring consistent key naming and valid JSON output. It identifies user-facing text in JSX tags, placeholders, alt text, and aria-labels while ignoring technical strings like class names or URLs.

    What it does

    • Source analysis scans .jsx and .tsx files to find candidate strings for translation.
    • Smart extraction replaces hardcoded text with t('key') calls using standardized naming conventions.
    • Complexity handling converts string interpolation and concatenation into single keys with placeholders.
    • JSON management merges new keys into existing en.json files while preserving and sorting existing data.
    • Context awareness filters out non-UI strings such as log outputs, test IDs, and enum values.

    How it works

    1. Stack validation checks for React and react-i18next dependencies before proceeding.
    2. Safety check verifies the git status to prevent overwriting uncommitted work without permission.
    3. Key approval presents a sample of proposed translation keys for manual review and confirmation.
    4. Automated refactor rewrites components and updates the central locale file.
    5. Verification runs a final scan to report any remaining strings that require manual attention.

    Frameworks & tools

    Built specifically for React and react-i18next. Uses Python for scanning logic if available, falling back to file-system parsing.

    Why this beats prompting it yourself

    Standard prompts often miss attributes like aria-label or break interpolation logic by creating fragmented keys. This skill enforces a strict naming schema and ensures one sentence equals one key, preventing the common mistake of splitting translatable units.

    Use cases

    • Initial setup for a React project moving from single-language to multi-language support.
    • Component audits to find and extract hardcoded strings missed during development.
    • Pluralization refactors to convert manual count logic into proper i18next plural keys.

    Known limitations

    Supports React only, not Next.js or Vue. Requires react-i18next to be pre-installed in package.json. Requires a clean git working tree or explicit user override.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Translation & Localization.

    Supports React only. Requires react-i18next to be pre-installed. Only scans .jsx and .tsx files. Does not perform the initial i18next configuration setup.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 17 days ago

    • Free with an Agensi account

    Software
    Git

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Listed17 days ago

    What's inside

    Frequently Asked Questions

    Locforge Extract Lite identifies user-facing strings in React components and automatically replaces them with i18next `t()` calls while simultaneously updating your `en.json` file. It solves the tedious manual work of internationalization and prevents common errors like fragmented keys or missing aria-labels.

    This skill is specifically optimized for React (.jsx and .tsx) projects that use the react-i18next library. It requires a clean git working tree to ensure you can review and revert changes, and it currently does not support other frameworks like Vue or Next.js-specific setups.

    Unlike a basic AI prompt, this skill uses specialized logic to handle complex string interpolation and concatenation. It ensures that entire sentences are kept as single keys with placeholders rather than breaking them into nonsensical fragments that are impossible to translate.

    Yes, the skill includes a 'Key Approval' step where it presents a sample of proposed translation keys for your review. You can verify the naming conventions and the mapping before any automated refactoring of your source code begins.

    Locforge Extract Lite is designed to be context-aware, meaning it intelligently filters out non-UI strings such as console logs, test IDs, and enum values. This ensures your locale files stay clean and only contain text that users actually see.

    New in Translation & Localization

    Free