cardputer-buddy

Push single .py files to a provisioned Cardputer-Adv over USB-serial.

28|5|Updated Jun 24, 2025
One-click install
npx skills add https://github.com/thevibeworks/claude-code-docs --skill cardputer-buddy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cardputer-buddy
Source: https://github.com/thevibeworks/claude-code-docs/tree/main/content/github/claude-plugins-official/plugins/cwc-makers/skills/cardputer-buddy
Command: npx skills add https://github.com/thevibeworks/claude-code-docs --skill cardputer-buddy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Iterating on the Cardputer-Adv MicroPython “Cardputer Buddy” app bundle is slow when you have to re-flash for every small change, so developers need a faster workflow to add new apps, push updates, and debug what the device is doing over serial logs.

Core Features & Use Cases

  • Add apps via a local buddy/device/apps workflow: Create or adapt an app module (e.g., based on the provided hello and snake examples) so it appears in the device launcher menu without rebuilding the whole payload.
  • Push single-file changes: Upload only the modified .py (or a small subset) over USB-serial instead of performing full device re-flashing.
  • Debug with device serial logs and one-shot commands: Tail serial output and run REPL one-liners to inspect the device filesystem and verify behavior after pushing changes.
  • Best fit use cases: Following up after initial /maker-setup, adding a new app, updating Claude Buddy/MicroPython payload behavior, and iterating on BLE/UI/state/protocol integration.

Quick Start

Ask Claude Code to help you push a single changed app file to your already-provisioned Cardputer over USB-serial and verify the result by tailing the device logs.

Frequently Asked Questions about cardputer-buddy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I push a single changed MicroPython file to Cardputer without re-flashing?▼

Push a single changed MicroPython .py file to Cardputer without re-flashing by using the provided onboard/scripts tooling to upload the modified file over USB-serial directly to the /flash/apps/ deployment directory on the detected device port.

How do I add a new app to the Cardputer MicroPython launcher menu?▼

Add a new app to the Cardputer launcher menu by creating or adapting an app module within the local buddy/device/apps workflow, allowing it to appear in the launcher without rebuilding the entire payload.

Can I tail serial logs and run REPL commands on Cardputer during app debugging?▼

Tail serial logs and run one-shot REPL inspection commands on Cardputer to debug device behavior, inspect the filesystem, and verify results immediately after pushing incremental app updates over USB-serial.

Do I need to run m5-onboard provisioning before using the Cardputer incremental update workflow?▼

You need to run m5-onboard provisioning and /maker-setup first to establish the local build-with-claude buddy/ payload layout before applying incremental app updates, single-file pushes, or serial debugging.

What is the best way to iterate on Cardputer BLE client and UI integration?▼

The best way to iterate on Cardputer BLE client, UI, and state protocol integration is pushing single modified .py files over USB-serial and verifying behavior by tailing device serial logs, avoiding full payload rebuilds.

Why does pushing an app update to Cardputer fail to appear in the launcher menu?▼

Pushing an app update fails to appear in the launcher menu if the file is not deployed to the correct /flash/apps/ directory or if the device port detection fails during the USB-serial upload via the onboard/scripts tooling.