orbit-i18n

Audit WordPress plugin internationalization compliance for string wrapping and text domain consistency.

2|1|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/adityaarsharma/orbit --skill orbit-i18n
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orbit-i18n
Source: https://github.com/adityaarsharma/orbit/tree/main/skills/orbit-i18n
Command: npx skills add https://github.com/adityaarsharma/orbit --skill orbit-i18n

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of ensuring that a WordPress plugin is properly internationalized (i18n) before release, covering critical aspects like string wrapping, text domain matching, and POT file freshness.

Core Features & Use Cases

  • Internationalization Checks: Validates that every user-facing string is correctly wrapped for translation.
  • Text Domain Consistency: Ensures that the text domain in the plugin matches the plugin folder name.
  • Locale-Loading Hook Timing: Verifies that the locale is loaded at the correct time during plugin initialization.
  • Translator-Friendly Placeholders: Checks that placeholders use %1$s for consistent translation.
  • Pluralization and Context: Ensures correct pluralization and context disambiguation for translations.
  • Use Case: Before releasing a new version of your plugin, run this Skill to automatically audit and fix potential i18n issues.

Quick Start

Use the orbit-i18n skill to audit the i18n readiness of your plugin 'my-plugin'.

Frequently Asked Questions about orbit-i18n

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if my WordPress plugin is ready for internationalization?

WordPress plugin internationalization readiness is verified by auditing string wrapping, text domain consistency, locale-loading hook timing, translator-friendly placeholders, pluralization, and context disambiguation to ensure correct multilingual localization.

What does text domain consistency mean for WordPress plugin i18n?

Text domain consistency in WordPress plugin i18n means the text domain declared in your plugin code matches the plugin folder name, ensuring translation files load correctly during localization.

How do I fix locale-loading hook timing for a WordPress plugin text domain?

Fix locale-loading hook timing by verifying the text domain loads at the correct time during plugin initialization, ensuring translation files are available before user-facing strings render in WordPress.

Why do WordPress translation placeholders need to use %1$s format?

WordPress translation placeholders need %1$s format to be translator-friendly, allowing translators to reorder variables in localized strings for different language grammar structures during plugin internationalization.

When should I audit my WordPress plugin for i18n compliance?

Audit WordPress plugin i18n compliance before releasing a new version, ensuring every user-facing string is correctly wrapped for translation, pluralization is handled, and POT files are fresh for multilingual users.

Does this internationalization audit check pluralization and context disambiguation?

Yes, this internationalization audit checks pluralization and context disambiguation, ensuring WordPress plugin translations correctly handle singular and plural forms while distinguishing identical strings with different meanings.