Develop and update MicroPython apps on an already provisioned Cardputer-Adv. Add apps to its launcher, transfer individual changed files without reflashing, inspect serial logs, and run a single command through the device’s interactive Python console.
Iterate on the Cardputer-Adv MicroPython app bundle (Claude Buddy, Snake, Hello) after the device is already provisioned via m5-onboard. Use when the user wants to add a new app, push a single changed .py without re-flashing, watch device serial logs, or run a one-shot REPL command. Trigger on "add an app", "push to the cardputer", "tail the device", "run on the device", or follow-up work after /maker-setup.
Review the instructions the agent will receive before you install.
The buddy/ directory in the local build-with-claude clone is the MicroPython payload that m5-onboard installs onto /flash/. Work inside that clone.
/flash/
├── main.py launcher menu (replaces UIFlow's boot flow)
├── buddy_*.py shared libs (BLE, UI, state, protocol, chars)
├── burst_frames.py sprite frames
└── apps/
├── claude_buddy.py BLE client → Claude Desktop's Hardware Buddy
├── hello_cardputer.py
└── snake.py
main.py scans /flash/apps/ at boot and lists every .py as a menu entry. Drop a file into buddy/device/apps/, push it, and it appears on next boot.
Crib from buddy/device/apps/hello_cardputer.py — smallest example of keyboard polling, font, and exit conventions. Then push without re-flashing:
python3 onboard/scripts/install_apps.py --port <PORT> --src buddy
<PORT> is whatever detect.py reported last run (e.g. /dev/cu.usbmodem1101, /dev/ttyACM0, COM3).
buddy/scripts/)# Push a subset of files over USB-serial
python3 buddy/scripts/push.py --port <PORT> --files apps/snake.py
# Watch device logs
python3 buddy/scripts/tail_serial.py --port <PORT>
# One-shot REPL exec
python3 buddy/scripts/repl_run.py --port <PORT> --script "import os; print(os.listdir('/flash'))"
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Manage access to a Discord channel integration by approving pairing codes, updating allowed users, and setting direct-message and channel policies. Check pending requests and adjust reply behavior through configuration files read by the channel server.
Manage who can contact an assistant through the iMessage channel. Update approved senders, approve pairing codes, and configure direct message and group access rules by editing the channel’s local settings.
Manage access to a Telegram channel integration by approving pairing codes, updating allowed users, and setting direct-message and group policies. Check pending requests and adjust reply behavior through configuration files read by the channel server.
Design autonomous agents for Claude Code plugins, including when they should run, what they should do, and which tools they may use. Provides file templates and guidance for validating configuration and testing behavior.
Add interactive panels to an MCP server so users can select records, view charts, or follow progress inside a conversation. The skill guides tool connections, interface implementation, sandbox restrictions, and testing in hosts that support these panels.
Plan and build an MCP server, a connection that lets Claude use external tools. Choose hosting, tool structure, authentication, and a framework, then scaffold a server or hand off to specialized packaging and interface skills.