arduino
Build, review, debug, and scaffold professional Arduino projects across classic AVR boards (`Uno`, `Nano`, `Mega`), Renesas-based R4 boards (`Uno R4 Minima`, `Uno R4 WiFi`, `Nano R4`), ESP32-based Arduino boards, and other common Arduino-family targets. Use when asked for sketches, `.ino` files, Ard
v2026.11.13-21cd5683 instalações+3 em 7 dias39 EstrelasMITsincronizado há 10 horas
Instalar
Ainda não tem a CLI da NotHoly? Instale primeiro.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install aeondave/arduinoGrava em ~/.notholy/skills depois de conferir a assinatura e o SHA-256.
AssinaturaAssinado, ed25519
Pacote43bc100a…c1256517
43bc100adb64…1825c12565175 arquivos · 8.2 KBVarreduraBaixonenhum achado
Fontegithub.com/AeonDave/malskill/tree/main/hardware/arduino@21cd568
Este item ainda não foi escrito no seu idioma, então aparece em English.
Nesta página
This skill is for end-to-end Arduino work that must survive contact with real hardware: board selection, wiring, firmware structure, PlatformIO, testing, debugging, and troubleshooting.
If the task is mainly about choosing sensors or dealing with noisy detection in robotics/domotica, also load sensors.
Workflow
Lock the target board, toolchain, and capability profile.
- Prefer exact names:
Arduino Uno,Uno R4 WiFi,Nano ESP32,ESP32 Dev Module, etc. - Lock the toolchain:
Arduino IDE 2,Arduino CLI,PlatformIO, orArduino Cloud. - If the target is unknown, state assumptions and choose the narrowest safe target.
- Immediately note: board family, voltage domain, resource limits, reserved pins, wireless stack.
- Prefer exact names:
Plan hardware and wiring before code structure.
- Separate inputs, outputs, buses, interrupts, and high-current loads.
- Document pull-up or pull-down assumptions, current draw, and shared grounds.
- Call out when motors, relays, LEDs, displays, or radio modules need external power, drivers, transistors, or level shifting.
Choose the right project shape.
- Use a single
.inoonly for small sketches or fast experiments. - For reusable or testable firmware, split pure logic from hardware access.
- For professional or multi-file work, prefer
PlatformIOwithsrc/,lib/,include/, andtest/. - When migrating from Arduino sketches to PlatformIO, remember that
.inopreprocessing disappears: add#include <Arduino.h>, proper headers, and forward declarations.
- Use a single
Write firmware for bring-up, maintenance, and testability.
- Keep pin constants, feature flags, calibration values, and timing constants centralized.
- Prefer
millis()scheduling, finite-state machines, or task-style loops over long blockingdelay()chains. - Isolate pure logic so it can be unit-tested without hardware.
- Add serial diagnostics that help first power-on, but avoid unbounded serial spam.
- Use compile-time flags or config constants for optional hardware and verbose logging.
Define a verification ladder before finishing.
- Smoke test: compile, upload, and confirm a minimal heartbeat or serial log.
- Functional test: verify each sensor, bus, actuator, and failure path.
- For PlatformIO projects, include
build,upload,monitor, andteststeps. - If the board supports debugging, include a debug plan and probe assumptions.
- If the board does not support practical source-level debugging, fall back to serial tracing, staged bring-up, and smaller test sketches.
Deliver complete output.
- firmware files
- wiring table / pin map
- library or dependency list
- board/toolchain assumptions
- first power-on checklist
- test plan
- troubleshooting notes for the most likely failure modes
Board-family rules
Load references/board-families.md for full details. Minimum awareness without loading the reference:
- Classic AVR: tight RAM/flash; avoid
Stringabuse and large buffers;D0/D1are serial-sensitive. - Renesas R4: not a faster AVR; check USB behavior, timers, analog resolution, and extra peripherals.
- ESP32-based:
3.3Vlogic; be explicit about radio constraints and boot-sensitive pins. - Native USB:
while (!Serial) {}blocks autonomous boot; serial port can disappear on reset.
Review checklist
- board target is explicit
- toolchain is explicit (
Arduino IDE 2,Arduino CLI, orPlatformIO) - pin map in code matches pin map in docs
- analog/digital assumptions are documented
- power and voltage-domain notes are present
- blocking
delay()use is justified or removed - optional hardware is behind flags or clearly separated
- first bring-up and troubleshooting path exists
PlatformIOconfig, if present, matches the board and monitor assumptions- library and dependency versions are pinned when reproducibility matters
Output rules
- Do not claim portability across boards when using board-specific pins.
- Do not invent a
PlatformIOboard ID, upload protocol, or debugger choice. - Do not scatter GPIO numbers through the code.
- Do not leave voltage-domain assumptions implicit.
- Do not recommend powering motors, servos, relays, or LED strips directly from a board pin.
- Call out when serial debugging may fail because of board/port selection, driver issues, baud mismatch, native USB resets, or
while (!Serial) {}. - For
Uno R4 WiFi, mention board-specific caveats when they matter: Qwiic is3.3VonWire1, HID can change the USB port, and direct ESP32 programming can break the default bridge firmware. - If a sensor needs protection or signal conditioning, say so clearly.
- Pin library versions in dependency lists and
lib_depswhen the project needs reproducibility.
When to load references
- Load
references/project-patterns.mdfor project shape, architecture, OTA guidance, bring-up flow, and deliverables. - Load
references/pin-planning.mdwhen assigning GPIOs, documenting wiring, or checking bus and voltage constraints. - Load
references/board-families.mdwhen selecting a board, comparing families, or explaining board-specific caveats. - Load
references/platformio-testing-debugging.mdwhen the request mentionsPlatformIO, tests, upload issues, serial monitor issues, or debugging.
Resources
references/
references/project-patterns.md— project intake, architecture, deliverable bundles, and first-power-on workflow.references/pin-planning.md— GPIO planning, voltage-domain checks, bus mapping, and wiring-output format.references/board-families.md— practical differences between AVR, R4, ESP32-based, and native-USB Arduino targets.references/platformio-testing-debugging.md— PlatformIO structure, migration guidance, unit testing, debugging, and troubleshooting.
Arquivos desta versão
references/414.6 KB
- board-families.md3.0 KB
- pin-planning.md3.9 KB
- platformio-testing-debugging.md3.8 KB
- project-patterns.md3.9 KB
- SKILL.md6.4 KB
Permissões
| Permissão | Declarada | Encontrada na varredura |
|---|---|---|
| Lê arquivos | Não | Não |
| Grava arquivos | Sim | Sim |
| Roda comandos no shell | Não | Não |
| Usa a rede | Não | Não |
| Usa conectores | Sim | Sim |
| Controla um navegador | Não | Não |
Achados da varredura
Revisado em 13 de nov. de 2026
A varredura não encontrou nada para apontar nesta versão.
Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.
| Versão | Publicada em | Commit | SHA-256 | Assinatura | Mudança de permissão |
|---|---|---|---|---|---|
| v2026.11.13-21cd568 | 13 de nov. de 2026 | 21cd568 | 43bc100a | Assinada | – |
Mais de AeonDave
Tudo deste publicadorMais em Mobile, firmware e hardware
Ver a categoriaPergunte tudo o que o seu escopo permite.
Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.
- 1/3
Crie a conta
Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.
Pessoa físicaEmpresa - 2/3
Adicione créditos
No cartão. Você paga por token, sem assinatura.
$5.00recarga mínima - 3/3
Pergunte
No chat, ou instale o CLI e rode notholy login no terminal.
$ notholy login