Backend Internationalization
Use when the user asks about backend i18n, translating API messages, locale negotiation (Accept-Language), ICU MessageFormat, pluralization, BCP 47 tags or locale-aware dates and currency. Produces a server-side localization setup. Not for UI string handling (use frontend-internationalization).
Install
npx skills add j4flmao/agent-skills --skill backend-internationalizationgit clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/backend/universal/internationalization ~/.claude/skills/backend-internationalizationPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Backend Internationalization ## Purpose Design i18n architecture with locale selection, translation workflow, and message formatting. ## Agent Protocol ### Trigger Exact user phrases: "i18n", "internationalization", "localization", "l10n", "translation", "multi-language", "locale", "language support", "translation file", "gettext", "message format", "ICU message", "pluralization", "RTL support". ### Input Context Before activating, verify: - Initial languages to support and priority order - Translation workflow (in-house translators, vendor, Crowdin/Lokalise) - Content types needing translation (API messages, emails, push notifications, error messages) - Who provides translations (developers, product team, translation service) ### Output Artifact Internationalization architecture design as formatted text. ### Response Format ```yaml # Locale configuration with fallback chains # Translation file structure ``` ```typescript // Message formatting code // Locale detection and negotiation ``` No preamble. No postamble. No explanations. No filler/hedging/transitions. Compress output — why use many token when few do trick. ### Completion Criteria - [ ] Locale selection with BCP 47 tags and fallback chains - [ ] Message storage with ICU MessageFormat and key naming convention - [ ] Translation workflow defined (extract → translate → import → validate) - [ ] API message delivery with Accept-Language parsing and Content-Language header
Details
- Skill name
backend-internationalization- Repository
- j4flmao/agent-skills
- Path
skills/backend/universal/internationalization/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Backend Internationalization skill do?
Use when the user asks about backend i18n, translating API messages, locale negotiation (Accept-Language), ICU MessageFormat, pluralization, BCP 47 tags or locale-aware dates and currency. Produces a server-side localization setup. Not for UI string handling (use frontend-internationalization).
How do I install the Backend Internationalization skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill backend-internationalization. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Backend Internationalization popular?
It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.
Related skills
Agent Observability
45j4flmao/agent-skills
Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).
AI Agent Architectures
45j4flmao/agent-skills
Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).
AI Agent Core Loop
45j4flmao/agent-skills
Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).
Backend Message Queue
45j4flmao/agent-skills
Use when the user asks about Kafka topics and partitions, RabbitMQ exchanges, SQS, consumer groups, consumer lag, dead letter queues, retention or message size limits. Produces broker topology and producer/consumer configuration. Not for event design between services (use backend-event-driven) or stream processing (use data-streaming).
Backend Idempotency
45j4flmao/agent-skills
Use when the user asks about idempotency keys, a payment endpoint that charges twice when the client retries, safe retries, duplicate requests or deduplication. Produces an idempotency-key store and middleware. Not for message consumer dedupe in brokers (use backend-message-queue) or locks (use backend-distributed-locking).
Backend Multi Tenancy
45j4flmao/agent-skills
Use when the user asks about multi-tenancy, SaaS where each customer must only see their own data, tenant isolation, row-level security, schema or database per tenant, tenant context or tenant provisioning. Produces an isolation model with enforcement code. Not for Supabase RLS specifics (use supabase).
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.