- Home
- Skills
- Translation & Localization
- Brazilian Portuguese (pt-BR) Localization
Brazilian Portuguese (pt-BR) Localization
Natural pt-BR for apps and sites: correct formats (R$ 1.234,56, 31/12/2026), native microcopy, and the translation mistakes that make Brazilians cringe.
Free
Works with the AI Agents you already use
Brazilian Portuguese (pt-BR) Localization
Example session with this skill installed
Translate these UI strings to Brazilian Portuguese: "Are you sure you want to delete this project?", "Submit", "Forgot your password?", "You have 0 items", "Price: $1,234.56 (BRL)". Show a table.
- Read your context and instructions
- Compiled the brazilian portuguese pt-br
| Original (EN) | pt-BR | Notes |
|---|---|---|
| Are you sure you want to delete this project? | Excluir este projeto? Essa ação não poderá ser desfeita. | Evita "Você tem certeza que deseja...?". "Excluir" é o verbo padrão de interface. A frase explica a consequência. |
| Submit | Enviar | "Submeter" é calque e soa pouco natural. Botões usam o verbo no infinitivo. |
| Forgot your password? | Esqueceu a senha? | Forma natural. "Senha esquecida?" soa como tradução literal. |
| You have 0 items | Você tem 0 itens | Em pt-BR o zero leva o plural. Em código, use ICU: {count, plural, one {# item} other {# itens}}. Para um estado vazio, Nenhum item por aqui também funciona. |
| Price: $1,234.56 (BRL) | Preço: R$ 1.234,56 | Usa ponto como separador de milhar e vírgula como decimal. Mostra R$ no lugar de "(BRL)". |
Dicas de implementação
- Gere o valor em reais com
Intl.NumberFormat('pt-BR', {style:'currency', currency:'BRL'}). Ele insere um espaço não separável depois deR$, então testes que comparam com um espaço normal vão falhar. - Se o item "Price" aceitar entrada do usuário, aceite
1234,56e1234.56. Nunca useparseFloat("1.234,56"), que retorna 1.234. - Trate o primeiro texto como pergunta de confirmação. O botão de confirmação deve dizer
Excluir, e o outroCancelar.
Real output from a Claude Code session with this skill installed.
Connects securely to your tools. The creator never sees your data.
About this skill
Bad translations alienate users. When software feels like a literal machine translation or uses European Portuguese (pt-PT) terms like "ecrã" instead of "tela," Brazilian users lose trust. This skill ensures your UI microcopy, data formats, and tone sound like they were written by a native Brazilian product designer.
What it does
- Localizes formats for currency (R$ 1.234,56), dates (31/12/2026), and phone numbers ((11) 91234-5678).
- Corrects UI microcopy by replacing word-for-word translations with natural Brazilian phrasing, including infinitive verbs on buttons (Salvar, not Salve).
- Identifies regionalisms to prevent pt-PT vocabulary or "gerundismo" from entering your pt-BR codebase.
- Adjusts gendered phrasing to use neutral alternatives like "Boas-vindas" instead of gender-specific greetings.
- Formats document and address fields: CPF, CNPJ and CEP masks, and the CEP-first address form order.
How it works
- Submit UI strings or code snippets containing hardcoded English or machine-translated Portuguese text.
- Review the audit which lists the original text, the proposed fix, and a specific reason for the change.
- Implement formatting logic using provided
Intlsnippets to handle decimal commas and non-breaking spaces correctly.
Frameworks & tools
The skill provides implementation guidance for the Intl JavaScript API, ICU MessageFormat for complex plurals, and standard Brazilian document structures (CPF/CNPJ).
Why this beats prompting it yourself
Standard LLMs often blend pt-PT and pt-BR or miss technical nuances like the non-breaking space that Intl inserts after "R$" (which breaks naive string tests). This skill enforces specific Brazilian UX conventions, like using infinitive verbs for buttons, which general-purpose prompts frequently get wrong.
Use cases
- Converting an existing English React/Next.js frontend to natural Brazilian Portuguese.
- Auditing a translation vendor's delivery to ensure they didn't use European Portuguese terms.
- Designing a checkout flow with correct CEP-first address logic and properly formatted CPF fields.
Known limitations
This skill focuses on linguistic and format localization. It does not perform legal audits for LGPD compliance or provide functional code for third-party payment gateways.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Translation & Localization.
Focuses on linguistic and format localization. Does not provide legal LGPD audits or functional payment gateway code. Overflows may occur as pt-BR strings are 15-30% longer than English.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free to use
No account required to browse
Trust & safety
Security scan
Security scan passed 16 days ago
- Free with an Agensi account