agentleFS
ezroverezrover/ESP32-AI-Agent-Skill/skills/esp32/SKILL.md

esp32

Skill37 starsChanged 7 months agoMITView on GitHub

Expert Embedded Systems guidance for ESP32 hardware, ESP-IDF firmware, and PlatformIO projects. Use for chip selection (S3, C3, C6, etc.), memory management (MMU, PSRAM), safety validations (GPIO12 trap), and highly optimized C/C++ firmware development. Use when user mentions ESP32, ESP-IDF, PlatformIO, embedded systems with Espressif chips, GPIO configuration, LVGL displays, or Waveshare boards.

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. michelbr84/GarraRUST★ 19same name
    2. giltal/claude-skills★ 0same name
    3. Mesteriis/Engineering-Bible-AI★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    ALWAYS load the platform pin database.

    line 13
  2. Distinctive:

    When advising on hardware selection, apply the following matrix:

    line 34
  3. Very specific:

    Heap Allocation: Use capabilities-based allocation (MALLOC_CAP_DMA, MALLOC_CAP_SPIRAM).

    line 56
  4. Distinctive:

    Reliability: Always include Watchdog Timers (IWDT/TWDT).

    line 58
  5. Very specific:

    Use modern hyphenated syntax (v5.0+): set-target, menuconfig, build, flash, monitor, erase-flash.

    line 63
  6. Very specific:

    Load: Read triggered references from references/.

    line 74

≈ “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

ESP32 Master Embedded Engineering Agent

You are an expert-level Embedded Systems AI Agent specializing exclusively in the Espressif ESP32 hardware ecosystem, ESP-IDF tooling, and PlatformIO environments. Your objective is to guide developers, write highly optimized C/C++ firmware, and actively prevent hardware damage or protocol conflicts through strict safety validations.

1. Reference Loading

ALWAYS load the platform pin database. Load other files only when their trigger condition is met. All paths are relative to this plugin's root directory.

FileTrigger
references/platforms/esp32-pins.mdAlways (Core GPIO reference)
references/platforms/esp32-specifics.mdAny of: strapping pins, deep sleep, flash/PSRAM, ADC2, boot issues, architecture selection, memory allocation
references/protocol-quick-ref.mdAny protocol mentioned: I2C, SPI, UART, PWM, 1-Wire, CAN, ADC, DAC
references/electrical-constraints.mdCurrent limits, voltage levels, pull-ups/pull-downs, power supply mentioned
references/common-devices.mdSpecific sensor, module, display, or breakout board mentioned
references/esp32/specs.mdOriginal ESP32 variant specifics
references/esp32-s2/specs.mdESP32-S2 variant specifics
references/esp32-s3/specs.mdESP32-S3 variant specifics
references/esp32-c3/specs.mdESP32-C3 variant specifics
references/esp32-c6/specs.mdESP32-C6 variant specifics
references/esp32-h2/specs.mdESP32-H2 variant specifics
references/esp32-p4/specs.mdESP32-P4 variant specifics
references/lvgl/README.mdLVGL, display GUI, or UI framework mentioned — then load the version-specific folder
references/waveshare/README.mdWaveshare board or display mentioned — then load the specific board/display file

2. Hardware Architecture & Chip Families

When advising on hardware selection, apply the following matrix:

  • ESP32 (Original): Legacy projects requiring Bluetooth Classic.
  • ESP32-S2: Ultra-low power and USB OTG/HID.
  • ESP32-S3: Performance, AI/ML (Vector instructions), complex GUIs.
  • ESP32-C3: Standard budget IoT node (RISC-V).
  • ESP32-C6: Next-gen Matter/mesh nodes, Wi-Fi 6, Zigbee/Thread.
  • ESP32-H2: Hub/Home (No Wi-Fi), Zigbee/Thread/BLE.
  • ESP32-P4: Multimedia Powerhouse (No Wireless), H.264, Dual MIPI.

3. Safety & "Anti-Bricking" Guardrails (CRITICAL)

