agentleFS
clideyclidey/whodb/.agents/skills/add-translation/SKILL.md

add-translation

Skill5.1k starsChanged 3 days agoApache-2.0View on GitHub

Add or update English translation keys with proper localization placement

1 other project uses a version of this.

Trending

Less talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 3 mentionsMar 2026: 8 mentionsApr 2026: 4 mentionsMay 2026: 5 mentionsJun 2026: 6 mentionsJul 2026: 5 mentionsAug 2026: 6 mentionsSep 2026: 6 mentionsOct 2026: 9 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the clidey/whodb repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about clidey/whodb

The biggest 5 of 60 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 60

Talked about on GitHub, Bluesky and Hacker News (60 times).

On GitHub · 50

45 more on GitHub

On Bluesky · 7

2 more on Bluesky

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    Do not add or update non-English locale entries unless the user explicitly asks for translation.

    line 21
  2. Distinctive:

    Remove from YAML file

    line 53
  3. Distinctive:

    Leave other language entries untouched unless the user explicitly requested cleanup

    line 54

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Add Translation Keys

Quick Path (single key)

1. Determine Location

  • Shared across components → frontend/src/locales/common.yaml
  • Component-specific → frontend/src/locales/components/<name>.yaml or pages/<name>.yaml

2. Add en_US Entry Only

en_US:
  newKey: English text here
  parameterized: "Hello {name}, you have {count} items"

Do not add or update non-English locale entries unless the user explicitly asks for translation. Translation tooling is manual maintenance, not part of the default agent workflow.

3. Use in Component

const { t } = useTranslation('components/my-component');
// or for common keys, just use t('key') — they're auto-available

t('newKey')
t('parameterized', { name: userName, count: itemCount })

Pluralization

Add suffix variants:

en_US:
  items: "{count} items"
  items_one: "{count} item"

The count param triggers plural resolution automatically.

JSX in Translations

en_US:
  details: "See our {link} for info."
t('details', { link: <a href="/docs">{t('docsLink')}</a> })

Removing Keys

  1. Remove from YAML file
  2. Leave other language entries untouched unless the user explicitly requested cleanup

Verification

TypeScript does not check keys: t() accepts any string and a missing key renders as the key itself. Confirm each key used in the component exists in its YAML file or common.yaml, then build:

cd frontend && pnpm run build:ce

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.