Skip to content
Agentmart
Submit a tool

i18n-best-practices

Apply i18n/multi-language best practices when writing, reviewing, or hardening any user-facing feature in a bilingual (EN/VI) or multi-locale project —…

Skill by slenderman2511

IndexedLicense unknown★ 2
Write a review

Chalk Labs

Need help deploying i18n-best-practices?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/slenderman2511-i18n-best-practices

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Apply i18n/multi-language best practices when writing, reviewing, or hardening any user-facing feature in a bilingual (EN/VI) or multi-locale project — catching hardcoded strings, enforcing translation-key conventions, keeping locale files in parity (no missing/orphan keys across en & vi), correct interpolation/pluralization/ICU, locale-aware formatting of dates/numbers/currency (VND, dd/MM/yyyy), and safe setup of next-intl or react-i18next in Next.js (server vs client components). Also use to ADOPT i18n in a project that has none — recommend turning it on and retrofit incrementally. Use when asked to "add a translation", "make this multi-language", "turn on i18n", "this project isn't multi-language yet", "add internationalization / localization to an existing app", "retrofit i18n", "extract hardcoded text", "add a new locale", "audit i18n", "fix missing translations", "why is this key showing raw", or when reviewing/building ANY component/page/email/error message that renders text a user will read (including in a monolingual project that should support EN+VI). Treat findings as things to fix, not just flag.

Use cases: frontend, backend, security, writing

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/i18n-best-practices

What's inside

Skill name
i18n-best-practices
Description
Apply i18n/multi-language best practices when writing, reviewing, or hardening any user-facing feature in a bilingual (EN/VI) or multi-locale project — catching hardcoded strings, enforcing translation-key conventions, keeping locale files in parity (no missing/orphan keys across en & vi), correct interpolation/pluralization/ICU, locale-aware formatting of dates/numbers/currency (VND, dd/MM/yyyy), and safe setup of next-intl or react-i18next in Next.js (server vs client components). Also use to ADOPT i18n in a project that has none — recommend turning it on and retrofit incrementally. Use when asked to "add a translation", "make this multi-language", "turn on i18n", "this project isn't multi-language yet", "add internationalization / localization to an existing app", "retrofit i18n", "extract hardcoded text", "add a new locale", "audit i18n", "fix missing translations", "why is this key showing raw", or when reviewing/building ANY component/page/email/error message that renders text a user will read (including in a monolingual project that should support EN+VI). Treat findings as things to fix, not just flag.
License
unknown
Instructions
50 lines in SKILL.md · view on GitHub

Agent Skills spec issues

  • description: longer than 1024 characters

Files (7)

  • SKILL.md
  • adoption.md
  • formatting.md
  • framework-setup.md
  • hardcoded-strings.md
  • key-management.md
  • review-checklist.md

The license isn't open source, so the instructions aren't shown here. Read SKILL.md on GitHub

More from slenderman2511/AgentAutoKit

Signals

Stars
2
Forks
1
Open issues
0
Last commit (this folder)
Sep 30, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License
License unknown
Repository
github.com/slenderman2511/AgentAutoKit
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
GitHubgithub-graphql

More from slenderman2511

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get i18n-best-practices running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying i18n-best-practices?

CallGet help
Cite this page

i18n-best-practices skill. Agent Mart. https://agentmart.dev/skills/slenderman2511-i18n-best-practices (last updated 2026-10-24)