Who it is forA small team localizing a product website into new languages and worried about layouts breaking in translated text.
The problemTranslation is often added late, so layouts and formatting fail once longer or right-to-left text arrives.
The outcomeA first contract that names target locales, with gates for layout expansion, right-to-left rendering, plurals, and locale formatting.
What you need first
- A copy of the Agent-Forge repository from GitHub
- A coding agent of your choice
- A written brief describing the site or page you want to build
- Someone available to act as an independent reviewer for the gate checks
Steps
- Read the multilingual guidance in /docs and the playbook stages in /playbook.
- List the target locales in the first contract in /contracts.
- Require string extraction by contract, not by accident, in the contract's scope.
- Add gates in /gates for right-to-left rendering, pluralization categories, and locale formatting for dates, numbers, and currency.
- Test layouts against text expansion and record the decisions in /ledger.
Prompt for your agent
Using the Foreman Continuum repo (JamesBuciaIt3A/Agent-Forge), write a contract for a website that must support <target> locales. The contract must require string extraction and list gates for right-to-left rendering, pluralization, and locale formatting. Verify that each gate names a check a reviewer can run on the rendered page.
Caveat. The README describes multilingual guidance as part of the playbook but does not provide localization starter kits yet, which it lists only as roadmap proposals.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for JamesBuciaIt3A/Agent-Forge and "Plan a multilingual site with locale rules in contracts"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer