What Flows just did
Based on your request to build Add Internationalization (i18n) to Existing App, Flows created 6 implementation stages and 28 checks.
You asked for: Add full internationalization support for English, Spanish, and French, including a language selector that persists the user’s choice across sessions.. Flows generated 6 stages because the application requires Use i18next and react-i18next for translation management; Provide translation JSON files for en, es, fr with at least five UI keys; Replace hardcoded UI strings with the translation function. Each stage tells your AI builder what to do, tests whether it actually worked, and gives a repair instruction when it fails. These checks are designed to catch: AI inserts placeholder strings like "TODO" instead of real translations; AI generates component code missing required imports or the useTranslation hook; AI forgets to call localStorage.setItem when changing language.
Example failure
The form reported success, but no database record was created.
What Flows does
Flows detects the failure, generates a repair instruction, reruns the test, and stores the passing evidence.
Stages — Plan → Build → Test → Fix → Prove → Ship
6 stages · 28 checks · progressive disclosure — open a stage for details
Copy to external builder
Copies a prompt for Claude/Cursor/etc. Records prompt_copied only — not execution, commits, or checks.
Execute through Oort
Requires Sign in with Oort + a provider connection (BYOK). Keys stay on Oort. A model name in the dropdown is not the same as a live connection.
Next
Check off: i18next appears in package.json dependencies
Add a proof note on each check — a checkbox alone is weak proof.
Probes & advanced tools are under “More verification tools”. Experience level: Settings.
Project (saved with proof)
Project binding: Unbound — complete project binding before trusting this run · missing repositoryUrl, repositoryStartCommit, environment, stack
More verification tools (probes, timeline, adapters)Show
App persistence (create → read → assert token)
Body template: {"probe":"{{token}}","title":"flows-probe-{{token}}"}. Needs CORS-readable public create/list endpoints (or inconclusive). Badge only when create→read→refresh finds the token (detects false success).
Two-account authorization (User B cannot see/change User A)
Authorization evidence source: Cross-account ownership test (trust level 5/6). These are not equivalent. Unauthenticated probe alone is weaker (source: unauthenticated API probe). Tokens stay in this browser session only — not uploaded to Flows servers.
Generated edge-case tests (review / approve)
- api_probe Submitting the form empty is rejected with a clear error
- api_probe Each required field can be omitted and fails validation
- api_probe Malformed email is rejected
- api_probe Malformed phone is rejected when phone is collected
- api_probe Duplicate submission does not create two records
- api_probe Double-click submit creates only one record
- false_success_probe Failed request does not show success
- browser_automation Refresh during submission does not leave corrupt state
- api_probe Oversized input is rejected
- api_probe Unsafe strings do not execute or break storage
- api_probe Logged-out users cannot open protected pages
- api_probe Protected API rejects requests without credentials
- api_probe Expired session cannot mutate data
- browser_automation Logout in one tab invalidates mutations from another
- cross_account_probe User B cannot see or change User A’s data
- cross_account_probe Participant cannot call coach/admin endpoints
Generated from this route’s signals — you approve; you do not invent security tests.
Content probe (GET body contains text)
In-product content probe reads response text when CORS allows — not full DOM/click automation. Playwright script is optional and external.
Proof strength
thin · 0/100
Heuristic from notes + probes + gates — not a production certification.
Verification adapters
- ● Deploy URL probe · idle
- ● API path probe · idle
- ● Authz probe (unauth → 401/403) · idle
- ● Browser persistence · idle
- ● App persistence (create→read) · idle
- ● Content / body text probe · idle
- ○ In-product Playwright DOM · not embedded (download external script)
Filled circles = available here. Empty = not shipped. Probes are not a production audit. Adapter docs
Step 1 of 6
Not startedIntegrate i18n library
Add a robust internationalization library to provide translation support.
The app is a React project using JavaScript/JSX. We will use i18next and react-i18next.
Flows keeps plan, checks, failures, and next steps connected
Your AI tool writes or changes the code
Repository grounds the plan only after inspect
Checks always carry a validation tier
How this plan was created
Plan from project details
Flows creates steps using the goal, requirements, stack, platform, and details you provide.
- Project description
- Selected template / route
- User-entered stack
- Constraints and notes
- Add Internationalization (i18n) to Existing App
No repository inspection implied. Connect and inspect a codebase to ground steps in real files.
Codebase access
Checking GitHub…
Or paste a repository URL manually
Use these instructions in Claude, ChatGPT, Cursor, Emergent, or another builder.
1. Add i18next and react-i18next as dependencies using the project's package manager (e.g., npm install i18next react-i18next). 2. In the src directory, create a file named i18n.js. 3. In i18n.js, import i18next, initReactI18next, and set up i18next.init with: language: 'en', fallbackLng: 'en', resources: {}, and use initReactI18next. 4. Export the configured i18next instance (or simply run the init code). 5. Ensure i18n.js is imported at the top level of the app (e.g., in index.js) so the configuration runs before any component renders. Do not include placeholder comments; provide real, executable code.
Project context
Copies the project goal, technical details, current step, previous progress, and checks so your AI tool understands what it is working on.
Expected after this step
i18n.js file exists, i18next is listed in package.json, and the file initializes i18next with default language 'en' and fallback.
Should not happen
- ✕AI inserts placeholder strings like "TODO" instead of real translations
- ✕AI generates component code missing required imports or the useTranslation hook
- ✕AI forgets to call localStorage.setItem when changing language
- ✕AI leaves hardcoded UI text that should be translated
Verify gate — prove this step works before continuing
Do not move on until every check is true. Add proof notes — a checked box alone is weak proof. Checks are manual by default; deploy/API probes live under “More verification tools” and do not auto-check boxes.
Do not continue if…
- !AI inserts placeholder strings like "TODO" instead of real translations
- !AI generates component code missing required imports or the useTranslation hook
- !AI forgets to call localStorage.setItem when changing language
- !AI leaves hardcoded UI text that should be translated
- !AI provides only mock UI screenshots rather than executable JSX/JS code
Repair path — if this step fails
Use the Repair Prompt when a verify gate fails. Loop: Detected → Diagnosed → Repair issued → Changed → Retested → Resolved
Show repair prompt textShow
The AI omitted the real i18next initialization or left placeholder comments. Provide a complete src/i18n.js with proper imports, i18next.init call configuring language 'en' and fallbackLng, and an export or side‑effect import in index.js.
Your notes for this step
Definition of Done
Final route-level requirements. Manual checks — separate from per-step verify gates. Completing step gates does not auto-check these. Route completion is not a production-ready claim.