Skip to content
SkillCheatSheet Sign in

translation-strings

An AI agent skill from thedaviddias/Front-End-Checklist, scored 50 out of 100 by code.

50/ 100D

Code score by group

  • Spec20/20
  • Description7/20
  • Procedure0/15
  • Done criteria4/15
  • Resources7/10
  • Scripts2/8
  • Safety7/7
  • Upkeep3/5

It loses the most points in Procedure (15), the group that checks whether the steps are numbered, read the context first and say what to do when something fails.

What the author says it does

Use when reviewing a codebase for internationalisation readiness, setting up an i18n library, or preparing strings for a new locale.

This is the description in the skill's own SKILL.md, written by its author, not by SkillCheatSheet.

Repository
thedaviddias/Front-End-Checklist
Folder
skills/translation-strings
License
MIT
GitHub stars
74,709
SKILL.md lines
46
Other files
1

Add translation-strings to your agent

npx skills add thedaviddias/Front-End-Checklist --skill translation-strings

The command uses the open skills CLI. A skill is instructions and scripts your agent will follow, so read it first: open the folder on GitHub at the commit that was scored.

More skills from thedaviddias/Front-End-Checklist

  1. find-npm-packages

    Use when you need to find the 2-3 most popular and well-maintained npm packages relevant to a frontend checklist rule, validate they meet quality thresholds, and add them to the r…

    77B
  2. frontend-checklist-global

    Use when auditing or improving any frontend codebase against the full Front-End Checklist rule corpus through one entry point.

    76B
  3. improve-rule

    Use when reviewing or improving a Front-End Checklist rule MDX file to raise its quality score, fix stub prompts, add missing fields, or enrich content with real code examples.

    74B
  4. offscreen-lazy

    Use when reviewing image assets, markup, and CDN or build transforms related to Lazy load offscreen images. Check encoded size, rendered size, loading strategy, and above-the-fold…

    69C
  5. sensory-instructions

    Use when reviewing rendered HTML, interactive components, or design-system patterns related to Avoid sensory-only instructions. Check native semantics first, then inspect keyboard…

    65C
  6. focus-order

    Use when reviewing rendered HTML, interactive components, or design-system patterns related to Ensure logical focus order. Check native semantics first, then inspect keyboard beha…

    64C
  7. focus-styles

    Use when reviewing stylesheets, component styles, and responsive behavior related to Provide visible custom focus indicators. Check the rendered layout across breakpoints and inte…

    64C
  8. lazy-loading

    Use when auditing slow page loads, heavy assets, or rendering delays related to Implement lazy loading for offscreen content. Verify the actual bottleneck in DevTools, Lighthouse,…

    64C

All skills in thedaviddias/Front-End-Checklist

Scores come from a snapshot of 300 public GitHub repositories taken on 12 November 2026. Every score is the result of fixed checks run by code; no AI is involved. How scoring works.