react-admin-i18n
Guidelines for internationalizing a react-admin or shadcn admin kit application. Use when adding i18n support, creating translation files, translating hardcoded English strings in JSX, or reviewing i18n PRs in a react-admin project. Covers namespace conventions, interpolation, pluralization, locale-aware formatting, and the full workflow for converting an English-only app to multi-language. Trigger this skill whenever the user mentions i18n, internationalization, translation, localization, locale switching, or multi-language in a react-admin or shadcn admin kit context — even if they just say "translate this component" or "add French support".
90
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that hits all the marks. It provides specific concrete actions, comprehensive trigger terms covering both technical jargon and natural user language, explicit 'Use when' and 'Trigger this skill whenever' clauses, and a well-defined niche at the intersection of i18n and react-admin/shadcn. The description uses proper third-person voice throughout and is thorough without being padded.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and concepts: adding i18n support, creating translation files, translating hardcoded English strings in JSX, reviewing i18n PRs, namespace conventions, interpolation, pluralization, locale-aware formatting, and converting an English-only app to multi-language. | 3 / 3 |
Completeness | Clearly answers both 'what' (guidelines for internationalizing, covering namespace conventions, interpolation, pluralization, locale-aware formatting, full workflow) and 'when' (explicit 'Use when...' and 'Trigger this skill whenever...' clauses with detailed trigger scenarios). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'i18n', 'internationalization', 'translation', 'localization', 'locale switching', 'multi-language', 'translate this component', 'add French support', 'react-admin', 'shadcn admin kit'. Includes both technical abbreviations and natural phrasings users would actually say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive by scoping to a specific intersection: i18n/internationalization within react-admin or shadcn admin kit projects. The combination of domain (i18n) and technology (react-admin/shadcn) creates a clear niche unlikely to conflict with general React skills or general translation skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality, deeply actionable skill with excellent concrete examples (❌/✅ patterns), a clear workflow, and a thorough PR checklist. Its main weakness is length—at ~400 lines it could benefit from splitting detailed sections (type safety, testing, i18nProvider setup) into referenced files, and trimming some explanatory text that Claude doesn't need. The actionability and workflow clarity are exemplary for a complex multi-step process.
Suggestions
Extract the Type-Safe Message Catalogs, i18nProvider Setup, Language Switcher, and Testing sections into separate referenced files (e.g., TYPES.md, PROVIDER_SETUP.md, TESTING.md) to reduce the main skill's token footprint.
Remove explanatory sentences that describe what things are rather than what to do (e.g., 'React-admin's translation system (Polyglot.js) uses a hierarchical key structure' and 'Localization of numbers and dates is already handled by JavaScript's built-in Intl methods')—Claude already knows these concepts.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite long (~400 lines) and includes some explanatory context that Claude likely already knows (e.g., explaining what Polyglot.js pluralization is, what Intl does). However, most content is actionable rules with concrete examples, so it's not egregiously verbose—just could be tightened in places. | 2 / 3 |
Actionability | Excellent actionability throughout. Every rule includes concrete ❌/✅ code examples that are executable and copy-paste ready. The i18nProvider setup, language switcher, type-safe catalogs, and test examples are all fully executable TypeScript/TSX code. | 3 / 3 |
Workflow Clarity | The high-level workflow is clearly sequenced (8 numbered steps), the component conversion process has a systematic checklist of locations to scan, and the PR checklist at the end serves as a comprehensive validation checkpoint. The workflow covers the full lifecycle from setup to audit. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear headings and sections, but it's entirely monolithic—everything is in one large file with no references to external documents for advanced topics. The type-safe catalog setup, testing section, and detailed rules could be split into separate reference files to keep the main skill leaner. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- marmelab/react-admin
- Commit
73b0971
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.