Menu
Verify GPIO pin assignments match between firmware (board_config.h) and schematic (config.py)
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | firmware-sync |
| model | claude-opus-4-7 |
| description | Verify GPIO pin assignments match between firmware (board_config.h) and schematic (config.py) |
| disable-model-invocation | true |
| allowed-tools | Bash, Read, Grep, Glob, Edit |
Cross-reference GPIO pin assignments between the firmware source of truth and the schematic generator.
cd /Users/pierrejonnycau/Documents/WORKS/esp32-emu-turbo
Read scripts/generate_schematics/config.py — this is the master GPIO mapping:
Read software/main/board_config.h — the firmware's GPIO definitions.
For each signal, verify:
Print a comparison table:
Signal | Schematic GPIO | Firmware GPIO | Status
-------------|---------------|---------------|-------
LCD_D0 | 4 | 4 | OK
LCD_D1 | 5 | 5 | OK
...
BTN_START | 18 | 19 | MISMATCH!
If mismatches found:
board_config.h to match config.pyscripts/generate_schematics/config.py — Master GPIO mapping (source of truth)software/main/board_config.h — Firmware GPIO definitionswebsite/docs/snes-hardware.md — Documentation (should also match)Full PCB verification loop using local kicad-cli (DRC + 3D render + gerbers)
Create a new Claude Code skill for this project. Use when you need to add a new skill, improve an existing skill, or convert a workflow into a reusable skill.
Verifies that every PCB pad-to-net assignment matches the manufacturer datasheet pin specifications. Use when changing board.py/routing.py/footprints.py, after GPIO remapping, before releases, or when adding new components. Automated guard against wiring errors like unconnected VBUS, wrong pin assignments, or missing GND connections.
Design intent adversary — cross-checks GPIO, nets, power chains, signal paths across firmware/schematic/PCB/datasheet sources to find lost connections and inconsistencies
Analyze a DFM report and fix all issues in the PCB generation scripts
Run DFM guard tests and add new regression tests after fixing PCB issues