language-conventions-source-en-docs-br

Enforce Brazilian Portuguese for documentation and English for source code.

1|Updated Mar 7, 2026

Search Tags:#documentation #docstrings #english #inline-comments #brazilian-portuguese #enforce #language-conventions

Ready to run

npx skills add https://github.com/kayaman/skills --skill language-conventions-source-en-docs-br

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: language-conventions-source-en-docs-br
Source: https://github.com/kayaman/skills/tree/main/skills/language-conventions-source-en-docs-br
Command: npx skills add https://github.com/kayaman/skills --skill language-conventions-source-en-docs-br

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces consistent language usage across project artifacts by applying Brazilian Portuguese to documentation and docstrings while keeping source code in English.

Core Features & Use Cases

Defines language mappings for artifacts (docstrings, docs, comments, identifiers, settings, commit messages).
Guides teams on when to use Brazilian Portuguese vs English, with practical examples and best practices.
Supports repository-wide consistency checks and onboarding of new contributors.

Quick Start

Apply the language-conventions rule to your repository to standardize Brazilian Portuguese for docs and English for source code.

Frequently Asked Questions about language-conventions-source-en-docs-br

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce Brazilian Portuguese for documentation while keeping source code in English?▼

To enforce Brazilian Portuguese for documentation, apply language-conventions rules that map docstrings and user-facing docs to Portuguese while keeping identifiers and source code in English, providing examples and checklists for consistency.

What artifacts should use Brazilian Portuguese vs English in a software project?▼

Brazilian Portuguese applies to docstrings, product docs, user-facing docs, inline comments, and commit messages, while English applies to source code identifiers, parameters, and settings to maintain code readability.

How do I standardize commit message language conventions for a Brazilian development team?▼

Standardize commit message language conventions by applying rules that enforce Brazilian Portuguese for commit messages while maintaining English for source code, ensuring repository-wide consistency through actionable checklists.

Can I use frontmatter discovery to apply language conventions across a repository?▼

Yes, language conventions support frontmatter-based discovery via name and description in SKILL.md, allowing repository-wide consistency checks to automatically apply Brazilian Portuguese and English mappings across artifacts.

What is the best way to onboard new contributors to Brazilian Portuguese documentation conventions?▼

The best way to onboard new contributors is applying language-conventions rules that provide practical examples, best practices, and checklists defining when to use Brazilian Portuguese versus English across project artifacts.

Why keep source code identifiers in English when documentation is in Brazilian Portuguese?▼

Keeping source code identifiers in English maintains code readability and interoperability while Brazilian Portuguese documentation ensures local team comprehension, balancing global coding standards with regional accessibility.