All build paths

Build with the GitHub Copilot App

Describe your idea in the GitHub Copilot desktop app. Copilot builds the app and copies it to your connected badge. You test it on the badge.

These steps work on Windows and macOS. They assume the GitHub Copilot App, Python 3.10 or newer, and hyb26-skill are already installed. The skill is a set of instructions and tools that helps Copilot build apps for this badge. Installation is not covered here. Use the GitHub Copilot app, not Microsoft Copilot. You do not need to write code yourself.

1. Connect the badge

Connect the badge to your computer with a USB cable that transfers data. Leave it connected while Copilot works. You do not need to enter Disk Mode before you start.

When Copilot is ready to copy your app, hyb26-skill switches the badge into USB Disk Mode. The badge restarts and appears as a BADGER drive on your computer. This is expected.

If automatic Disk Mode fails: quickly press RESET twice, then ask Copilot to try again. If it still cannot find BADGER, check the USB data cable and ask staff for help.

If you see RP2350, stop: that drive is for firmware updates, not apps. Do not copy files to it, erase the drive, or change the firmware.

2. Open a local project in the Copilot App

  1. Open the GitHub Copilot App.
  2. Under Projects, select the Badge Projects folder prepared for you.
  3. Start an Interactive session for that local project.

Use a local session on your computer, not a cloud session. A cloud session cannot access the badge plugged into your computer. Use the project session, not a general chat, so Copilot has a place to save your app.

3. Describe your app

Tell Copilot what you want to make in your local session and ask it to use hyb26-skill. The prompt below is only an example. You do not need to copy it or use it as written; describe your own idea in your own words.

Use hyb26-skill to make a badge app with a counter that increases when I press SELECT. Walk me through anything I need to do with the badge using plain English.

Answer Copilot's questions. If a permission request appears, check that it is for your local project, the installed skill tools, or BADGER before allowing it. You may still need to approve a tool action; the prompt does not bypass those controls. Do not use an allow-everything option.

On macOS, your tool may also ask for access to Documents or removable volumes. Allow only access needed for this work; do not grant broad disk access or disable safety settings.

Copilot should check the app before copying it. If the skill, Python, or badge tools are missing, or Copilot cannot identify the badge, ask staff for help rather than skip the checks.

4. Test on your badge

Wait until Copilot says copying has finished. The skill can eject BADGER and wait for the badge to restart into its menu. Follow Copilot's test steps:

  1. Open your app from the badge menu. If the menu has not returned after ejecting, press RESET once.
  2. Try its screens and buttons, then press HOME to return to the menu.
  3. If the app saves data, reopen it and check the data after a reset too.

Copilot can check files and copy them, but it needs you to report what the badge displays and how the controls work. Sensors and wireless features need tests on the real badge; passing file checks does not prove they work.

If you need to eject by hand, wait until copying has finished, then use the steps for your computer:

Windows: press Windows key + E to open File Explorer. Under This PC, right-click BADGER and choose Eject. Its drive letter may differ between computers.

macOS: open Finder and click the Eject button beside BADGER under Locations. If external disks are hidden, enable them in Finder > Settings > Sidebar.

Wait for BADGER to disappear. If it is still present and your computer says it is in use, close files or terminals using the badge and try again; do not force eject. The badge normally returns to its menu by itself. Press RESET once if it does not.

5. Continue building

Tell Copilot what you want to change. If the badge shows an error, give Copilot the error message as best as you can and ask it to try to fix it. If anything is unclear, ask a volunteer for help.

Reconnect the badge if needed. The skill handles Disk Mode for the next copy; follow Copilot's steps to copy and test the updated app.

When updating your own app, tell Copilot it is an update so it uses the skill's replacement option and keeps a backup. Do not replace someone else's app or change shared badge files.

If Copilot cannot copy your app, ask it for the full path to your checked app folder and the correct BADGER destination. With Copilot's guidance, you can copy that one folder in File Explorer on Windows or Finder on macOS, then eject and test as above. Do not disable broad safety settings to give access.