Content
78%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A lean, highly actionable policy skill: it teaches only project-specific conventions, gives real commands and APIs, and includes an explicit validation step. The main gaps are the absence of a concrete catalog-entry example and any guard-failure recovery guidance.
Suggestions
Add a minimal en-US.ts catalog snippet (one plain key and one plural key with a {{placeholder}}) so the core edit task is copy-paste concrete.
Add one line to the Verification section on what to do when `pnpm guard:i18n-catalogs` fails (fix missing keys/placeholders per its output, re-run).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with project-specific policy Claude cannot know (locale codes, plural suffix rules, RTL utility lists, exact commands) and explains no general concepts. Not a 5 because a few passages are tangled and could be leaner — e.g., the long `/settings` bullet packing the account-menu, ⌘,, Preferences-page, and language-icon facts into one parenthetical-laden paragraph. | 4 / 5 |
Actionability | Concrete throughout: exact paths (`app/i18n/en-US.ts`, `index.ts`), real commands (`pnpm guard:i18n-catalogs`, `pnpm typecheck`), specific APIs (`useT()`, `useFormatters()`, `buildSettingsRoute(page, sub?)`, `AppProviders i18n={{ catalog: i18nCatalog }}`), and exact locale/plural-suffix lists. Not a 5 because the core task — adding/editing a catalog entry — has no example snippet showing key structure or placeholder syntax. | 4 / 5 |
Workflow Clarity | The Rule section gives a clear ordered process — "update the English source catalog first, then update only the locale catalogs listed in `translations.locales`, and run the i18n guard" — with an explicit validation command and escalation guidance ("For broader changes, also run the affected template tests and `pnpm typecheck`"). Not a 5 because there is no error-recovery guidance (what to do when the guard fails) and the sequence is prose rather than explicit steps. | 4 / 5 |
Progressive Disclosure | No bundle files exist and none are needed: all content is core policy at appropriate inline density, organized into clean, navigable sections (Rule, Catalogs, UI Pattern, Plurals And Placeholders, RTL, Verification) with nothing buried or padded. Per the rubric's simple-skill guidance, well-organized sections with no need for external references warrant a 5. | 5 / 5 |
Total | 17 / 20 Passed |