MicroPython_Skills

Analyze MicroPythonOS App ideas directly or when invoked by mpos-plan-app. Use to turn natural-language MPOS App requests into requirements, default app identity, manifest draft, Activity/Service plan, MPOS/LVGL API plan, dependency risk, test/deploy plan, mandatory MicroPythonOS resource links, and a JSON handoff before code generation.

Deploy or preview a MicroPythonOS app on desktop, web, device copy, MPK install, or installer/flash guidance paths. Use when Codex needs to launch a confirmed app for manual preview, copy it to a board with mpremote, validate an MPK on-device, or route firmware install and erase to install.micropythonos.com. Does not own app generation, static lint, packaging, or default smoke testing.

MicroPythonOS 基础开发知识库。提供代码架构、App/MPK 约束、LVGL 编程约定、MPY API reference、官方 docs 专题 reference、AGENTS 本地强约束。mpos-plan-app / mpos-analyze-app / mpos-prepare-deps / mpos-gen-app / mpos-test-app / mpos-package-app / mpos-deploy-app / mpos-publish-app 均依赖此 skill。

Generate, update, and repeatedly repair MicroPythonOS App code after requirements are confirmed. Use after mpos-analyze-app and optionally mpos-prepare-deps to create or modify an internal_filesystem/apps package directory with root MANIFEST.JSON, root icon_64x64.png, assets/*.py entrypoints/dependencies, dependency adapters, and validation results. Always defaults to a two-phase flow: first produce a generation plan and ask for confirmation, then write files only after explicit user confirmation. Supports repeated calls for user feature changes and test-failure repair loops. Does not analyze vague requirements, prepare external dependencies, package MPK files, deploy devices, flash firmware, publish to upystore, or rebuild lvgl_micropython.

Package and validate a single MicroPythonOS App as an MPK release artifact. Use when Codex needs to create a .mpk, validate an MPOS App manifest/icon/package structure, emit one app_index_entry.json fragment, run optional temporary install validation, or prepare AppStore/upystore publishing artifacts without uploading.

Orchestrate a MicroPythonOS App workflow across analyze, dependency preparation, generation, testing, packaging, deployment, and upystore publishing. Use when Codex needs to start from a natural-language app request, continue or resume an interrupted MPOS app task, decide the next mpos-* skill, maintain per-app plan_state.json and activity_log.jsonl under tmp/mpos-plan-app, handle user requirement changes with invalidation confirmation, or run the default path through mpos-publish-app. Does not implement code, download dependencies, test, package, deploy, flash, or upload directly.

Prepare application-layer dependencies for MicroPythonOS Apps after mpos-analyze-app and before mpos-gen-app. Use when an MPOS App needs pure-Python MicroPython drivers, async/uasyncio/aio libraries, upypi or GitHub dependency research, vendored runtime files, dependency search caching, synchronous-driver adapter planning, or a machine-readable dependency handoff. Does not rebuild firmware, modify lvgl_micropython, add C/native/frozen modules, flash devices, package MPK files, or publish apps.

Validate and prepare a MicroPythonOS App for upystore release after packaging, testing, and deployment. Use when Codex needs to read package_result.json, app_test_result.json, and deploy_result.json together, compare the App version against upystore public listings, assemble store metadata such as screenshots, short/long descriptions, hardware tags, and release notes, produce publish_result.json, and guide the user to upload manually. Does not upload, login, package MPK files, deploy devices, flash firmware, or repair app code.

Test a specific MicroPythonOS App after mpos-gen-app using MicroPythonOS built-in desktop simulator/controller tools. Use when Codex needs to smoke-test or interactively exercise one generated MPOS app in the MPOS runtime with AppManager.start_app, visible text/widget-tree checks, screenshots, or scripted UI input. Does not own static gates such as make lint, flake8, pylint, manifest checks, syntax checks, packaging, deployment, device debugging, firmware rebuilds, or full OS regression testing.

插件化工作流版 analyze。读取用户自然语言和插件上下文，完成需求解析、器件确认、驱动搜索、替代推荐或冷门驱动标记，并以 phase_complete + manifest_content 把结果交给下游。触发：插件 start_phase(analyze)。

插件化工作流版 MicroPython 固件解析、下载、烧录或手动确认。用于 Codex 收到 next_phase=upy-flash-mpy-firmware-plugin 的 phase_complete(select-hw) 时；消费 select-hw manifest_content，从 micropython.org/download 或受信任 vendor source 解析固件，协助 ESP32 esptool 烧录，引导 Pico/RP2 UF2 复制，或为其他板卡提供手动烧录链接，最后输出 next_phase=upy-scaffold-plugin。

插件化工作流版 select-hw。消费 upy-analyze-plugin 的 phase_complete.payload.manifest_content，完成板卡/MCU 确认、MicroPython 固件核验、引脚分配和 BOM，输出 phase_complete(select-hw) 给 MPY 固件烧录阶段。

第七步——软件架构图生成。读取 firmware/ 代码和 project-manifest.json，LLM 生成中间 JSON，脚本渲染 Mermaid 文本架构图（.md 代码块，CLI 原生可读）+ SVG + PNG + HTML（双击浏览器可看）。触发：upy-generate 完成后。

插件化工作流版 MicroPython 项目骨架生成。用于 Codex 收到 next_phase=upy-scaffold-plugin 的 phase_complete(upy-flash-mpy-firmware-plugin) 或用户在后续阶段新增器件时；消费 select-hw manifest_content，审批调度模式和模块后生成 file_operation 写入的 firmware/ 骨架，或 incremental 只生成新器件 driver stub。

第三步——项目骨架生成。读取 select-hw 阶段的 project-manifest.json，按调度模式（Timer/asyncio/_thread）生成完整 firmware/ 目录骨架。触发：upy-select-hw 完成后自动进入。

插件化 MicroPython 业务代码生成阶段。用于收到 next_phase=upy-generate-plugin 的 scaffold phase_complete 后，生成驱动依赖、factory/mock、tasks、conf.py、main.py、测试、lint/check/git commit 和 phase_complete；也用于 deploy/simulate/autofix 或用户反馈后以 mode=fix 最小修复代码。

插件化 workflow skill，用于从 datasheet、Arduino/C/C++ source、GitHub repository、chip model 或当前项目 cold-driver item 生成缺失的 MicroPython hardware driver。适用于插件全局工具 "生成缺失硬件驱动" 被触发、manifest 中存在 devices[].driver.status=cold_driver_required，或 deploy/autofix 反馈显示缺失/损坏硬件驱动，并且流程需要 session/checkpoint/resume、retry、timeout、cancellation、permission prompts、structured errors 和 artifact manifests。

Use this skill when the user provides a URL and wants to extract key information from it. Supports GitHub files, upypi pages, and general web pages. Invoke when user says things like "帮我看一下这个链接", "从这个URL提取信息", "这个页面说了什么", "读取这个文档", or pastes any URL and asks about its content.

Use this skill for general MicroPython device interaction via mpremote, including connecting, running code, checking device state, and managing the device. Triggers on "connect to micropython", "run code on device", "check device state", "mpremote", "micropython device", "repl", "device version", "device reset", "连接设备", "在设备上运行代码", "查看设备状态".

Use this skill when copying files to or from a MicroPython device using mpremote. Covers file copy syntax, directory operations, and best practices for device filesystem management. Triggers on "copy file to device", "upload to device", "download from device", "mpremote fs", "device filesystem", "copy firmware files", "上传文件到设备", "从设备下载文件", "同步文件".

Use this skill when maintaining a persistent interactive connection to a MicroPython device for sending commands and capturing output. This is the PREFERRED method for device interaction when multiple commands need to be sent, when monitoring device output over time, or when the device runs an asyncio event loop with aiorepl. Triggers on "send commands to device", "monitor device output", "interactive session", "persistent connection", "stress test device", "capture serial output", "持续监听设备", "长连接设备", "监控串口输出".

Use this skill when the user wants to review MicroPython code changes using historical review patterns. Invoke when user mentions reviewing code, finding review examples, or wants feedback on MicroPython PRs/commits/diffs. Provides semantic search across ~19.5K categorized review comments.

插件化 V0 analyze 阶段。读取一句话硬件项目需求和插件上下文，完成需求解析、器件确认、驱动搜索、替代推荐或冷门驱动标记，并输出完整 envelope 的 phase_complete + manifest_content。触发：插件 start_phase(analyze)、用户描述“做一个/我想做/帮我写一个”MicroPython 硬件项目、需要生成 project manifest。

第六步——编排协调层。读取设备日志，解析错误，分级决策后委托上游 skill 修复（generate/select-hw/analyze），最多 3 次尝试。触发：upy-deploy 运行失败后自动进入。

第五步——一键烧录运行。上传 firmware/ 到设备、软复位、持久会话采集输出、读取设备端日志、初判通过/失败。触发：upy-generate 完成后自动进入。

Use this skill after upy-norm-pkg completes to deploy normalized driver files to a MicroPython device and validate by running main.py. Invoke when user says things like "烧录测试", "deploy and test", "上传并运行", "验证设备", or after norm-pkg asks to proceed with device testing.

插件化 MicroPython 软件架构图生成阶段。用于收到 upy-generate-plugin success 的 optional_next_phases 选择后，读取生成后的 firmware 与 project-manifest.json，生成 docs/diagram.json，校验 diagram.schema.json，渲染 architecture/flowchart/data_flow 的 md/svg/png/html，并输出带 session/checkpoint/artifact manifest 的 phase_complete；兼容插件协议调用和本地 skill 直测，不覆盖原 upy-diagram。

从 PDF 数据手册或 Arduino/C++ 代码生成 MicroPython 驱动。当 upypi 和 GitHub 均无驱动时使用。流程：提取→生成调试版→硬件验证循环→脱调试→规范化。触发：upy-analyze 搜不到驱动时调用，或用户直接 /upy-gen-driver。

Use this skill when the user wants to generate a new main.py test file from scratch for a MicroPython driver. Invoke when user says things like "generate main.py", "生成测试文件", "从零生成main.py", "帮我写测试文件", or provides a driver .py file and asks to create a test program.

Use this skill when the user wants to generate a package.json from scratch for a MicroPython driver package. Invoke when user says things like "generate package.json", "生成package.json", "帮我写包配置", "创建mip包配置", or provides a driver directory/file and asks to create a package config.

Use this skill when the user wants to generate a README.md from scratch for a MicroPython driver. Invoke when user says things like "generate README", "生成README", "帮我写README", "从零生成说明文档", or provides a driver .py file and asks to create documentation.

第四步——业务代码生成。读取 scaffold 阶段的 project-manifest.json，下载驱动、生成 DI 架构的业务代码、Mock 层、单元测试。触发：upy-scaffold 完成后自动进入。

Use this skill when the user wants to normalize or standardize an existing MicroPython driver .py file (non-main.py) according to the GraftSense coding spec. Invoke when user says things like "normalize this driver", "规范化这个驱动文件", "按规范改写", or provides a .py driver file path and asks for standardization.

Use this skill when the user wants to normalize or standardize an existing MicroPython main.py test file according to the GraftSense coding spec. Invoke when user says things like "normalize this main.py", "规范化测试文件", "按规范改写main.py", or provides an existing main.py path and asks for standardization.

Use this skill when the user wants to normalize/standardize an existing validated MicroPython driver package (one or more driver .py files, optional main.py) according to the GraftSense coding spec. Invoke when user says things like "规范化驱动包", "norm pkg", "对整个驱动目录规范化", or provides a driver directory path and asks for full normalization.

Use this skill when the user wants to optimize the performance of any existing MicroPython .py file (driver, main.py, or any other file) according to the GraftSense performance optimization guide. Invoke when user says things like "优化性能", "optimize", "加速", "对驱动做性能优化", "优化这个文件", or provides any .py file path or directory path and asks for performance improvement.

Use this skill when the user wants to package a MicroPython driver into the standard GraftSense directory structure. Invoke when user says things like "打包驱动", "pack driver", "生成驱动包目录", "整理成标准目录", or has finished normalizing/generating all files and wants to organize them.

Use this skill when the user mentions a device/chip name and wants to know how to use its MicroPython driver from upypi. Invoke when user says things like "怎么用BMP280", "DS18B20怎么调用", "告诉我MPR121的用法", "查一下upypi上XX的驱动怎么用", or mentions any chip/sensor name and asks for usage guidance.

Use this skill when the user describes a MicroPython project — what it should do, what microcontroller and sensors to use. Invoke when user says things like "我想做一个MicroPython项目", "帮我写一个ESP32程序", "用BMP280和OLED做一个气象站", "帮我实现XX功能", or describes any embedded project with hardware components.

第二步——MCU 选型 + 固件核验 + 引脚分配 + BOM 生成。输入 upy-analyze 的 project-manifest.json，输出完整的硬件方案。触发：upy-analyze 完成后自动进入。