skills.rest
Sonder4
Sonder4COMMUNITY
Explore all skills by this author →
GitHub

bfd-project-init

Generate canonical STM32 runtime profiles from IOC, startup, linker, SVD, and CFG artifacts.

27|1|Updated Mar 9, 2026
Search Tags:#automation#debugging#stm32#ioc#project-scanning#runtime-profile
One-click install
npx skills add https://github.com/Sonder4/STM32-BFD-Kit --skill bfd-project-init
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bfd-project-init
Source: https://github.com/Sonder4/STM32-BFD-Kit/tree/main/skills/claude/bfd-project-init
Command: npx skills add https://github.com/Sonder4/STM32-BFD-Kit --skill bfd-project-init

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Automates the generation of canonical STM32 runtime profiles by scanning IOC, startup, linker, SVD, and CFG artifacts and consolidating them into a single, reproducible profile for debugging workflows.

Core Features & Use Cases

  • Automated profile discovery: detects MCU family, device name, and relevant artifacts (.ioc, startup_stm32*.s, .ld/.sct, *.svd, *.cfg) and exports a canonical profile.
  • Cross-skill compatibility: mirrors a runtime profile to .codex/bfd and a legacy mirror under .codex/stm32/bootstrap for compatibility with downstream tools.
  • Auto-remediation (apply mode): can create missing baseline files from family templates and seed J-Link templates to bootstrap a project.
  • Output artifacts: generates .codex/bfd/active_profile.json and .codex/bfd/active_profile.env, plus a bootstrap_report and ioc_json for IOC tracing.

Quick Start

Run the bootstrap to generate the canonical profile for your STM32 project.

Frequently Asked Questions about bfd-project-init

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate an STM32 runtime profile for debugging?▼

To generate an STM32 runtime profile, run the bootstrap to scan IOC, startup, linker, SVD, and CFG artifacts, exporting a canonical active profile JSON and env for debugging.

What is an STM32 IOC-based runtime profile used for?▼

An STM32 IOC-based runtime profile consolidates detected MCU family, device name, and artifacts into a single reproducible JSON to streamline end-to-end debugging workflows.

Can I automatically create missing STM32 debugging configuration files?▼

Yes, you can create missing STM32 debugging files using apply mode remediation, which generates baseline files from family templates and seeds J-Link templates.

Does STM32 runtime profile generation work with legacy bootstrap directories?▼

Yes, STM32 runtime profile generation mirrors a legacy profile directory under .codex/stm32/bootstrap, ensuring compatibility with downstream debugging and profiling tools.

What artifacts are required to scan an STM32 project for debugging profiles?▼

Scanning an STM32 project for debugging profiles requires artifacts including .ioc files, startup_stm32*.s assembly, *.ld or *.sct linker scripts, *.svd files, and *.cfg configurations.

Related Skills

Explore More Software Engineering Skills→
Sonder4Sonder4
27

bfd-ozone

Generate canonical SEGGER Ozone .jdebug files and bind J-Link probes to STM32 profiles.

Community
Advanced
vinnie357vinnie357
24

nushell

Process structured data like JSON and CSV in Nushell pipelines.

Community
Intermediate
Sonder4Sonder4
27

bfd-rtt-logger

Capture STM32 RTT output via J-Link into structured debugging logs.

Community
Intermediate
51hhh51hhh

stm32-cmake-cross-compile

Build and diagnose STM32 firmware cross-compilation with CMake and arm-none-eabi-gcc.

Community
Intermediate