PlatformIO Development
Apply the repository rules in AGENTS.md first. This skill ensures that platform source changes are applied correctly and consistently to the local PlatformIO package cache, and that local development uses one clear platform environment rather than multiple inconsistent copies.
- Before editing, require the developer to provide: fork URL, a new branch based on the fork's
main, sample directory, PlatformIO environment, and the local fork checkout path. If any item is absent, ask for it and do not start implementation. Keep the fork URL and branch stable for the whole development task.
- Identify the protected contract and the owning layer before choosing an implementation: board ID, framework selection, package version, upload/debug behavior, example path, or firmware artifact. Select the smallest sample and environment that exercise it.
- Temporarily change the target sample's
platformio.ini so its platform entry references the stable fork URL and branch, for example https://github.com/<fork-owner>/platform-seeedboards.git#<branch>. Do not use a changing commit SHA in this inner loop: each new Git commit reference creates a new @src-<hash> directory under the PlatformIO platforms cache. Do not commit this test-only override or any local absolute path; restore it before preparing the upstream pull request.
- Bootstrap the package once, then discover the selected package directory with
pio system info and pio pkg list -d <sample> --only-platforms -v. Record that exact directory under C:\Users\seeed\.platformio\platforms; never guess from a directory name and never select a different @src-* copy.
- Immediately after changing any platform source file, apply the same change to the selected local PlatformIO platform package. Keep the fork checkout and that one cached package aligned before compiling. Do not modify other platform-cache copies, run
pio pkg update, or change the fork branch/commit reference during the development loop.
- Every time a sample compiles new firmware, run
pio run -d <sample> -e <environment> -t clean after synchronization, then run the sample build.
- When the developer explicitly asks to stage, commit, push, and create or update a GitHub pull request, invoke the
yeet skill. It owns the Git and PR workflow.
Customer-facing language
Write customer-facing repository content in clear, technically precise English by default, including README files, comments, help text, configuration descriptions, sample output, and implementation documentation. Keep Chinese explanations in the conversation or internal notes rather than replacing deliverable content.
1---2name: platformio-development3description: Develop and validate behavior-changing work in the Seeed Studio PlatformIO platform through a stable developer fork branch and one synchronized local package-cache instance. Use when implementing or debugging board metadata, platform.py, SCons builders, framework integration, examples, CI scripts, or PlatformIO package-cache synchronization.4---56# PlatformIO Development78Apply the repository rules in `AGENTS.md` first. This skill ensures that platform source changes are applied correctly and consistently to the local PlatformIO package cache, and that local development uses one clear platform environment rather than multiple inconsistent copies.9101. Before editing, require the developer to provide: fork URL, a new branch based on the fork's `main`, sample directory, PlatformIO environment, and the local fork checkout path. If any item is absent, ask for it and do not start implementation. Keep the fork URL and branch stable for the whole development task.112. Identify the protected contract and the owning layer before choosing an implementation: board ID, framework selection, package version, upload/debug behavior, example path, or firmware artifact. Select the smallest sample and environment that exercise it.123. Temporarily change the target sample's `platformio.ini` so its `platform` entry references the stable fork URL and branch, for example `https://github.com/<fork-owner>/platform-seeedboards.git#<branch>`. Do not use a changing commit SHA in this inner loop: each new Git commit reference creates a new `@src-<hash>` directory under the PlatformIO platforms cache. Do not commit this test-only override or any local absolute path; restore it before preparing the upstream pull request.134. Bootstrap the package once, then discover the selected package directory with `pio system info` and `pio pkg list -d <sample> --only-platforms -v`. Record that exact directory under `C:\Users\seeed\.platformio\platforms`; never guess from a directory name and never select a different `@src-*` copy.145. Immediately after changing any platform source file, apply the same change to the selected local PlatformIO platform package. Keep the fork checkout and that one cached package aligned before compiling. Do not modify other platform-cache copies, run `pio pkg update`, or change the fork branch/commit reference during the development loop.156. Every time a sample compiles new firmware, run `pio run -d <sample> -e <environment> -t clean` after synchronization, then run the sample build.167. When the developer explicitly asks to stage, commit, push, and create or update a GitHub pull request, invoke the `yeet` skill. It owns the Git and PR workflow.1718## Customer-facing language1920Write customer-facing repository content in clear, technically precise English by default, including README files, comments, help text, configuration descriptions, sample output, and implementation documentation. Keep Chinese explanations in the conversation or internal notes rather than replacing deliverable content.
Seeed-Studio