embedded-device-protocols
Change or diagnose ESP32 camera and LED-device wire protocols, Arduino/PlatformIO firmware, STM32 board configuration, and AVR USB HID while preserving framing, buffer ownership, and hardware identity.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- embedded-device-protocols
- license
- MIT
- description
- Change or diagnose ESP32 camera and LED-device wire protocols, Arduino/PlatformIO firmware, STM32 board configuration, and AVR USB HID while preserving framing, buffer ownership, and hardware identity.
02 资源文件 3
- 许可证LICENSE1.3 KB
- 参考文档references/board-contracts.md2.6 KB
- 参考文档references/camera-and-wire.md3.8 KB
03 SKILL.md 正文
From checked-out configuration, identify exact board, framework/platform versions, pin mapping, transport peer and build environment. Portfolio: ESP32/ESP8266, STM32-compatible BluePill clone, ATmega32u4 USB HID. Shared Arduino API does not make their GPIO, interrupt, memory, timing or upload behavior interchangeable.
Hardware/build changes: read references/board-contracts.md. Camera transport, frame parsing, device/server compatibility: read references/camera-and-wire.md. Read only relevant path. Keep each protocol's opcodes, framing and status behavior separate. “TCP camera” and “matrix controller” are not protocol definitions.
Trace ownership: capture allocates/borrows buffer, slot or queue transfers it, sender consumes it, one owner releases it on success and every failure path. Track whether driver reuses pointer. Where possible, decide retries and backpressure before borrowing scarce hardware resources. Network retry must not repeat physical action whose execution is unknown.
Before hardware tests, use offline packet vectors, fake short-read/short-write transports, native parser tests and compile checks. Build success proves toolchain compatibility, not electrical correctness or device timing. Flashing, USB HID output, relay/motor actuation and live camera/network checks need authorized target and bounded check. Never run them as incidental validation of unrelated source edit.
Report tested layer and remaining physical assumptions. Performance work: record separately capture rate, successful send rate, dropped/stale frames, send time, reconnect delay, memory/buffer availability. Latency-sensitive live preview: prefer bounded latest-frame delivery. Use reliable retention only when application needs every frame and storage/backpressure design supports it.
04 同仓库更多 Skills
wiki-builder
Create and maintain a local Markdown research wiki (sources with provenance, compiled concept/source pages, index, maintenance log) driven by a per-wiki config. Use when the user wants to start a wiki or knowledge base, ingest sources into one, or query and update it; use wiki-page-writer for a single code deep-dive page.
refactoring-guru
Diagnose a named code smell and apply the smallest behavior-preserving refactoring, with verification before and after and an explicit stop condition. Use for structural refactors (extract, move, consolidate, change ownership), not for feature or bug work; for readability cleanup of recent changes use code-simplification.
legacy-seams
When changing untested legacy code, pin the observed results with characterization tests and open the smallest seam that substitutes only the blocking dependency, separate from any later logic change. Use when a clock, random source, I/O, global, or hidden constructor blocks a test or a safe edit. Use test-driven-development for a new behavior or a bug, refactoring-guru for one named structural refactor after the seam exists, and code-refactoring-tech-debt to choose which legacy to replace.
idea-refine
Refine a raw idea into a one-page brief (problem statement, recommended direction, assumptions to validate, MVP scope, not-doing list) through divergent then convergent thinking. Use when an idea is still vague or you want options and a stress test before committing; use interview-me when the goal itself is unclear and spec-driven-development once the direction is chosen.
code-review-and-quality
Review rubric and approval standard for any change before merge, including code written by you, another agent, or a human: five axes (correctness, readability, architecture, security, performance), change sizing, structural remedies, severity labels, and feedback technique. Use to judge whether a change is fit to merge; use code-review to run a PR or diff review end to end.
code-perfection
Smell and style gate for code you write or change. Bans known code smells (long method, large class, primitive obsession, long parameter list, data clumps, duplicate code, dead code, feature envy, shotgun surgery, flag arguments, message chains) and enforces behavior-preserving structure. On Scala files, enforces worxbend style. Use while implementing, reviewing a diff for smells, or when a smell or style violation is suspected. Routine construction stays with code-complete. SOLID and DRY stay with clean-code-guard. One named structural refactor stays with refactoring-guru.