stm32-development
Skill28 starsChanged 29 days agoMITView on GitHub
Build and diagnose STM32Cube HAL/LL projects using their existing CMake, Make, CubeIDE or PlatformIO toolchain. Use when requests involve STM32 clocks, startup/linker files, generated code, SWD or HAL peripheral setup.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- wedsamuel1230/arduino-skillsword for word, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 1
- wedsamuel1230/arduino-skills★ 28100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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.
In this repository48 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/arduino-skills.mdcCursor rule
- cli-creatorSkill
- plugin-creatorSkill
- skill-creatorSkill
- arduino-cli-skillSkill
- arduino-code-generatorSkill
- arduino-project-builderSkill
- arduino-serial-monitorSkill
- arduino-workflow-routerSkill
- battery-selectorSkill
- board-selectionSkill
- board-supportSkill
- bom-generatorSkill
- boot-flash-recoverySkill
- bus-debuggingSkill
- circuit-debuggerSkill
- code-review-facilitatorSkill
- datasheet-interpreterSkill
- embedded-build-workflowSkill
- embedded-project-loopSkill
- enclosure-designerSkill
- error-message-explainerSkill
- fault-forensicsSkill
- field-power-and-connectivity-triagerSkill
- freertos-patternsSkill
- hardware-tddSkill
- i2c-bringup-diagnosticianSkill
- library-selectionSkill
- memory-budgetingSkill
- memory-timing-debuggingSkill
- mermaid-diagram-generatorSkill
- micropython-developmentSkill
- non-blocking-patternsSkill
- ota-deployment-guardianSkill
- pico-sdk-developmentSkill
- pin-assignmentSkill
- power-budget-calculatorSkill
- probe-debuggingSkill
- readme-generatorSkill
- realtime-control-designSkill
- sensor-calibration-workbenchSkill
- sensor-signal-filteringSkill
- usb-debuggingSkill
- wireless-telemetrySkill
- wiring-safety-checkSkill
- zephyr-developmentSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Read the shared embedded contract and keep source/build, device and physical evidence separate.
- Distinctive: line 12
Read build and target diagnosis.
- Very specific: line 17
Use the existing CMake preset, generated Makefile, CubeIDE headless build or PlatformIO environment.
- Very specific: line 28
Use probe-debugging for SWD/probe sessions, fault-forensics for Cortex-M fault registers and bus-debugging for transfers.
≈ “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.
Files
STM32 Development
Read the shared embedded contract and keep source/build, device and physical evidence separate.
Read build and target diagnosis. Identify exact STM32 part and board revision, Cube/HAL package, generator, startup file, linker script, flash/RAM banks and oscillator population. Do not infer an HSE frequency or pin mux from a Nucleo family name.
Use the existing CMake preset, generated Makefile, CubeIDE headless build or
PlatformIO environment. STM32CubeCLT availability does not imply a CMake
project. Preserve .ioc, source-controlled generator output and USER CODE
sections; inspect a regeneration diff before replacing manual code.
Retain the ELF/map and compiler options. Verify vector-table location, Reset handler, stack, heap and memory-region overlap before changing an address to silence a linker failure. Diagnose clock faults through oscillator readiness, PLL constraints, bus prescalers, flash latency and error paths for that exact MCU/reference manual. Distinguish HAL timeout symptoms from their cause.
Use probe-debugging for SWD/probe sessions, fault-forensics for Cortex-M
fault registers and bus-debugging for transfers. Do not turn on a conflicting
peripheral to test a pin on an attached actuator. Deliver the smallest change,
matching build artifacts and measured-versus-unverified behavior.
See platform coverage for the exact tested combination. A source procedure is not a claim that every target was tested.
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
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.