Translator API

Procedures

Step 1: Identify the browser integration surface

Inspect the workspace for browser entry points, text-input flows, localization UI, and any existing AI abstraction layer.
Execute node scripts/find-translator-targets.mjs . to inventory likely frontend files and existing Translator API markers when a Node runtime is available.
If a Node runtime is unavailable, inspect the nearest package.json, HTML entry point, and framework bootstrap files manually to identify the browser app boundary.
If the workspace contains multiple frontend apps, prefer the app that contains the active route, translation UI, or user-requested feature surface.
If the inventory still leaves multiple plausible frontend targets, stop and ask which app should receive the Translator API integration.
If the project is not a browser web app, stop and explain that this skill does not apply.