embedded-build-workflow
/embedded-build-workflow
Sprawdza, odtwarza i migruje procesy budowania embedded w PlatformIO, ESP-IDF, Zephyr, Pico SDK lub STM32Cube, także w CI.
- Autor
- wedsamuel1230 ↗
- Repozytorium
- embedded-engineering-skills ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 15.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 5
- Skrypty
- 2
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 15.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- 2 skrypty w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
Skrypty: scripts/check_memory_config.py, scripts/inspect_build.py
Co robi i kiedy
Sprawdza, odtwarza i migruje procesy budowania embedded w PlatformIO, ESP-IDF, Zephyr, Pico SDK lub STM32Cube, także w CI.
Oryginalny opis (EN)
Inspect, reproduce or migrate embedded build workflows with PlatformIO, native ESP-IDF, Arduino CLI, Zephyr/west, Pico SDK, STM32Cube or MicroPython. Use when a request concerns build environments, mixed frameworks, dependency pins, CI, SDK migration or flash/PSRAM configuration. Do not use for ordinary application logic, GPIO lookup or flashing an unknown device.
Jak działa
- Workflow
- Outputs
- Ownership
- Sources and verification
- Platform procedures
Podgląd SKILL.md
---
name: embedded-build-workflow
description: Inspect, reproduce or migrate embedded build workflows with PlatformIO, native ESP-IDF, Arduino CLI, Zephyr/west, Pico SDK, STM32Cube or MicroPython. Use when a request concerns build environments, mixed frameworks, dependency pins, CI, SDK migration or flash/PSRAM configuration. Do not use for ordinary application logic, GPIO lookup or flashing an unknown device.
metadata: {triggers: "PlatformIO, ESP-IDF, mixed firmware builds, SDK migration, sdkconfig, CI, Zephyr, Pico SDK, STM32Cube, MicroPython"}
---
# Embedded Build Workflow
Produce an explicit project/environment matrix and the smallest reproducible
build path. A framework name is not target support or a successful build.
## Workflow
1. Read [the shared contract](../../docs/arduino-skill-contract.md). Preserve
source locations and existing pinned tooling before proposing migration.
2. Run the offline inspector:
`uv run scripts/inspect_build.py --project PATH`. It never builds, flashes,
opens ports, installs packages or executes project scripts. It returns
argument arrays, not shell commands. Treat custom build scripts as code to
review before a separately authorized build.
3. Read [toolchain branches](references/toolchain-branches.md) for the detected
framework. Choose the repository's build manager, not an Arduino default.
If PlatformIO contains `extra_configs`, `extends` or interpolation, obtain
its native computed configuration and retain unresolved status meanwhile.
Do not share raw computed config when it contains credentials.
4. Record board/carrier revision, module suffix, flash and PSRAM separately,
environment, host OS, tool versions and dependency resolution. For ESP32-S3
memory work, read [memory evidence](references/memory-evidence.md); use
`scripts/check_memory_config.py` only with the explicit physical profile and
provenance of the selected generated sdkconfig.
5. Build every declared program/environment in scope. If an input program has
no build path, report it; do not infer that every sketch needs a sibling INI
when a root project already owns its source. Reuse the same matrix in CI.
6. Keep migration staged: baseline build, bounded API/driver adaptation, host
tests, native build, then authorized target tests. Arduino libraries may rely
on `Wire`, timing, callbacks and runtime initialization unavailable natively.
7. Report the inspected evidence and unverified stages. Use the
[support matrix](../../docs/platform-support.md), not a family-wide badge.
## Outputs
- project paths; all declared environments; framework and manager;
- explicit versions, unresolved inheritance and custom-script trust boundary;
- build/test argument arrays and actual results, when execution was authorized;
- four memory outcomes: `confirmed-mismatch`, `consistent-with-inspected-evidence`,
`unresolved`, `not-applicable`;
- source revision/input hashes, selected environment and artifact identity;
- upload, physical memory population and runtime behavior marked unverified.
## Ownership
The workflow router retains combined board/wiring/application work.
`arduino-cli-skill` owns Arduino CLI commands; native projects stay here.
`board-support` resolves board identity; this skill checks build configuration.
`realtime-control-design`, `freertos-patterns` and `wireless-telemetry` own their
respective designs. Keep pin and electrical claims outside the inspector.
## Sources and verification
The helpers use the Python standard library. Run
`uv run -m unittest discover -s tests -p test_embedded_workflows.py` from the
package root. See [source lessons](../../docs/research/2026-10-15-bottlesumo-lessons.md)
and [research lineage](../../docs/research/2026-10-15-universal-embedded-skills.md).
Tests of the helper prove its output and uncertainty handling, not a firmware
build. Run the trusted compile fixtures separately before claiming build proof.
## Platform procedures
Use the selected specialist for concrete native mechanics:
[Zephyr](../zephyr-development/SKILL.md),
[STM32Cube](../stm32-development/SKILL.md),
[Pico SDK](../pico-sdk-development/SKILL.md),
[MicroPython](../micropython-development/SKILL.md).
Rust is outside the current implementation scope.
Pliki w paczce (5)
- SKILL.md 4 KB
- references/memory-evidence.md 3 KB
- references/toolchain-branches.md 4 KB
- scripts/check_memory_config.py 6 KB
- scripts/inspect_build.py 6 KB
Wersje
W bazie nie ma innych skilli o nazwie embedded-build-workflow.
Identyczna treść występuje jeszcze w 1 innych folderach na GitHubie. Tu pokazujemy jedną, najlepiej ocenioną kopię.
Migawka bazy z 13.11.2026 · wersja paczki 15da4e08f9f3 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100esp32-development
Wspiera budowanie, konfigurację, wgrywanie, testowanie, debugowanie i odzyskiwanie firmware'u dla płytek ESP32 w ESP-IDF, Arduino, MicroPython, ESPHome, Zephyr i Rust, w tym OTA i testy sprzętowe. - 100engineering-embedded-firmware-engineer
Wspiera pisanie firmware'u bare-metal i RTOS dla ESP32, ARM Cortex-M, STM32 i Nordic nRF z użyciem FreeRTOS, Zephyr, PlatformIO oraz Arduino. - 95esp-pio-handling
Prowadzi cykl PlatformIO dla firmware ESP32: platformio.ini, budowanie, wgrywanie i monitor szeregowy przez USB lub testbench. - 100embedded-best-practices
Opisuje dobre praktyki programowania systemów wbudowanych dla ESP32, FreeRTOS i ESP-IDF, przy pisaniu firmware'u, przeglądzie implementacji i nauce wzorców. - 100arduino-project-builder
Buduje kompletne projekty Arduino i wbudowane w Arduino IDE, Arduino CLI, PlatformIO i narzędziach producentów, łącząc firmware, czujniki, aktuatory, sieć, zasilanie i wdrożenie, ze scaffoldem dla UNO, ESP32 i Raspberry Pi Pico. - 100esp32-wroom-30pin
Wspiera tworzenie firmware'u na 30-pinową płytkę ESP32-WROOM-32 (DOIT DevKit V1): konfiguracja platformio.ini i sdkconfig dla ESP-IDF lub Arduino, mapowanie pinów, bezpieczne GPIO i piny strappingowe.