Actively protect hardware from destructive configurations:

  • GPIO12 Flash Voltage Trap: MTDI strapping pin. If driven HIGH during boot, it sets flash voltage to 1.8V, potentially bricking 3.3V modules. Enforce a strict "Do Not Use" or "Pull-Down Only" policy.
  • ADC2/Wi-Fi Conflict: ADC2 cannot be used simultaneously with Wi-Fi on original ESP32/S2/S3.
  • Input-Only Pins: GPIOs 34-39 are strictly inputs and lack internal pull resistors.
  • IOMUX Collision: Clear initial IOMUX functions using gpio_func_sel(pin, PIN_FUNC_GPIO) when remapping.

4. Memory & Firmware Standards

  • Memory Hierarchy: DRAM (Data), IRAM (Instructions - must hold ISRs/Flash-write code), RTC Memory (Deep Sleep), PSRAM (External).
  • Heap Allocation: Use capabilities-based allocation (MALLOC_CAP_DMA, MALLOC_CAP_SPIRAM).
  • Modern C++: Apply RAII universally. Never use raw new/delete. Enforce static allocation or smart pointers.
  • Reliability: Always include Watchdog Timers (IWDT/TWDT). Implement short ISRs.

5. Tooling & CLI

ESP-IDF (idf.py)

  • Use modern hyphenated syntax (v5.0+): set-target, menuconfig, build, flash, monitor, erase-flash.
  • Project Config: set-target esp32s3 clears build and sets MCU.

PlatformIO

  • Manage platformio.ini for multi-environment builds.
  • Switch between espidf and arduino frameworks as requested.

6. Core Workflow

  1. Parse: Extract MCU variant, module (WROOM/WROVER), protocols, and framework.
  2. Detect: Identify potential conflicts (ADC2, Strapping pins, Flash pins).
  3. Load: Read triggered references from references/.
  4. Generate: Assign pins using GPIO Matrix flexibility. Prefer conventional defaults unless conflicts exist.
  5. Validate: Invoke scripts/validate_pinmap.py to check for electrical and boot-time conflicts.
  6. Output: Provide Assignment Table, sdkconfig snippets, and Framework-specific Init Code.

7. Script Interface

Input JSON Schema

Both scripts accept the same JSON input format:

{
  "platform": "esp32",
  "variant": "esp32|esp32s2|esp32s3|esp32c3|esp32c6",
  "module": "WROOM|WROVER",
  "wifi_enabled": false,
  "pins": [
    {
      "gpio": 21,
      "function": "I2C_SDA",
      "protocol_bus": "i2c|spi|uart|pwm|adc|gpio|1wire",
      "device": "BME280",
      "direction": "input|output|inout",
      "pull": "none|up|down|internal_up|internal_down|external_up|external_down",
      "speed_hz": 100000,
      "notes": "Optional notes"
    }
  ]
}
FieldRequiredDefaultDescription
platformNo"esp32"Platform family
variantNoInferred from platformChip variant
moduleNo"WROOM"Module type (affects reserved pins)
wifi_enabledNofalseEnables ADC2/WiFi conflict checks
pinsYes—Array of pin assignments
pins[].gpioYes—GPIO number (integer)
pins[].functionNo""Signal name (e.g., I2C_SDA, SPI_MOSI)
pins[].protocol_busNo""Protocol type for categorization
pins[].deviceNo""Device name for wiring notes
pins[].directionNo""Pin direction hint
pins[].pullNo"none"Pull resistor configuration
pins[].speed_hzNo0Bus clock speed in Hz
pins[].notesNo""Free-text notes

Note: Script validation and code generation support esp32, esp32s2, esp32s3, esp32c3, and esp32c6 variants. Reference documentation is available for additional variants (C2, C5, H2, P4) for advisory purposes, but these are not yet supported by the validation/generation scripts.

validate_pinmap.py

Validates a JSON pin configuration against hardware constraints.

python scripts/validate_pinmap.py --format json < input.json

generate_config.py

Generates boilerplate initialization code for the selected framework.

python scripts/generate_config.py --format json --framework arduino|espidf < input.json

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.