agentleFS
Sign inStart free
DailybotHQDailybotHQ/deepworkplan-website/.agents/skills/add-language/SKILL.md

add-language

Skill15 starsChanged 5 months agoMITView on GitHub

Add a new language to the site end-to-end (scaffold → translate → native review → QA). Use when adding a locale beyond the active set.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Add a brand-new language to deepworkplan.com to full parity with English — UI strings + all content collections (methodology, spec, kit, …

    line 20
  2. Distinctive:

    Does NOT change the i18n architecture (registry, routing, middleware).

    line 29
  3. Very specific:

    Does NOT translate the canonical agent layer: /init.md, the skill, and the spec source stay English.

    line 30
  4. Very specific:

    Translate (pass 1): every string value in <code>.ts and the full prose of each content file, following the translation style guide: brand …

    line 42

“Common” is measured: kept by at least 6 in 10 of the 4 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

Skill: Add Language

Objective

Add a brand-new language to deepworkplan.com to full parity with English — UI strings + all content collections (methodology, spec, kit, pages) + agent .md endpoints — at native, professional quality. The site's i18n architecture is N-language ready: availability is derived from file presence, and routing, middleware, hreflang, sitemap, and the switcher all derive from the registry, so no route/middleware/registry plumbing is needed per language.

Non-Goals

  • Does NOT change the i18n architecture (registry, routing, middleware).
  • Does NOT translate the canonical agent layer: /init.md, the skill, and the spec source stay English; the bootstrap URL is never localized.

Procedure

  1. Register the code (only for a language not already in the 17-entry registry): add it to src/lib/language-codes.ts and add a LANGUAGES entry in src/lib/i18n.ts (name, nativeName, hreflang, ogLocale [underscore, e.g. pt_BR], dateLocale [hyphen, e.g. pt-BR], urlPrefix /<code>, flag).
  2. Scaffold the English-seeded skeleton: pnpm run i18n:scaffold <code> — creates src/lib/translations/<code>.ts and src/content/{methodology,spec,kit,pages}/<code>/ (49 files, English slugs).
  3. Translate (pass 1) every string value in <code>.ts and the full prose of each content file, following the translation style guide: brand "Broadsheet" voice, the canonical-English glossary, the do-not-translate list (brand, code, paths, tool names, the https://deepworkplan.com/init.md URL, English slugs), and the language's locale conventions (quotes, script, punctuation, casing). Translate only title/description/summary frontmatter; keep keys and order/lang/kind/section/icon.
  4. Native review (pass 2) — delegate to the i18n-guardian agent to fix naturalness, register, technical fidelity, and glossary consistency. Never ship a single-pass machine translation.
  5. Validate (all must pass):
    pnpm run i18n:check       # content parity + script sanity
pnpm run astro:check      # string-key parity (SiteTranslations interface)
pnpm run md:check:strict  # agent .md endpoints
pnpm run biome:check
pnpm run build
  6. Commit: feat(i18n): add full <Language> (<code>) translation.

Notes

  • For many languages at once, fan out one agent per language (each writes only its own disjoint files) — see the i18n expansion plan's Team Agents Configuration.
  • RTL languages (e.g. Arabic) additionally need RTL layout work — out of scope for this skill's baseline.

References

  • docs/I18N_GUIDE.md — the N-language model + add-a-language flow.
  • scripts/i18n/scaffold-language.mjs, scripts/i18n/check.mjs — tooling.
  • i18n-guardian agent — the native-review pass.
  • translate-sync skill — keeping existing languages in sync when EN changes.

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