Wp I18n
Use when internationalizing WordPress plugins or themes: PHP gettext functions (__/esc_html__/etc.), JavaScript i18n (@wordpress/i18n), .pot/.po/.mo translation workflow, WP-CLI i18n commands, RTL stylesheet support, and multilingual plugin setup (Polylang/WPML).
Install
npx skills add morrealev/wordpress-manager --skill wp-i18ngit clone --depth 1 https://github.com/morrealev/wordpress-manager.git /tmp/wordpress-manager
mkdir -p ~/.claude/skills
cp -r /tmp/wordpress-manager/skills/wp-i18n ~/.claude/skills/wp-i18nPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# WP i18n ## When to use - Adding internationalization (i18n) to a WordPress plugin or theme - Preparing a plugin or theme for WordPress.org submission (i18n is required) - Generating `.pot` template files from source code - Adding JavaScript translations via `@wordpress/i18n` - Supporting right-to-left (RTL) languages such as Arabic, Hebrew, or Persian - Setting up a multilingual WordPress site with Polylang or WPML ## Inputs required - **Repo root** — path to the plugin or theme project directory - **Text domain** — the unique slug used in all gettext calls (matches the plugin/theme slug) - **Project kind** — `plugin` or `theme` (determines how text domain is loaded) - **Target languages** — locale codes for translations (e.g., `it_IT`, `de_DE`, `ar`) - **Whether JS translation is needed** — true if the project has JavaScript files with user-facing strings ## Procedure ### 0) Detect i18n status Run the detection script to assess the current state of internationalization: ```bash node skills/wp-i18n/scripts/i18n_inspect.mjs --cwd=/path/to/project node skills/wp-project-triage/scripts/detect_wp_project.mjs ``` The i18n inspection script outputs JSON with: - `textDomain` — the text domain declared in the plugin/theme header - `phpI18n` — count and distribution of PHP gettext function usage - `jsI18n` — whether `@wordpress/i18n` is installed and configured - `translationFiles` — existing .pot, .po, .mo, and .json files
Details
- Skill name
wp-i18n- Repository
- morrealev/wordpress-manager
- Path
skills/wp-i18n/SKILL.md- Repo updated
- 2 March 2026
FAQ
What does the Wp I18n skill do?
Use when internationalizing WordPress plugins or themes: PHP gettext functions (__/esc_html__/etc.), JavaScript i18n (@wordpress/i18n), .pot/.po/.mo translation workflow, WP-CLI i18n commands, RTL stylesheet support, and multilingual plugin setup (Polylang/WPML).
How do I install the Wp I18n skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add morrealev/wordpress-manager --skill wp-i18n. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Wp I18n popular?
It lives in morrealev/wordpress-manager, which has 9 GitHub stars and 1 forks.
Related skills
Wordpress Router
9morrealev/wordpress-manager
“Use when the user asks about WordPress — whether development (plugins, themes, blocks, REST API) or operations (deploy, audit, backup, migrate, content management). Classifies the task and routes to the correct development or operational skill/agent.”
Wp Accessibility
9morrealev/wordpress-manager
Use when improving WordPress accessibility: block accessibility (ARIA, keyboard navigation), theme accessibility (landmarks, skip links, color contrast), interactive component accessibility, media accessibility (alt text, captions, transcripts), and automated/manual a11y testing with WCAG 2.2 compliance.
Wp Alerting
9morrealev/wordpress-manager
This skill should be used when the user asks about "alerting", "alerts", "Slack notifications", "email alerts", "monitoring alerts", "threshold alerts", "health reports", "escalation", "incident notifications", "uptime alerts", "error alerts", "performance alerts", "scheduled reports", or mentions setting up notification channels for WordPress monitoring events.
Wp Local Env
9morrealev/wordpress-manager
Use when the user wants to work with a local WordPress development environment — WordPress Studio, LocalWP, or wp-env. Handles environment detection, site lifecycle, WP-CLI proxy, REST API access, symlink workflows, database operations, and preview/share.
Wp Headless
9morrealev/wordpress-manager
Use when building headless/decoupled WordPress architectures: choosing between REST API and WPGraphQL, headless authentication (JWT, application passwords, NextAuth), CORS configuration, frontend framework integration (Next.js, Nuxt, Astro), content webhooks, and ISR/SSG strategies.
Auto Scope
9borkweb/skills
Scopes a coding task before implementation — names the handful of files actually relevant (read/edit these), the areas to leave alone, and any open scope questions, so work doesn't start by reading the whole repo. Fires proactively at the start of substantive, multi-file, or unfamiliar-area work; stays silent on single-file edits, one-line fixes, questions, and continued work in an area already scoped this session. Use when beginning a feature, bug fix, or refactor that could plausibly touch several files or an area not yet seen this session.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.