subagent official · GitHub

Lingo.dev Localization (i18n) Agent — GitHub Copilot subagent

Q: How do I install Lingo.dev Localization (i18n) Agent in GitHub Copilot?

Add the agent definition file to your repository at `.github/agents/lingodotdev-i18n.agent.md`.

Q: What does this subagent require to run?

It needs file access and terminal tools (`shell`, `read`, `edit`, `search`) plus an active SSE connection to the MCP server at `https://mcp.lingo.dev/main`.

Subagent that configures web application internationalization through a rigid step-by-step checklist. It inspects project code, implements i18n, and verifies builds.

Install into GitHub Copilot · Manually: put the files in place All methods and platforms ↓

.github/agents/lingodotdev-i18n.agent.md

Open on GitHub

What Lingo.dev Localization (i18n) Agent does

This subagent coordinates web application internationalization using an external checklist tool. The entire flow runs strictly through i18n_checklist: the agent fetches task requirements with done: false, completes the edits, and confirms the outcome with done: true before moving on. It never writes code ahead of the checklist.

Alongside standard file editing, search, and shell tools, the agent connects to an external MCP server at https://mcp.lingo.dev/main via SSE. Without a working network connection to this SSE endpoint, the agent cannot retrieve its task list and will stop working.

What it helps with

configure multi-language support in web applications step by step
fetch project-specific localization guides using an external checklist
validate code changes against project builds after adding translations
track localization milestones with evidence verification at each step

Example prompts for the agent

Configure internationalization for this web application and start the checklist
Set up multi-language support using the Lingo i18n checklist tool
Implement i18n in our project and verify the changes with a build

How to install Lingo.dev Localization (i18n) Agent

Manually: put the files in place

.github/agents/lingodotdev-i18n.agent.md

Manually: put the files in place

.claude/agents/lingodotdev-i18n.md

For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention. Copilot names tools its own way in the tools field: remove it or rewrite it for Claude Code

Manually: put the files in place

.codex/agents/lingodotdev-i18n.toml

Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

Manually: put the files in place

.cursor/agents/lingodotdev-i18n.md

Cursor also reads .claude/agents/

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about Lingo.dev Localization (i18n) Agent

How do I install Lingo.dev Localization (i18n) Agent in GitHub Copilot?

Add the agent definition file to your repository at .github/agents/lingodotdev-i18n.agent.md.

What does Lingo.dev Localization (i18n) Agent do?

It implements internationalization in web applications using a strict checklist tool. The subagent inspects the repository, applies necessary code changes, and validates them with project builds.

What does this subagent require to run?

It needs file access and terminal tools (shell, read, edit, search) plus an active SSE connection to the MCP server at https://mcp.lingo.dev/main.

Source text

lingodotdev-i18n.agent.md · MIT

---
name: Lingo.dev Localization (i18n) Agent
description: Expert at implementing internationalization (i18n) in web applications using a systematic, checklist-driven approach.
tools:
  - shell
  - read
  - edit
  - search
  - lingo/*
mcp-servers:
  lingo:
    type: "sse"
    url: "https://mcp.lingo.dev/main"
    tools: ["*"]
---

You are an i18n implementation specialist. You help developers set up comprehensive multi-language support in their web applications.

## Your Workflow

**CRITICAL: ALWAYS start by calling the `i18n_checklist` tool with `step_number: 1` and `done: false`.**

This tool will tell you exactly what to do. Follow its instructions precisely:

1. Call the tool with `done: false` to see what's required for the current step
2. Complete the requirements
3. Call the tool with `done: true` and provide evidence
4. The tool will give you the next step - repeat until all steps are complete

**NEVER skip steps. NEVER implement before checking the tool. ALWAYS follow the checklist.**

The checklist tool controls the entire workflow and will guide you through:

- Analyzing the project
- Fetching relevant documentation
- Implementing each piece of i18n step-by-step
- Validating your work with builds

Trust the tool - it knows what needs to happen and when.

Similar subagents

All subagents for Frontend and UI →

frontend-developer VoltAgent Community Subagent for building complete frontend applications with React 18+, Vue 3+, and Angular 15+. Handles component architecture, state management, testing, and accessibility. 40,905installs ui-ux-designer Seth Hobson This subagent creates interfaces, wireframes, and design systems. Use it for user flows, accessibility work, and consistent UI patterns. CX Codex 27,069installs fullstack-developer VoltAgent Community This subagent carries a feature across the database, API, and frontend layers. Use it when one change needs a consistent end-to-end implementation. 18,117installs javascript-pro Seth Hobson A subagent for modern JavaScript, async code, and Node.js APIs. Use it to debug event-loop issues, review complex patterns, and plan TypeScript migrations. CX Codex 4,974installs ui-designer VoltAgent Community Designs visual interfaces, builds component libraries, and creates handoff documentation. Ideal when code needs structured UI states and design tokens. 1,979installs ui-designer Seth Hobson Designs interfaces, components, and responsive layouts with implementation in mind. Use it when building screens, forms, tables, or a design system. CX Codex 1,979installs

From the same set861

The whole set →