Implementing firmware

Skill qte77/claude-code-plugins/plugins/embedded-dev/skills/implementing-firmware

A Claude Code plugin marketplace providing skills, rules, and scripts extracted from a production development workflow.

Install

npx -y skills add qte77/claude-code-plugins --skill implementing-firmware

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Implements ESP-IDF or PlatformIO firmware with mandatory requirement docstring tags and MISRA-C linting. Use when writing embedded C code, implementing firmware features, or adding requirement-traced functions.

SKILL.md

2.3 KB, as published. Nobody here has run it

Firmware Implementation

Target: $ARGUMENTS

Implement firmware code with mandatory requirement traceability tags, following ESP-IDF or PlatformIO patterns.

References (MUST READ)

Read these before proceeding:

references/esp-idf-patterns.md — Component structure, FreeRTOS, sdkconfig, idf.py
references/platformio-patterns.md — platformio.ini, pio commands, library management
references/c-safety-rules.md — MISRA-C cppcheck flags, clang-tidy, tagging rules

Workflow

Detect framework:
- CMakeLists.txt + sdkconfig* → ESP-IDF
- platformio.ini → PlatformIO
- Neither → ask user which framework to use
Read existing requirements — Check for docs/requirements.md to understand which SW-REQs need implementing

Implement code with mandatory docstrings on every new function:

/**
 * @brief <What this function does>
 *
 * @requirement SW-REQ-NNN
 * @parent      PRD-REQ-NNN
 * @test        TEST-NNN
 *
 * @param ...
 * @return ...
 */

Create test stubs in test/ with matching @test TEST-NNN references

Lint with cppcheck:

cppcheck --addon=misra.py --std=c11 --enable=all --xml src/ 2> misra-report.xml

Build:
- ESP-IDF: idf.py build
- PlatformIO: pio run
Report — Count tagged functions, list any warnings

Rules

Every new function must have @requirement, @parent, and @test tags
Follow existing code style (indentation, naming conventions) in the project
Use ESP-IDF error handling patterns (ESP_ERROR_CHECK, esp_err_t returns)
Do not suppress MISRA warnings without documenting the deviation
Create header declarations alongside implementations
Test stubs must compile even if test logic is not yet implemented