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 installs+3 in 7 days39 StarsMITsynced 11 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install aeondave/arduinoWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package43bc100a…c1256517
43bc100adb64…1825c12565175 files · 8.2 KBScanLowno findings
Sourcegithub.com/AeonDave/malskill/tree/main/hardware/arduino@21cd568
On this page
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.
Files in this version
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
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | Yes | Yes |
| Runs shell commands | No | No |
| Uses the network | No | No |
| Uses connectors | Yes | Yes |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
The scan found nothing to flag in this version.
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.11.13-21cd568 | Nov 13, 2026 | 21cd568 | 43bc100a | Signed | – |
More from AeonDave
All from this publisherMore in Mobile, firmware and hardware
See the categoryAsk anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login