How do I install the I18N skill?

Run npx skillmds@latest add launch52-ai/i18n in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with I18N?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

launch52-ai (@launch52-ai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

I18N by launch52-ai — Agent Skill

Name: I18N
Author: launch52-ai

I18N

Audit Flutter code for hardcoded strings, write clear user-friendly text following UX guidelines, and migrate strings to i18n files. Use when checking localization, finding hardcoded text, improving string clarity, writing error messages, button labels, or any user-facing text.

launch52-ai 08e2266 5 files · 53.6 KB Updated Sep 17, 2026

File contents

i18n - Localization & UX Writing

Ensure all user-facing text is localized and crystal clear. Every string should be understandable by a 10-year-old or non-native English speaker.

When to Use This Skill

Checking for hardcoded strings
Writing or improving user-facing text
Creating error messages, button labels, confirmations
Migrating strings to i18n files
Reviewing string quality

Quick Reference

The Golden Rules

Be specific, not vague - "Could not save photo" not "Error occurred"
Use plain words - "Sign in" not "Authenticate"
Buttons complete "I want to ___" - "Delete photo" not "OK"
Errors say what to do - "Check your connection and try again"
No confusing dialogs - Never [Cancel] [OK] on a cancel confirmation

File Structure

lib/
├── core/i18n/
│   ├── common.i18n.yaml        → t.common.*
│   └── translations.g.dart     → Generated
└── features/{feature}/i18n/
    └── {feature}.i18n.yaml     → t.{feature}.*

Commands

# Audit for hardcoded strings
dart run .claude/skills/i18n/scripts/check.dart --audit

# Audit specific feature
dart run .claude/skills/i18n/scripts/check.dart --audit auth

# Generate missing i18n files
dart run .claude/skills/i18n/scripts/check.dart --generate

# Regenerate translations
dart run build_runner build --delete-conflicting-outputs

Workflow

1. Audit

dart run .claude/skills/i18n/scripts/check.dart --audit {feature}

Look for: Text('...'), title:, hintText:, label:, SnackBar messages, Dialog content.

2. Evaluate & Improve

Check each string against ux-writing-guide.md. Use patterns from examples.md.

3. Add to i18n File

Create/update lib/features/{feature}/i18n/{feature}.i18n.yaml with proper strings.

4. Replace in Code

// Before: Text('Welcome back')
// After:  Text(t.auth.login.title)

5. Regenerate

dart run build_runner build --delete-conflicting-outputs

Guides

Guide	Use For
setup-guide.md	Initial slang setup, build.yaml, file structure
ux-writing-guide.md	UX writing principles, patterns
examples.md	Before/after examples by scenario

Checklist

A 10-year-old would understand it
Names the specific thing (photo, message, account)
If error: says what happened AND what to do
If button: completes "I want to ___"
If confirmation: buttons clearly show outcomes
No jargon (credentials, authenticate, invalid, terminate)

Related Skills

/a11y - Accessibility labels (add to accessibility: section in i18n files)

---name: i18ndescription: Audit Flutter code for hardcoded strings, write clear user-friendly text following UX guidelines, and migrate strings to i18n files. Use when checking localization, finding hardcoded text, improving string clarity, writing error messages, button labels, or any user-facing text.---# i18n - Localization & UX WritingEnsure all user-facing text is localized and crystal clear. Every string should be understandable by a 10-year-old or non-native English speaker.## When to Use This Skill- Checking for hardcoded strings- Writing or improving user-facing text- Creating error messages, button labels, confirmations- Migrating strings to i18n files- Reviewing string quality## Quick Reference### The Golden Rules1. **Be specific, not vague** - "Could not save photo" not "Error occurred"2. **Use plain words** - "Sign in" not "Authenticate"3. **Buttons complete "I want to ___"** - "Delete photo" not "OK"4. **Errors say what to do** - "Check your connection and try again"5. **No confusing dialogs** - Never [Cancel] [OK] on a cancel confirmation### File Structure```lib/├── core/i18n/│ ├── common.i18n.yaml → t.common.*│ └── translations.g.dart → Generated└── features/{feature}/i18n/ └── {feature}.i18n.yaml → t.{feature}.*```### Commands```bash# Audit for hardcoded stringsdart run .claude/skills/i18n/scripts/check.dart --audit# Audit specific featuredart run .claude/skills/i18n/scripts/check.dart --audit auth# Generate missing i18n filesdart run .claude/skills/i18n/scripts/check.dart --generate# Regenerate translationsdart run build_runner build --delete-conflicting-outputs```## Workflow### 1. Audit```bashdart run .claude/skills/i18n/scripts/check.dart --audit {feature}```Look for: `Text('...')`, `title:`, `hintText:`, `label:`, SnackBar messages, Dialog content.### 2. Evaluate & ImproveCheck each string against [ux-writing-guide.md](ux-writing-guide.md). Use patterns from [examples.md](examples.md).### 3. Add to i18n FileCreate/update `lib/features/{feature}/i18n/{feature}.i18n.yaml` with proper strings.### 4. Replace in Code```dart// Before: Text('Welcome back')// After: Text(t.auth.login.title)```### 5. Regenerate```bashdart run build_runner build --delete-conflicting-outputs```## Guides| Guide | Use For ||-------|---------|| [setup-guide.md](setup-guide.md) | Initial slang setup, build.yaml, file structure || [ux-writing-guide.md](ux-writing-guide.md) | UX writing principles, patterns || [examples.md](examples.md) | Before/after examples by scenario |## Checklist- [ ] A 10-year-old would understand it- [ ] Names the specific thing (photo, message, account)- [ ] If error: says what happened AND what to do- [ ] If button: completes "I want to ___"- [ ] If confirmation: buttons clearly show outcomes- [ ] No jargon (credentials, authenticate, invalid, terminate)## Related Skills- `/a11y` - Accessibility labels (add to `accessibility:` section in i18n files)

Frequently asked questions