i18n-patterns
Skill665 starsChanged 6 months agoMITView on GitHub
Implements internationalization with Rails I18n for multi-language support. Use when adding translations, managing locales, localizing dates/currencies, pluralization, or when user mentions i18n, translations, locales, or multi-language. WHEN NOT: English-only applications without localization needs, formatting handled by presenters, or date/number formatting in non-user-facing code.
- Reads credentials
In this repository43 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude_37signals/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- accessibility-reviewSkill
- action-cable-patternsSkill
- active-storage-setupSkill
- api-versioningSkill
- authentication-flowSkill
- behavioral-guidelinesSkill
- caching-strategiesSkill
- code-reviewSkill
- codex-reviewSkill
- dependabot-reviewSkill
- extraction-timingSkill
- friction-reviewSkill
- i18n-patternsSkill
- mutation-testingSkill
- performance-optimizationSkill
- postgres-patternsSkill
- rails-architectureSkill
- rails-concernSkill
- security-auditSkill
- solid-queue-setupSkill
- accessibility-reviewSkill
- action-cable-patternsSkill
- active-storage-setupSkill
- api-versioningSkill
- authentication-flowSkill
- behavioral-guidelinesSkill
- caching-strategiesSkill
- code-reviewSkill
- codex-reviewSkill
- dependabot-reviewSkill
- extraction-timingSkill
- friction-reviewSkill
- mutation-testingSkill
- performance-optimizationSkill
- postgres-patternsSkill
- rails-architectureSkill
- rails-concernSkill
- security-auditSkill
- solid-queue-setupSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 1 is distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 68
Use lazy lookup in views: t(".title") resolves to "events.index.title"
- Very specific: line 69
Use _html suffix for strings containing HTML markup
- Very specific: line 70
Use I18n.l (localize) for dates, times, and numbers — not I18n.t
- Very specific: line 71
Use I18n.t with full key path in models, services, and presenters
- Very specific: line 149
Use i18n-tasks gem to detect missing and unused keys
- Distinctive: line 150
Write view translation specs to assert rendered content
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
I18n Patterns for Rails 8
Overview
Rails I18n provides internationalization support:
- Translation lookups
- Locale management
- Date/time/currency formatting
- Pluralization rules
- Lazy lookups in views
Quick Start
# config/application.rb
config.i18n.default_locale = :en
config.i18n.available_locales = [:en, :fr, :de]
config.i18n.fallbacks = trueProject Structure
config/locales/
├── en.yml # English defaults
├── fr.yml # French defaults
├── models/
│ ├── en.yml # Model translations (EN)
│ └── fr.yml # Model translations (FR)
├── views/
│ ├── en.yml # View translations (EN)
│ └── fr.yml # View translations (FR)
├── mailers/
│ ├── en.yml # Mailer translations (EN)
│ └── fr.yml # Mailer translations (FR)
└── components/
├── en.yml # Component translations (EN)
└── fr.yml # Component translations (FR)Locale File Organization
Organize locale files by domain: models/, views/, mailers/, components/.
- Models:
activerecord.models,activerecord.attributes,activerecord.errors - Views: nested under controller name and action (e.g.
events.index.title) - Shared:
common.actions,common.messages,common.date.formats - Components:
components.<component_name>.<key>
See locale-files.md for complete YAML examples for models, views, shared keys, and components.
Usage Patterns
Key Principles
- Use lazy lookup in views:
t(".title")resolves to"events.index.title" - Use
_htmlsuffix for strings containing HTML markup - Use
I18n.l(localize) for dates, times, and numbers — notI18n.t - Use
I18n.twith full key path in models, services, and presenters - Pass dynamic values via interpolation:
t(".greeting", name: user.name)
In Views
<h1><%= t(".title") %></h1>
<%= link_to t(".new_event"), new_event_path %>
<p><%= t(".welcome", name: current_user.name) %></p>
<p><%= t(".intro_html", link: link_to("here", help_path)) %></p>In Controllers
redirect_to @event, notice: t(".success")In Models/Presenters
I18n.t("activerecord.attributes.event/statuses.#{status}")
I18n.l(event_date, format: :long)See usage-patterns.md for full examples including presenters, components, date/currency formatting, and pluralization.
Locale Switching
URL-Based Locale
# config/routes.rb
Rails.application.routes.draw do
scope "(:locale)", locale: /en|fr|de/ do
resources :events
end
end
# app/controllers/application_controller.rb
class ApplicationController < ActionController::Base
around_action :switch_locale
private
def switch_locale(&action)
locale = params[:locale] || I18n.default_locale
I18n.with_locale(locale, &action)
end
def default_url_options
{ locale: I18n.locale }
end
endUser Preference Locale
class ApplicationController < ActionController::Base
around_action :switch_locale
private
def switch_locale(&action)
locale = current_user&.locale || extract_locale_from_header || I18n.default_locale
I18n.with_locale(locale, &action)
end
def extract_locale_from_header
request.env['HTTP_ACCEPT_LANGUAGE']&.scan(/^[a-z]{2}/)&.first
end
endTesting I18n
- Raise on missing translations in
spec/rails_helper.rb - Use
i18n-tasksgem to detect missing and unused keys - Write view translation specs to assert rendered content
See testing.md for complete spec examples and i18n-tasks configuration.
Best Practices
DO
# Use nested structure matching view paths
en:
events:
index:
title: Events
show:
title: Event Details
# Use interpolation for dynamic content
en:
greeting: "Hello, %{name}!"
# Use _html suffix for HTML content
en:
intro_html: "Welcome to <strong>our app</strong>"DON'T
# Don't use flat keys
en:
events_index_title: Events # BAD
# Don't hardcode in views
<h1>Events</h1> # BAD - use t(".title")
# Don't concatenate translations
t("hello") + " " + t("world") # BADChecklist
- Locale files organized by domain (models, views, etc.)
- All user-facing text uses I18n
- Lazy lookups in views (t(".key"))
- Pluralization for countable items
- Date/currency formatting localized
- Locale switching implemented
- i18n-tasks configured
- Missing translation detection in tests
- Fallbacks configured
References
- locale-files.md — YAML locale file examples for models, views, shared keys, and components
- usage-patterns.md — Usage examples in views, controllers, models, presenters, components, and formatting
- testing.md — RSpec specs and i18n-tasks for translation coverage
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

