# Poe2arb Workflow

> Handle Flutter localization workflows backed by POEditor and poe2arb. Use when adding translations, syncing ARB files with POEditor, or when the user mentions poe2arb, POEditor, seed, or flutter gen-l10n.

- Skill: `leancodepl/poe2arb-workflow` (Agent Skill)
- Install (CLI): `npx skillmds@latest add leancodepl/poe2arb-workflow`
- Raw SKILL.md: https://api.skillmd.com/api/skills/leancodepl/poe2arb-workflow/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: leancodepl (https://skillmd.com/u/leancodepl)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/leancodepl/poe2arb-workflow

---


# POEditor and poe2arb Workflow

Keep the localization workflow aligned with the shared localization rules.

## What to keep true

- Keep translations in package-specific `app_<language_code>.arb` files.
- Never hardcode translations.
- Use translations only in the presentation layer, inside widgets.
- Access translations as `final s = l10n(context);`
- If other layers need localized text, map message models to localized values in the presentation layer.

## Workflow when adding translations

1. Add the required translation to all relevant `app_<language_code>.arb` files.
2. Run `flutter gen-l10n`.
3. Run `poe2arb seed` to upload the added translation to POEditor.

## Output expectations

- If asked to change translations, update the ARB files first.
- Clearly say whether `flutter gen-l10n` and `poe2arb seed` were run or still need to be run.