stm32-hal-development
- Repo stars 530
- Author updated Live
- Author repo embed-ai-tool
- Domain
- Engineering
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @LeoKemp223 · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: stm32-hal-development
description: Develop STM32 firmware on CubeMX-generated HAL projects, including peripheral configuration, BSP…
category: engineering
runtime: no special runtime
---
# stm32-hal-development output preview
## PART A: Task fit
- Use case: Develop STM32 firmware on CubeMX-generated HAL projects, including peripheral configuration, BSP driver structure, interrupt-safe code, and hardware-aware troubleshooting. Use when Codex needs STM32 HAL implementation guidance rather than generic C advice..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Workflow / Notes” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Develop STM32 firmware on CubeMX-generated HAL projects, including peripheral configuration, BSP driver structure, interrupt-safe code, and hardware-aware troubleshooting. Use when Codex needs STM32 HAL implementation guidance rather than generic C advice.”.
- **02** When the source has headings, the agent prioritizes “Workflow / Notes” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “Workflow / Notes”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: stm32-hal-development
description: Develop STM32 firmware on CubeMX-generated HAL projects, including peripheral configuration, BSP…
category: engineering
source: LeoKemp223/embed-ai-tool
---
# stm32-hal-development
## When to use
- Develop STM32 firmware on CubeMX-generated HAL projects, including peripheral configuration, BSP driver structure, int…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Workflow / Notes” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "stm32-hal-development" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Workflow / Notes
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}STM32 HAL Development
Treat this skill as the working playbook for CubeMX-based STM32 projects.
Workflow
- Read references/core-guidelines.md first.
- Keep all custom code inside
USER CODEregions unless the project has an explicit non-CubeMX extension point. - Configure peripherals in CubeMX, regenerate code, then add application or BSP logic.
- Read additional references only as needed:
- references/peripheral-driver-guide.md for sensor and bus drivers
- references/hal-quick-reference.md for API lookups
- references/troubleshooting-guide.md for failure analysis
- references/usage-examples.md for implementation patterns
- Reuse assets/bsp-template.c and assets/bsp-template.h when starting a new BSP module.
Notes
- Prioritize hardware constraints, interrupt safety, and regeneration safety over local code convenience.
- Do not modify CubeMX-generated initialization files directly when the same change belongs in the
.iocconfiguration.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review