agentleFS
Sign inStart free
vasceannievasceannie/slopgate/.cursor/rules/i18n-arb.mdc

slopgate / rules

Cursor rule1 starsChanged 51 days agoMITView on GitHub

ARB-based localization standards — ARB as the single cross-platform source of truth for UI strings

We split this i18n-arb.mdc into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When ARB files exist in the project, they are the single source of truth for all user-facing strings — regardless of target platform.

    line 11

≈ “Common” is an estimate: at least 1 in 5 of the 6,350 Cursor rule 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
i18n-arb.mdc
---
description: "ARB-based localization standards — ARB as the single cross-platform source of truth for UI strings"
globs: "**/*.arb"
alwaysApply: false
---

<!-- Generated by oh-my-agent. Source: .agents/rules/i18n-arb.md -->

# ARB-Based Localization

When ARB files exist in the project, they are the **single source of truth** for all user-facing strings — regardless of target platform. A build step generates the platform-specific artifacts from ARB (e.g. JSON for web, generated Dart for Flutter).

1. **Never hardcode UI strings** — all user-visible text must come from ARB files (`*.arb`)
2. **Edit ARB first** — when adding or changing UI text, update the ARB file, then run the i18n build
3. **Build after changes** — run the project's i18n build task (e.g. `mise i18n:build`, or `dart run build_runner build` in a Flutter package) to regenerate localized output (JSON for web, generated Dart, etc.). Prefer the `mise` task when one exists.
4. **Generated output is never hand-edited** — change the ARB and rebuild; treat the emitted JSON/Dart as derived artifacts
5. **Base locale** — the primary ARB file (e.g., `app_en.arb`) is the reference; other locales derive from it
6. **Key naming** — use `camelCase` keys describing the purpose, not the content: `loginButton` not `clickHere`
7. **Placeholders** — use ICU message syntax for interpolation: `"greeting": "Hello, {name}!"`
8. **Do not translate keys** — ARB keys are identifiers, always in English

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