FIELD GUIDE / 06

Build an AI Passport play with Claude Code

Let Claude Code understand the play project and hardware constraints, produce an installable build, and refine it from device feedback.

STEP / 01

Choose a focused play and a minimum goal

Define the custom play in one sentence and keep the first version to one core flow: a learning exercise, a short game, or a wearable reminder. Avoid adding too many screens and connection features at once.

AI Passport showing a custom rabbit interaction — Start with one custom experience that fits the device

Name the user and real context
Define where one complete interaction starts and ends
List what version one must include and explicitly excludes

STEP / 02

Open the play directory in Claude Code

Start Claude Code from the play project root. Ask it to read the project instructions, build scripts, target-chip configuration, and the closest examples, then explain which files it plans to change.

Prompt for the Agent

Please download and use this project as a reference:
https://github.com/folotoy/ai-passport
Help me build a wooden-fish tapping app.

The Claude Code screen shown in the video — Start Claude Code in the complete play directory

Tip
Preserve the project's existing structure and commands. Reuse current display, button, and asset-loading code before introducing unrelated refactors.

STEP / 03

Add the AI Passport hardware constraints

Include the display, three physical buttons, audio, and connection capabilities in the task. Describe every screen state and exit path, and tell Claude Code to follow the hardware interfaces already supported by the project.

Open AI Passport hardware connected over USB — Keep every requirement grounded in the real device

Display content, refresh behavior, and asset limits
Up, Down, and Confirm behavior
Offline, Bluetooth, networking, or storage needs
Startup, failure, retry, and exit states

STEP / 04

Let Claude Code edit, build, and summarize

Have Claude Code implement the agreed plan, run the project's build and check commands, and continue from compiler errors. Ask for a change summary, verification results, and the final play path.

Tip
If only the source changes are complete, ask it to run the real build. Continue to installation only after the build succeeds and the artifact exists.

STEP / 05

Install the play on a development device

Use the local play installer to select the Claude Code build. Verify the device and file before installation, restart afterward, and check the first screen, buttons, audio, and required connectivity.

A Claude Code build running on a real AI Passport — Complete the first verification on real hardware

Keep a recoverable build before installation
Maintain a stable USB connection while writing
Record unexpected visuals, reproduction steps, and device logs

STEP / 06

Continue from hands-on feedback

Have the intended user complete one real task with the device. Observe whether instructions are clear, controls feel natural, and feedback is timely. Return the most important issues and reproduction steps to Claude Code for another focused change.

A child using AI Passport as a learning tool — Bring real use feedback into the next Claude Code iteration

Fix issues that block the core flow first
Change only a small set of testable details per iteration
Keep the source commit, play, and test notes for stable versions