القائمة
pt-BR voice and error-message conventions for nf. Use when adding or editing Cobra command descriptions, error wrappers, render labels, or any other user-visible string.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | nf-cli-translation |
| description | pt-BR voice and error-message conventions for nf. Use when adding or editing Cobra command descriptions, error wrappers, render labels, or any other user-visible string. |
The CLI and all user-facing output are in pt-BR. Agent-facing prose (AGENTS.md, CLAUDE.md, SKILL.md, agent prompts), code comments, and package doc strings stay in English. This skill documents how the split is enforced in practice.
Pattern: package prefix in English, body in pt-BR.
fmt.Errorf("xmlsig: documento vazio")
fmt.Errorf("soap: falha ao montar envelope")
fmt.Errorf("wsdl: targetNamespace não encontrado")
fmt.Errorf("emit: assinatura: %w", err)
Why: the prefix is diagnostic (the user can grep code by it), the body
is informational (the user reads it on the terminal). Errors percolate
through fmt.Errorf("%w", ...) wrapping; each layer adds its own
prefix and pt-BR clause.
Standard prefixes in use:
| Prefix | Package |
|---|---|
xmlsig: | internal/xmlsig |
soap: | internal/soap |
wsdl: | internal/soap (WSDL) |
emit: | internal/service/emit |
query: | internal/service/query |
cancel: | internal/service/cancel |
nota: | internal/nota |
config: | internal/config |
When introducing a new error in an existing package, reuse the existing prefix. When introducing a new package, pick a short English prefix that does not collide.
Short, Long, and flag descriptions are pt-BR.
root := &cobra.Command{
Use: "nfe",
Short: "CLI para NFS-e ABRASF",
Long: "Cliente de linha de comando para emissão, consulta e cancelamento de NFS-e seguindo o padrão ABRASF v2.04.",
}
root.PersistentFlags().StringVarP(&gf.configPath, "config", "c",
defaultConfigPath(), "caminho do arquivo de configuração")
Style: imperative verbs for Short ("Emite", "Consulta", "Cancela"),
descriptive sentences for Long. No trailing period on Short; full
sentence with terminating period on Long.
internal/render/human.go standardises the labels that prefix output
lines:
OK: — success path. Kept English; "OK" is universally readable and
the existing convention.ERRO: — error path.dica: — suggestion / next-step pointer.Status messages are short pt-BR sentences:
projeto inicializado em <path>ambiente alterado para <name>falha na emissãofalha na consultafalha no cancelamentonenhuma NFS-e encontradadry-run — sem chamada SOAP, sem incremento do contadorWhen adding a new label, follow the same lowercase-pt-BR style.
The user-facing README at the repo root is pt-BR. The nfe init
command writes a project-local README (initReadme constant in
internal/cli/init.go) — that one is also pt-BR.
If the same noun appears in both audiences (e.g. "emissão" vs "emission"), prefer the audience's natural form on each side.
ABRASF v2.04 XML emission rules for nf. Use when changing builders, decimal formatting, struct ordering, or golden XML fixtures under internal/abrasf and testdata/golden.
Enveloped XMLDSig pipeline for nf. Use when changing the signer, the PKCS#12 loader, or anything that affects how the <Signature> block is computed and attached to ABRASF envelopes.
Local development workflow for the nf repository. Use when orienting in the codebase, choosing the right just recipe, picking a validation lane, or making cross-package changes that are not tied to a single domain skill.
SOAP 1.1 transport and WSDL auto-discovery for nf. Use when changing the SOAP client, the envelope shape, mTLS plumbing, or anything around how endpoint URLs and SOAPAction values are discovered.