agentsclimarketplace
Sign in

Internationalization and translation

Skill soden46/syarif-laravel-ai-skills/skills/internationalization-and-translation

Build with i18n in mind from day one using Laravel translation helpers, JSON files, Blade integration, and locale managementFrom its SKILL.md

Install
npx -y skills add soden46/syarif-laravel-ai-skills --skill internationalization-and-translation

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.0 KB, 351 tokens by cl100k_base, as published. Nobody here has run it

Internationalization And Translation

Use this skill when a Laravel task involves internationalization and translation.

This skill is adapted to the personal Laravel standards in this repository. It maps the public internationalization-and-translation topic from jpcaparas/superpowers-laravel into the local internationalization-and-translation catalog without copying third-party skill body text.

Syarif Defaults

  • Follow Laravel conventions before introducing custom abstractions.
  • Prefer project-local patterns when they are explicit and tested.
  • Keep controllers focused on HTTP orchestration.
  • Put validation, authorization, transactions, side effects, and integrations at clear boundaries.
  • Keep client names, credentials, internal URLs, provider secrets, and project-specific business rules out of reusable standards.
  • Verify important behavior with the smallest meaningful tests and quality checks.

Workflow

  1. Detect the Laravel version, PHP version, runner, package manager, and existing project conventions.
  2. Identify the smallest local skill set that overlaps this topic.
  3. Implement or review the change using Laravel-native APIs first.
  4. Add abstractions only when they reduce real complexity or protect a meaningful boundary.
  5. Run targeted tests and available quality checks before handoff.

Checkpoints

  • Authorization and validation boundaries are explicit.
  • Query shape, transactions, queues, cache, files, and external calls are intentional when touched.
  • User-facing behavior has feature, unit, browser, or integration tests at the right level.
  • Logs and errors are useful without exposing secrets or unnecessary personal data.
  • Documentation or proposals avoid importing source-project names or one-off business rules.

Related Skills

  • using-laravel-standards
  • architecture
  • testing
  • security

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most translation skills give in 351 tokens

Counted across 286 of the 304 authors here whose files we hold, read 2026-09-06

  • Preserve all markdown formattingin 8 of 286, across 5 files
  • Use ICU message format for complex stringsin 8 of 286
  • Preserve all numbers, dates, and amounts exactlyin 7 of 286
  • Use CSS logical properties for RTL layoutsin 7 of 286
  • Format dates, numbers, and currencies with FormatStylein 7 of 286, across 6 files
  • Use locale-aware formatters for dates, numbers, and currencyin 7 of 286
  • Merge translated chunks in orderin 6 of 286, across 3 files
  • Use logical CSS properties instead of physical onesin 6 of 286
  • Use leading and trailing, never left and rightin 6 of 286, across 5 files
  • Use time-limited SAS URLs for document translationin 5 of 286, across 2 files
  • Split long content at markdown block boundariesin 5 of 286, across 2 files
  • Run first-time setup before any translation when preferences missingin 5 of 286, across 2 files

Said here and by no other author read

  • Follow Laravel conventions before custom abstractions
  • Use Laravel-native APIs first
  • Keep controllers focused on HTTP orchestration
  • Put validation, authorization, transactions, side effects at clear boundaries
  • Add abstractions only when they reduce real complexity
  • Detect Laravel and PHP versions, runner, package manager

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.