embedded-dev
- Repo stars 0
- Author updated Live
- Author repo embedded-dev-skill
- Domain
- Other
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @zhaoyanxiang125 · 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: embedded-dev
description: > 根据用户问题的类型，优先阅读以下对应的参考文件： |------|---------| | 项目规划 / 流程 / 阶段管理 | references/process.md | | 芯片选…
category: other
runtime: no special runtime
---
# embedded-dev output preview
## PART A: Task fit
- Use case: > 根据用户问题的类型，优先阅读以下对应的参考文件： |------|---------| | 项目规划 / 流程 / 阶段管理 | references/process.md | | 芯片选型 / 架构设计 | references/architecture.md | | 驱动开发 / 外设接口 / 寄存器操作 | references/drivers.md | runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “使用本 Skill 的方式 / 核心原则（每次回答都要牢记） / 快速响应模板” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “> 根据用户问题的类型，优先阅读以下对应的参考文件： |------|---------| | 项目规划 / 流程 / 阶段管理 | references/process.md | | 芯片选型 / 架构设计 | references/architecture.md | | 驱动开发 / 外设接口 / 寄存器操作 | references/drivers.md | runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “使用本 Skill 的方式 / 核心原则（每次回答都要牢记） / 快速响应模板” 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 “使用本 Skill 的方式 / 核心原则（每次回答都要牢记） / 快速响应模板”. 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: embedded-dev
description: > 根据用户问题的类型，优先阅读以下对应的参考文件： |------|---------| | 项目规划 / 流程 / 阶段管理 | references/process.md | | 芯片选…
category: other
source: zhaoyanxiang125/embedded-dev-skill
---
# embedded-dev
## When to use
- > 根据用户问题的类型，优先阅读以下对应的参考文件： |------|---------| | 项目规划 / 流程 / 阶段管理 | references/process.md | | 芯片选型 / 架构设计 | references/…
- 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 “使用本 Skill 的方式 / 核心原则（每次回答都要牢记） / 快速响应模板” 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 "embedded-dev" {
input -> user goal + target files + boundaries + acceptance criteria
context -> 使用本 Skill 的方式 / 核心原则（每次回答都要牢记） / 快速响应模板
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
}嵌入式开发 Skill
使用本 Skill 的方式
根据用户问题的类型，优先阅读以下对应的参考文件：
| 场景 | 读取文件 |
|---|---|
| 项目规划 / 流程 / 阶段管理 | references/process.md |
| 芯片选型 / 架构设计 | references/architecture.md |
| 驱动开发 / 外设接口 / 寄存器操作 | references/drivers.md |
| RTOS 使用 / 任务调度 / 同步 | references/rtos.md |
| 调试技巧 / 故障排查 | references/debug.md |
| 代码规范 / 工程最佳实践 | references/coding-standards.md |
| 量产 / 测试 / EMC | references/production.md |
如果问题横跨多个领域，可以同时阅读多个文件。
核心原则（每次回答都要牢记）
- 资源约束优先：嵌入式系统内存、Flash、CPU 算力都极为有限，任何建议都要考虑资源开销。
- 确定性与实时性：嵌入式系统需要可预期的时序行为，避免不确定延迟。
- 硬件软件协同：问题常出在软硬件交界处，调试时不能只看代码。
- 防御性编程：所有外部输入、硬件状态都可能出错，必须有保护机制。
- 可测试性：从一开始就设计测试点、调试接口，而非事后补救。
快速响应模板
用户问"XXX 怎么调试"时
- 先确认硬件层面（电源、时钟、接口电平）是否正常
- 再看通信协议层面（时序、帧格式、ACK）
- 最后才看软件逻辑
用户问"XXX 怎么优化"时
先问：优化目标是什么？（功耗 / 速度 / Flash 大小 / RAM 占用），不同目标策略完全不同。
用户问"选什么芯片/方案"时
阅读 references/architecture.md，按需求维度逐一匹配。
常用代码片段（可直接使用）
安全的超时等待模板（裸机）
#define TIMEOUT_MS 1000
uint32_t tick_start = HAL_GetTick();
while (!condition_met()) {
if ((HAL_GetTick() - tick_start) > TIMEOUT_MS) {
return ERR_TIMEOUT;
}
}ISR 与主循环通信（标志位模式）
// 在 ISR 中：
volatile uint8_t g_uart_rx_flag = 0;
void USART1_IRQHandler(void) {
g_uart_rx_flag = 1; // 只设标志，不做处理
}
// 在主循环中：
if (g_uart_rx_flag) {
g_uart_rx_flag = 0;
process_rx_data();
}FreeRTOS 队列通信模板
// 创建
QueueHandle_t xQueue = xQueueCreate(10, sizeof(MyMsg_t));
// 发送（从 ISR）
BaseType_t xHigherPriorityTaskWoken = pdFALSE;
xQueueSendFromISR(xQueue, &msg, &xHigherPriorityTaskWoken);
portYIELD_FROM_ISR(xHigherPriorityTaskWoken);
// 接收（任务中）
MyMsg_t msg;
if (xQueueReceive(xQueue, &msg, pdMS_TO_TICKS(100)) == pdTRUE) {
// 处理消息
}阅读完本文件后，根据用户的具体问题，跳转到对应的 references/ 子文件获取更详细的内容。
Decide Fit First
Design Intent
How To Use It
Boundaries And Review