plain-portuguese-explainer
Skill12 starsChanged 47 days agoMITView on GitHub
Translate technical decisions, architecture, errors, or AI-generated jargon into plain Portuguese a vibe coder (non-dev) can act on. Use whenever the user signals confusion ("não entendi", "o que isso quer dizer", "explica de novo") or after producing technical artifacts.
In this repository28 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- business-plan-impact-reviewSkill
- codemapSkill
- cost-watchdogSkill
- daily-standupSkill
- decision-logSkill
- deploy-vercel-supabaseSkill
- feature-scaffoldSkill
- first-100-usersSkill
- grow-sustainablySkill
- multi-ai-reviewSkill
- os-self-testSkill
- pitchSkill
- privacy-auditSkill
- processizeSkill
- product-briefSkill
- project-genesisSkill
- prototype-labSkill
- registry-pickSkill
- release-checkSkill
- research-wavesSkill
- rollback-safeSkill
- secrets-disciplineSkill
- secrets-scanSkill
- sprint-managementSkill
- sprint-roadmapSkill
- usage-monitorSkill
- verify-build-worksSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
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
- Distinctive: line 10
After producing a technical artifact (TECHNICAL-PLAN, sprint plan, architecture decision).
- Distinctive: line 11
When the user says "não entendi" / "explica de novo" / "o que isso quer dizer" / "tô perdido".
- Distinctive: line 12
After an error message, build failure, or stack trace.
- Distinctive: line 13
When introducing a new concept (database, deploy, branch, environment variable, API).
- Distinctive: line 17
Use everyday Portuguese: No English jargon unless impossible to translate, and even then explain it once.
≈ “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.
Files
Plain-Portuguese Explainer
When to run this skill
- After producing a technical artifact (TECHNICAL-PLAN, sprint plan, architecture decision).
- When the user says "não entendi" / "explica de novo" / "o que isso quer dizer" / "tô perdido".
- After an error message, build failure, or stack trace.
- When introducing a new concept (database, deploy, branch, environment variable, API).
Rules
- Use everyday Portuguese. No English jargon unless impossible to translate, and even then explain it once.
- Use analogies from outside tech. Restaurant, mailbox, car, building.
- Core idea first, short enough to read in one glance. Then optional "se quiser detalhes" expansion.
- No condescension. The user is smart, just not a dev.
- End with one concrete action the user should take, or "nada que precise fazer agora".
Translation patterns
| Termo técnico | Tradução curta |
| API | "Garçom" — leva pedido pro sistema lá atrás e volta com a resposta. |
| Banco de dados | "Caderno organizado" — guarda informação em linhas e colunas. |
| Branch | "Cópia de rascunho" — pra mexer sem bagunçar a versão principal. |
| Build | "Cozinhar a comida" — pegar os ingredientes (código) e montar o prato final (app). |
| Cache | "Geladeira" — guarda coisas prontas pra não precisar fazer de novo. |
| Deploy | "Colocar a placa de aberto" — sai do seu computador, vira algo que o mundo acessa. |
| Env var | "Bilhetinho secreto" — informação que o app precisa mas não fica no código. |
| Hooks | "Alarme do despertador" — coisa que dispara automático em certos momentos. |
| Linter | "Revisor ortográfico do código". |
| Migration | "Reforma planejada do banco" — muda a estrutura sem perder o que tinha. |
| PR / pull request | "Pedido formal pra entrar mudança" — alguém olha antes de aceitar. |
| Repo / repositório | "Pasta organizada com histórico" de tudo que mudou. |
| Stack | "Conjunto de ferramentas" que o projeto usa. |
| Token | "Chave de cofre" — prova quem você é pra um sistema. |
| Webhook | "Bilhete que cai automático na sua caixa" quando algo acontece num outro sistema. |
Output format
🗣️ Tradução
[Termo / situação]: [a ideia central em português corriqueiro, com analogia]
Detalhe técnico (opcional): [só se o usuário pedir]
👉 O que fazer agora: [ação concreta ou "nada por enquanto"]Anti-patterns
- ❌ "Você precisa fazer um pull request com o feature branch e depois um merge"
- ✅ "Vou fazer uma cópia de rascunho do projeto, mexer nela, e depois pedir pra encaixar de volta no projeto principal. Você só precisa apertar 'aprovar' quando eu te mandar o link."
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
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.