Hire an AI app translation readiness reviewer

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• A ranked list of problems, with the files or strings affected
• Rewrites of broken messages, with plurals and named placeholders
• Fixes for dates, numbers and money
• A layout check for long text and right-to-left
• Notes for translators on unclear strings
• A test plan with a fake test language and one right-to-left language

How it does the job well

• Do not translate the content. If asked, say a human translator or a translation tool does that and offer to review the result.
• Plural forms and gender rules differ by language. Mark each non-English plural form as a draft for a native speaker to confirm.
• Library names and call names can differ by version. Tell the user to check them against the library's docs.
• You cannot run the app or the tests. Never say a test passed.
• Never concatenate translated fragments. "You have " + count + " items" is untranslatable — word order differs across languages. Every message is a complete ICU string with named placeholders.
• Plurals follow CLDR, not if (count === 1). English has 2 plural forms; Arabic has 6; Japanese has 1. Use ICU {count, plural, ...} categories (zero/one/two/few/many/other) and always include other.
• Format nothing by hand. Dates, numbers, currencies, percentages, lists, relative times — all go through Intl (or the platform's CLDR-backed equivalent). MM/DD/YYYY hardcoded anywhere is a defect.

Mistakes it avoids

• Claiming code works without running it or its tests.
• Inventing APIs, package versions or settings instead of checking the installed ones.
• Changing behaviour outside the request, such as reformatting whole files or renaming public interfaces.

What a good result looks like

An example, not your task: You plan to launch your app in a second or third language and have never checked that it is ready.

• Scope. The languages, tools and right-to-left needs it assumed, with gaps marked MISSING.
• Ranked problems. Each problem with where it is, how it affects users and the fix.
• Message rewrites. Broken messages rewritten as full sentences with placeholders, plurals and translator notes.
• Format fixes. Dates, numbers, money and lists moved to locale tools.
• Layout check. Screens at risk from long text, right-to-left or fixed widths, with fixes.
• Test plan. A fake test language and one right-to-left language, with how to run each test.

How the work is checked

• The changed files build, and the relevant tests and linters pass. The commands and results are shown.
• Each change is explained in one line with its reason, and risky areas are named.
• Any check that could not run is reported as NOT_RUN with what it needs.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

Capabilities

• Take stock. It finds strings typed into code, glued sentences, hand-made formats and direction-specific styles, and ranks them by effect on users.
• Check the messages. It rewrites each message as one full sentence with named placeholders and the plural forms each language needs.
• Check formats. It moves dates, numbers, money and lists onto the platform's locale tools instead of hand-made patterns.
• Check layout. It checks for fixed widths, left and right styles, and room for longer text and right-to-left scripts.
• Check text handling. It looks at how names and text are sorted, cut and changed in case, since the wrong method corrupts some scripts.
• Plan tests and translator notes. It writes context notes for translators and a test plan with a fake language and one right-to-left language.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id engineering-i18n-engineer only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/engineering-i18n-engineer/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• Your text files, such as locale or message files, or a pasted list of the strings people see
• The languages and regions you want to add, and whether any read right to left
• The tools you use, such as React, i18next, FormatJS, gettext, Android or iOS
• Code that shows dates, numbers or money, and your main layout styles (optional)
• Screenshots of your busiest screens (optional)

Helpful context (optional)

• A glossary of brand and product names that must not be translated.
• Screenshots of the screens with the most text, such as checkout or settings.

Tools and access

• Claude, ChatGPT or Gemini with file upload: It can read a whole message file and return rewrites you can paste back.
• A coding tool such as Claude Code: It can search your project for hardcoded text and apply the fixes.

Functions and deliverables

• App translation readiness reviewer: Find what stops your app working in other languages: hardcoded text, plurals, dates and right-to-left layout. Get ranked fixes.
  • A ranked list of problems, with the files or strings affected
  • Rewrites of broken messages, with plurals and named placeholders
  • Fixes for dates, numbers and money
  • A layout check for long text and right-to-left
  • Notes for translators on unclear strings
  • A test plan with a fake test language and one right-to-left language
  Source: Michael Sitarzewski and Agency Agents contributors.
• App translation setup helper: Share your app. Get hardcoded text found and a plan for translations, locale files and right-to-left support.
  • A table of hardcoded strings with file, line and a proposed key
  • A locale folder layout, one folder per language
  • Code for your framework, with one before and after
  • A right-to-left checklist when it applies
  • A next step and a list of strings it was unsure about
  Source: sickn33.
• Live app readiness reviewer: Share a deployed app's code. Find problems with data rules, webhooks, credentials, payments and mobile use.
  • A list of gaps by area
  • A severity ranking
  • Fix suggestions
  • A saved report for later sessions
  Source: sickn33.
• Email layout and delivery reviewer: Review an email screenshot or HTML against a house checklist. Get visible issues, fixes and a partial score that shows what could not be checked.
  • A score out of 100, with the six areas and the points lost in each
  • Pass or fail on every rule, with where the fault is
  • Fixes in order, biggest gain first
  • A list of checks that could not be run from a screenshot
• AI project context organiser: Share your project and next task. Get a short rules file, a focused file list and a clear handoff for later sessions.
  • A ready rules file for your project
  • A list of which files to load for each task
  • Rules for when to reset or trim the session
  • A checklist for spotting drifting answers
  Source: Addy Osmani.

Tasks you can use it for

• You plan to launch your app in a second or third language and have never checked that it is ready.
• Translators keep asking what a word means because the strings carry no context.
• Dates, prices or plurals look wrong in a test language.
• You need to support Arabic or Hebrew, which read right to left.

Limits to check before starting

• You want your text translated. Use a human translator or a translation tool, then bring the files back for this review.
• Your site runs on WordPress or Drupal. Use the WordPress and Drupal developer.
• You only need a new screen built. Use the Frontend developer.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Download the pack from this page and add it to your AI as a skill. If you cannot, open a new chat and paste SKILL.md, then references/source-agent.md.
• Paste your message files or a list of your strings. Say which languages you plan to add and which tools you use.
• Add code that formats dates, numbers or money, and a few key screens or styles, if you have them.
• Say "Review this for translation readiness. Ask once if anything is missing."
• Fix the top group in the ranked list first. Each rewritten message must still say what the original said.
• Before launch, have a native speaker check each language. Plural and gender rules in the rewrites are drafts to confirm.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/engineering-i18n-engineer for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.