frontend-translation-management

frontend-translation-management is a cursor rule for coding agents from CharLEE-X/effect-cursor-rules. It costs 0 tokens per session (1,456 once invoked), scanned A, original, MIT.

A frontend rule set defines how an application stores and uses text for multiple languages, such as English, German, and French. Internationalization means preparing software to support different languages and regions.

In plain words
What is it for?
It is for organizing translation files, naming translation keys consistently, and ensuring buttons, messages, errors, and changing interface states have translations.
Why use it?
It prevents visible text from being hardcoded in components or translated inconsistently, including during states such as loading, saving, or submitting.

Cursor rule

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/charlee-x/effect-cursor-rules/frontend-translation-management
Clone the repo
git clone --depth 1 https://github.com/CharLEE-X/effect-cursor-rules

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for frontend-translation-management

README.md
[![agentmods](https://agentmods.dev/badge/rules/charlee-x/effect-cursor-rules/frontend-translation-management.svg)](https://agentmods.dev/rules/charlee-x/effect-cursor-rules/frontend-translation-management)
Your own site
<a href="https://agentmods.dev/rules/charlee-x/effect-cursor-rules/frontend-translation-management"><img src="https://agentmods.dev/badge/rules/charlee-x/effect-cursor-rules/frontend-translation-management.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,456 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01456
Opus 5 $0.00000 $0.00728
Sonnet 5 $0.00000 $0.00291
Haiku 4.5 $0.00000 $0.00146

Measured 5d ago against content hash e072de964fec, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

frontend-translation-management scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

rules/frontend-translation-management.mdc · 269 lines

How it starts

The opening of the file, as written. The whole thing — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Frontend Translation Management

Overview

Maintain consistent translation practices across the frontend application to ensure proper internationalization and user experience.

Translation File Structure

apps/frontend/public/locales/
├── en/translation.json          # English (primary)
├── de/translation.json          # German
├── fr/translation.json          # French
└── [lang]/translation.json      # Other languages

Translation Key Naming Conventions

✅ CORRECT Patterns

// Hierarchical structure
"blog.status.published"
"user.profile.edit"
"common.loading"
"error.validation.required"

// Action-based keys
"button.save"
"button.cancel" 
"button.delete"

// State-based keys
"common.loading"
"common.saving"
"common.updating"
"form.submitting"

❌ WRONG Patterns

// Hardcoded text in components
<Button>Save</Button>
<span>Loading...</span>

// Inconsistent key naming
"saveBtn"
"save_button"
"SAVE_BUTTON"

// Missing translations for dynamic states
{isLoading ? "Loading..." : "Save"}

Required Translation Categories

Common States

{
  "common": {
    "loading": "Loading...",
    "saving": "Saving...",
    "updating": "Updating...",
    "deleting": "Deleting...",
    "submitting": "Submitting...",
    "processing": "Processing...",
    "success": "Success",
    "error": "Error",
    "retry": "Retry"
  }
}

Form States

{
  "form": {
    "submitting": "Submitting...",
    "validating": "Validating...",
    "saved": "Saved",
    "unsaved": "Unsaved changes"
  }
}

Button Actions

{
  "button": {
    "save": "Save",
    "cancel": "Cancel",
    "delete": "Delete",
    "edit": "Edit",
    "create": "Create",
    "update": "Update"
  }
}

Component Translation Patterns

✅ CORRECT Implementation

// Using loading states with translations
const { t } = useTranslation()
const isLoading = fetcher.state === 'submitting'

return (
  <Button disabled={isLoading}>
    {isLoading ? t('common.updating') : t('button.save')}
  </Button>
)

// With loading spinner
return (
  <Button disabled={isLoading}>
    {isLoading && <Spinner className="mr-2" />}
    {isLoading ? t('common.saving') : t('button.save')}
  </Button>
)

Read the full file on GitHub · 269 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 5d ago First seen · 269 lines · 1,456 tokens per session scan A e072de964fec

Subscribe to this mod's changes

frontend-translation-management is a cursor rule published in the GitHub repository CharLEE-X/effect-cursor-rules (6 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,456 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.