FOLOTOY AI Passport develop resources for Agent
This repository also configures its own agents. See what ai-passport tells them →
Skill Claude CodeCodex
After a firmware release, collect reusable development experience and submit it as a documentation pull request to the upstream FoloToy ai-passport project.
Skill Claude CodeCodex
After a firmware release, gather the releasing developer's own improvement points and file them as issues against the upstream FoloToy ai-passport project.
Skill Claude CodeCodex
After a firmware release, archive the published application into the upstream FoloToy ai-passport repository's docs/reference/ directory with an AI-generated bilingual functional summary (text-only; the cover image is recorded by file name and format, not committed).
Skill Claude CodeCodex needs its repo
Validate and package FoloToy AI Passport firmware, including a verified merged image and matching debugging artifacts. Use for build, test, and firmware-package requests; does not flash, commit, or publish.
Skill Claude CodeCodex
Diagnose FoloToy AI Passport runtime failures from logs and symptoms such as reboot, stack fault, watchdog, blank text, black screen, or missing audio. Implement a fix only when requested; not for toolchain installation problems.
Skill Claude CodeCodex
Implement or extend a FoloToy AI Passport application from a user requirement, coordinating implementation, validation, and device-test handoff. Not for advice-only questions, log-only diagnosis, or publishing.
Skill Claude CodeCodex
Guide authorized flashing and on-device acceptance of FoloToy AI Passport firmware, including device discovery and bounded serial observation. Use for explicit device-test or flash requests, not merely because a build succeeded.
Skill Claude CodeCodex
Prepare or diagnose the local ESP-IDF environment for FoloToy AI Passport when onboarding, tools are missing, or toolchain activation and dependency setup fail. Not for runtime firmware crashes.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: