Embedded C/C++ rules for MCU, STM32, HAL, interrupts, DMA, memory constraints, and hardware-focused testing
.cursorrules or .cursor/rules/embedded-stm32-hal.mdc # Embedded MCU, STM32, and HAL Rules ## Project Structure - Keep board support, drivers, middleware, application logic, and tests separate. - Isolate generated CubeMX or vendor code from hand-written application code. - Put hardware abstraction behind narrow interfaces so logic can be tested without hardware. - Document clock tree, pin mappings, peripheral ownership, and interrupt priorities. ## STM32 HAL and Peripherals - Initialize peripherals in one place and avoid hidden reconfiguration. - Check return values from HAL calls and handle timeout/error cases. - Keep blocking HAL calls out of time-critical paths. - Use DMA for high-throughput UART, SPI, I2C, ADC, or timer capture paths when appropriate. - Document buffer ownership and lifetime for DMA operations. - Use `volatile` only for memory shared with ISRs or hardware registers. ## Interrupts and Concurrency - Keep ISRs short and deterministic. - Defer heavy work from interrupts to the main loop, RTOS task, or event queue. - Protect shared data with critical sections, atomics, queues, or RTOS primitives. - Avoid dynamic allocation in interrupts. - Make interrupt priority decisions explicit. ## Memory and Timing - Avoid heap allocation in firmware unless the project explicitly allows it. - Check stack usage for ISRs and RTOS tasks. - Keep lookup tables `const` so they can live in flash. - Use fixed-width integer types for hardware-facing code. - Add timeouts for hardware waits. - Treat watchdog configuration as part of application design, not a late add-on. ## Testing and Debugging - Unit test pure logic on host builds. - Use hardware-in-the-loop tests for peripheral behavior. - Add assertions for impossible hardware states in debug builds. - Use SWD/JTAG, logic analyzers, and serial logs with rate limits. - Keep fault handlers useful: capture reset reason, fault registers, and build version when possible. ## Common Mistakes - Do not modify generated files unless the workflow preserves changes. - Do not busy-wait forever on hardware flags. - Do not share buffers between DMA and CPU without synchronization. - Do not assume peripheral reset state after low-power modes.
volatile only for memory shared with ISRs or hardware registers.const so they can live in flash.Quantitative factor research skills for Cursor. Evaluate factors, run backtests, mine new alpha through natural language.
Prevent AI over-engineering by keeping changes scoped, simple, and directly tied to the user's request
Anti-sycophancy directives for code review and generation. Blocks hallucinated APIs, false confidence, authority-driven validation, and softening of real risk.
Cursor rules for Aspnet Abp.
Guidelines and best practices for building applications with [Beefree SDK](https://docs.beefree.io/beefree-sdk), including installation, authentication, configuration, customization, and template management
Cursor rules for embedding Beefree SDK's no-code content editors (for emails, pages, and popups) into a web application.