القائمة
Audit Air360 firmware docs against the current implementation. Use when checking whether docs/firmware, firmware/README.md, and firmware-local agent docs still match the code.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Create a GitHub-release-ready firmware bundle for the Air360 ESP-IDF project from the current `firmware/build` outputs. Use when preparing a beta or stable firmware release and you need a deterministic package under `firmware/release/` with a versioned bundle folder, an uncompressed merged `full` image for serial flashing, an `ota` application image for OTA updates, `split` images, release-note markdown, and a split zip archive.
Use this skill when the task is to create, update, audit, or improve repository-level documentation for the Air360 project. Best for root README generation, repository structure explanation, documentation map creation, onboarding docs, architecture summaries based on docs/, and explaining how docs/ and firmware/ relate. Do not use for low-level firmware build or implementation documentation unless the request is primarily about the repository as a whole.
Use this skill when the task is to create, update, audit, or improve documentation for the ESP-IDF firmware project located in ./firmware. Best for firmware README generation, build/flash/monitor instructions, architecture docs based on firmware/main, sdkconfig explanation, partition table notes, Kconfig documentation, source layout explanation, and implementation-focused developer documentation for the C++17 firmware.
Use for ESP-IDF firmware development in C++ for ESP32-family repositories: component or driver work, FreeRTOS tasks, Wi-Fi/BLE/network features, sdkconfig-aware changes, CMakeLists or Kconfig updates, partition work, build-error triage, and embedded architecture refactors. Do not use for Arduino-only sketches unless the repository already mixes Arduino with ESP-IDF.
Produce an Air360 firmware change checklist before or after editing code. Use when a task needs a concrete list of co-change files, docs to update, and verification steps.
Explain a specific Air360 firmware subsystem with the right reading order, source files, and related docs. Use when mapping boot, networking, sensors, web UI, uploads, or storage for a contributor or agent.
| name | firmware-doc-audit |
| description | Audit Air360 firmware docs against the current implementation. Use when checking whether docs/firmware, firmware/README.md, and firmware-local agent docs still match the code. |
Use this skill when the user asks to:
Focus on:
firmware/firmware/CLAUDE.mdfirmware/README.mddocs/firmware/Treat firmware/ as the implementation source of truth.
CLAUDE.md and firmware/CLAUDE.md.docs/firmware/README.md and docs/firmware/change-impact-map.md.firmware/main/.python3 scripts/check_firmware_docs.py.Prioritize:
Prefer code-to-doc comparison, not doc-to-memory comparison.