Generate Translations

This automates translation generation for Payload CMS projects, handling both core packages and plugins. It walks you through adding English keys to the right files, then runs OpenAI-powered scripts to generate all other language versions automatically. The skill knows the difference between core translations that live in packages/translations and plugin-specific ones that sit in their own folders. It'll even scaffold the full translation folder structure if a plugin doesn't have one yet. Honestly, this is the kind of workflow automation that saves you from maintaining dozens of language files by hand and keeps everything consistent across a large monorepo.

skills.sh installs: 578
GitHub stars: 45.7K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add payloadcms/payload --skill generate-translations --agent claude-code

Installs into .claude/skills of the current project.

Files

Translation Generation Guide

Payload has two separate translation systems:

Core Translations - for core Payload packages (packages/ui, packages/payload, packages/next)
Plugin Translations - for plugins (packages/plugin-*)

1. Core Translations
2. Plugin Translations
- Scaffolding New Plugin Translations
Important Notes

1. Core Translations

When to use: Adding translations to core Payload packages (packages/ui, packages/payload, packages/next)

Steps:

Add the English translation to packages/translations/src/languages/en.ts
- Add your new key/value to the appropriate section (e.g., authentication, general, fields, etc.)
- Use nested objects for organization
- Example:
```
export const enTranslations = {
  authentication: {
    // ... existing keys
    newFeature: 'New Feature Text',
  },
}
```
Add client key (if needed for client-side usage) to packages/translations/src/clientKeys.ts