← Products

Developer tools
⚙ Needs: a code project to internationalize; nothing else — t…

i18n and localization patterns for developers

Detect hardcoded strings, manage translations, locale files and RTL support — React, Next.js and Python patterns plus a checker script

At a glance
What
Detect hardcoded strings, manage translations, locale files and RTL support — React, Next.js and Python patterns plus a checker script
Cost
Free
Needs
a code project to internationalize; nothing else — the skill is guidance plus a checker script, no accounts or keys required
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

@
Created by: @sickn33
⌁

Install

Prerequisites: a code project to internationalize; nothing else — the skill is guidance plus a checker script, no accounts or keys required Install "i18n and localization patterns for developers" for me. It teaches the agent @sickn33's i18n playbook: detecting hardcoded strings, managing translation keys and locale files, React/Next.js/Python patterns, RTL support, best practices and a pre-ship checklist — plus an i18n_checker.py script that finds hardcoded strings and missing translations. MIT-licensed. Repository: https://github.com/sickn33/agentic-awesome-skills/blob/main/plugins/agentic-awesome-skills-claude/skills/i18n-localization/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "i18n-localization". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. nothing — point the agent at your project when you want an i18n review). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.

?

Questions

How do I install a build?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.