agentleFS
Sign inStart free
johannesvedderjohannesvedder/flutter-localization-kit/skills/flutter-localization/SKILL.md

flutter-localization

Skill1 starsChanged 4 months agoMITView on GitHub

Manage Flutter ARB localization with a token-efficient CLI. Use when an agent must inspect, search, add, update, rename, delete, validate, find missing translations or usages, and regenerate Flutter localization files in a Flutter project.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. thiennc-tesoglobal/flutter-skills★ 16same name
    2. thienqo/flutter-skills★ 16same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the CLI for localization reads and every mutation.

    line 8
  2. Very specific:

    Run commands from the Flutter package containing pubspec.yaml and l10n.yaml, not a monorepo root.

    line 10
  3. Very specific:

    Never run q without search text or pipe search text to it.

    line 19
  4. Very specific:

    Search with q; use g only for exact keys.

    line 50
  5. Very specific:

    Check u before deleting or renaming.

    line 51
  6. Distinctive:

    Do not print prose from the CLI.

    line 55

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Flutter localization

Use the CLI for localization reads and every mutation. Do not load or rewrite complete ARB files unless diagnosing corruption.

Run commands from the Flutter package containing pubspec.yaml and l10n.yaml, not a monorepo root. Use installed l10n <command> when available. Otherwise use npx -y github:johannesvedder/flutter-localization-kit#v0.1.0 <command>.

Commands take positional arguments, not stdin, except x. Use q <text> for broad search and g <key> when the exact key is known:

l10n q login
l10n g login_page_title

Never run q without search text or pipe search text to it.

Protocol

  • i -> [[locales],arbDir,templateArb,generatedFile]
  • q <text> -> [[key,valueByLocale...],...]
  • g <key[,key...]> -> exact rows
  • m <locale> -> [missingKey,...]
  • u <key> -> [[dartFile,line],...]
  • v -> [1,fileCount,keyCount]
  • x reads mutation operations from stdin
  • z regenerates with flutter gen-l10n

Locale value order always follows i.

Mutation opcodes

Send one minified JSON array to x:

  • set: ["s","key",{"en":"Text","de":"Text"}]
  • delete: ["d","key"]
  • rename: ["r","old","new"]

Batch related mutations in one call. The CLI validates Flutter resource names and the complete batch before writing, rejects unknown locales and rename collisions, preserves @key metadata on rename, and runs flutter gen-l10n after changes. Failed writes restore original ARB bytes; failed generation also restores generated localization Dart bytes.

Success: [1,changedFileCount,generated]. Failure: [0,errorCode,optionalDetail]. Mutation errors use IN, OP, KEY, LOC, VAL, or EXISTS; ARB loading uses JSON, ARB, LOCALE, or TEMPLATE; filesystem writes use WRITE; generation uses GEN.

Workflow

  1. Run i once.
  2. Search with q; use g only for exact keys.
  3. Check u before deleting or renaming.
  4. Send one batched x payload.
  5. Report only changed keys, errors, and generation status.

Do not print prose from the CLI. Do not return full ARB content. Do not alter files outside the configured ARB directory; generation is the only allowed external side effect.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free