Agent skill · rafaelquintanilha
better-portuguese
Write, rewrite, translate, edit, or review written artifacts in Brazilian Portuguese with native syntax, vocabulary, punctuation, cohesion, and cadence. Use for PT-BR documentation, summaries, edited transcripts, UI copy, help text, email, marketing copy, titles, subtitles, and other prose, especially when the request or source material is in English. Preserve technical terms and identifiers when translation would reduce precision or change their domain meaning. Do not use merely because a conversation is in Portuguese, for Portuguese varieties other than PT-BR, or for verbatim quotations, literal transcripts, code, commands, identifiers, or data-only output.
What it needs
About 5k tokens when loaded.
What this skill does
Better Portuguese Produce the requested artifact in natural Brazilian Portuguese. Use English for agent reasoning, development instructions, and tool communication unless the task itself requires otherwise. This standard is calibrated for PT-BR. Do not silently normalize European, African, or other Portuguese varieties toward Brazilian usage, and do not present this skill as an authority on those varieties. Treat this skill as an opinionated editorial standard, not as a conversational persona, a generic grammar checker, or a way to imitate platform-specific slang. Apply the same standard of Portuguese across artifacts; let the artifact's function constrain length, structure, register, and density. For a new draft or an explicitly requested stylistic rewrite, apply the opinionated style defined here. When correcting, reviewing, or lightly editing Portuguese that is already competent, preserve its legitimate existing style and change only actual defects or points the user asked to reconsider. For sentence-level prose, first read the punctuation guide, then the grammar and style reference. Finally, read the editorial standard before drafting or revising the artifact, so that its final deconstruction remains the last editorial instruction applied. An isolated label, button, or similarly short interface element does not require the punctuation guide or the grammar and style reference. Follow the editorial workflow 1. Establish the artifact contract: purpose, audience, format, length or space limit, register, requested tone or emotion, required facts, protected meaning, literal tokens, and uncertainties. Infer missing constraints conservatively. Treat a supplied URL as a source locator, not as decorative context. When tools are available, inspect it before drafting whenever product naming, grammatical convention, house terminology, or claims depend on it. If it cannot be inspected, do not invent the missing convention or fact. 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills rafaelquintanilha/better-portuguese