Embedded-programming
Reduces hardware-software integration risks by applying domain-specific constraints and field-tested error patterns to STM32 development.
Agent skill for STM32 embedded development: SPL & HAL (CubeMX) x bare-metal & FreeRTOS, static discipline checker, 85 field-tested pitfalls, 29 domain docs (Keil/IAR/CMake), CAN/Modbus/BMS/FOC/LVGL/RTOS-porting coverage. Works in DSH / Claude Code. STM32 嵌入式开发技能:四轨代码生成+静态检查器+85 条实测坑。
- Generate STM32 code using HAL, SPL, or bare-metal approaches
- Check embedded code for common hardware-specific development pitfalls
- Automate the porting of FreeRTOS to specific STM32 hardware
Reduces hardware-software integration risks by applying domain-specific constraints and field-tested error patterns to STM32 development. It mitigates common firmware pitfalls and ensures compliance with complex real-time operating system and communication protocol requirements.
Embedded systems engineers developing firmware for STM32 microcontrollers using RTOS, bare-metal, or specialized industrial protocols.
https://github.com/wdcjx/Embedded-programming
By wdcjx
How to Get It
claude plugins install wdcjx/Embedded-programming
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
After installing, paste this into Claude:
Help me generate STM32 code using HAL, SPL, or bare-metal approaches
Trust Signals Auto-scanned
Community Pulse Growing
Discussed on Hacker News
- New embedded programming language with C as a host language — Hacker News · 95 pts
- Embedded Programming Without the IDE — Hacker News · 86 pts
- Embedded Programming with the GNU Toolchain — Hacker News · 85 pts
3 mentions across 1 sources
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 42 GitHub stars; contributors unknown; last commit 0d ago; license MIT.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 42 GitHub stars; contributors unknown; last commit 0d ago; license MIT.