Files
magnus919_agent-skills/esp32-development/templates/component-contract.md
T
Magnus HedemarkandGitHub 36638256a8 feat: add portable ESP32 development skill (#53)
* feat: add portable ESP32 development skill

Add source-backed workflows, safe templates, native CLI routing, and a read-only preflight for ESP32 hardware and firmware work.\n\nAI assistance: research, drafting, implementation, and review used OpenAI Codex and delegated DeepSeek agents under human direction.

* docs: harden ESP32 family and security guidance

Add source-backed family traps, brownout, calibration, USB recovery, and security-mode boundaries found during independent review.\n\nAI assistance: independent audits and drafting used delegated DeepSeek agents and OpenAI Codex under human direction.
2026-07-15 21:45:53 -04:00

58 lines
1.6 KiB
Markdown

# Attached component contract
## Identity and sources
- Manufacturer:
- Exact component / revision:
- Breakout or module / revision:
- Datasheet URL and revision:
- Module schematic URL and revision:
- Maintained framework driver and version:
- Access date:
## Electrical contract
- Supply range:
- Logic levels / absolute maximum:
- Typical, peak, startup, stall, or inrush current:
- Required decoupling:
- Pull-ups / pull-downs / termination:
- Driver, level shifter, transceiver, flyback, isolation, or current limit:
- Safe state during ESP32 reset, bootloader, crash, and update:
## Protocol contract
- Interface and mode:
- Pins / address / chip-select straps:
- Clock or baud range:
- Data order, word size, parity, or framing:
- Reset and startup timing:
- Identity / revision register or self-test:
- Readiness, interrupt, and clear sequence:
- Error, CRC, timeout, and retry behavior:
## Measurement or actuation contract
- Range and units:
- Resolution, accuracy, repeatability, and drift:
- Transfer function:
- Calibration points / source:
- Warm-up / settling / conversion time:
- Mechanical, thermal, environmental, or duty-cycle limits:
- Actuator feedback, timeout, interlock, and fault behavior:
## Bring-up evidence
- [ ] Supply measured at component
- [ ] Idle signal levels checked
- [ ] Bus scan / loopback / waveform checked
- [ ] Identity or self-test passed
- [ ] Raw data or unloaded output captured
- [ ] Conversion / calibration checked against reference
- [ ] Reset and power-cycle behavior checked
- [ ] Worst-case load / environment checked
## Unsupported or unresolved claims
-