agentleFS
kayamankayaman/skills/language-conventions-source-en-docs-br/SKILL.md

language-conventions-source-en-docs-br

Skill3 starsChanged 8 months agoCC0-1.0View on GitHub

Enforces language usage conventions for teams based in Brazil. Use when writing code, documentation, docstrings, comments, configuration, or any project artifact. Brazilian Portuguese for documentation and docstrings; English for everything else (source code, identifiers, parameters, class names, function names, settings, configuration keys, commit messages, PR descriptions).

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 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.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When writing any file, verify:

    line 63

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Language Conventions

Rule

ArtifactLanguage
DocstringsBrazilian Portuguese
Project/user-facing documentation (product README, user guides, markdown docs)Brazilian Portuguese
Inline comments explaining intentBrazilian Portuguese
Source code (identifiers, variables, functions, classes, modules)English
Parameters and argumentsEnglish
Settings / configuration keysEnglish
Exception messages (runtime)English
Log messagesEnglish
Test names and assertionsEnglish
Commit messages and PR descriptionsEnglish

Examples

Docstring — Brazilian Portuguese:

def submit_transcription(audio_path: str) -> str:
    """
    Submete um arquivo de áudio para transcrição assíncrona.

    Args:
        audio_path: Caminho do arquivo de áudio no armazenamento blob.

    Returns:
        Identificador do trabalho de transcrição criado.

    Raises:
        TranscriptionError: Quando o serviço de fala não está disponível.
    """

Source code — English:

class TranscriptionRepository:
    def find_by_status(self, status: JobStatus) -> list[TranscriptionJob]:
        ...

Inline comment explaining intent — Brazilian Portuguese:

# Agrupa por locutor antes de calcular métricas de sobreposição
grouped = group_by_speaker(segments)

Settings — English:

MAX_RETRY_ATTEMPTS = 3
BLOB_CONTAINER_NAME = "audio-uploads"

Checklist

When writing any file, verify:

  • All docstrings are written in Brazilian Portuguese
  • Project/user-facing documentation (product README, user guides, markdown docs) is written in Brazilian Portuguese
  • All identifiers (variables, functions, classes, modules) are English
  • Parameter names and type annotations are English
  • Configuration keys and environment variable names are English
  • Inline comments that explain non-obvious intent use Brazilian Portuguese
  • Log messages and exception strings are English

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.