agentleFS
lucasrafaldinilucasrafaldini/paperdeck/.agents/skills/add-locale/SKILL.md

add-locale

Skill1 starsChanged 47 days agoMITView on GitHub

Step-by-step workflow to add and synchronize a new internationalization locale in PaperDeck.

5 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions5 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 5

    1. polarsource/polar★ 10ksame name
    2. Kyome22/RunCat365★ 10ksame name
    3. Humanizr/Humanizer★ 9.9ksame name
    4. Swttch/swttch★ 322same name
    5. notum-cz/strapi-next-monorepo-starter★ 316same 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.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill whenever an agent is tasked with adding or updating a language translation dictionary in PaperDeck.

    line 8
  2. Very specific:

    Do not remove keys. Any missing key in the new file will automatically fall back to en.json, but for complete support all keys should be …

    line 23
  3. Distinctive:

    Ensure JSON is valid UTF-8 without BOM:

    line 30

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “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 Locale Skill

Use this skill whenever an agent is tasked with adding or updating a language translation dictionary in PaperDeck.

1. Identify Language Code

  • Determine the ISO 639-1 / BCP-47 tag (e.g., es for Spanish, fr for French, de for German, ja for Japanese).
  • Name the target file locales/<lang-code>.json.

2. Copy Base Structure from locales/en.json

  • locales/en.json is the canonical reference.
  • Maintain the three primary namespaces:
    1. meta: { "name": "Español", "locale": "es-ES", "currency": "EUR" }
    2. ui: all Electron desktop UI labels, buttons, forms, tooltips, dialogs.
    3. auth: CLI preflight and diagnostic messages.
    4. dashboard: strings rendered on the Kindle e-ink display.

3. Verify Key Completeness

  • Do not remove keys. Any missing key in the new file will automatically fall back to en.json, but for complete support all keys should be provided.
  • Preserve format parameters like {value}, {expiresAt}, {count}, {mode}.

4. Automatic Discovery

  • The app discovers translation files automatically from locales/. No TypeScript changes are necessary in src/.

5. Validate

  • Ensure JSON is valid UTF-8 without BOM:
    node -e "JSON.parse(require('fs').readFileSync('locales/<lang-code>.json', 'utf8'))"
  • Run tests:
    npm test

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.