FIELD GUIDE / 07
Build an AI Passport play with TRAE
Describe the play in TRAE Work, complete the code and build, then install the new experience on a wearable AI Passport.
STEP / 01
Connect the device and confirm the install baseline
Connect AI Passport with a USB data cable and install one published release from the official play library. This confirms the browser serial permission, cable, and device before custom development.

This removes connection uncertainty and establishes a clear recovery path for custom play work.
STEP / 02
Open the play project in TRAE Work
Enter TRAE Work and open the complete play directory as the project. Ask the agent to read the instructions, build scripts, target hardware, and existing play examples, then summarize its plan before editing.
Please download and use this project as a reference:
https://github.com/folotoy/ai-passport
Help me build a wooden-fish tapping app.
Keep modifications and command execution inside the project instead of generating a detached code snippet in chat.
STEP / 03
Describe the custom play you want
Describe the context, first screen, interaction flow, and successful outcome in plain language. Add requirements for the three physical buttons, audio, Bluetooth, or networking, and keep the first version small enough to verify quickly.

- Who uses it and in what context
- Screens and states that must appear
- How each physical button behaves
- Definition of done and explicit version-one boundaries
STEP / 04
Let TRAE code, build, and check the result
Have TRAE implement the agreed plan, run the project's build command, and continue fixing compiler errors. Ask for the changed files, verification result, play path, and anything that still needs hardware testing.
Do not stop after code generation. Confirm that the build succeeds and produces a real installable play.
STEP / 05
Install the play and check each feature
Open the local play installer, select the TRAE build, and write it to the test device. Restart and check the first screen, buttons, audio, connectivity, and failure recovery.

- Keep USB connected while writing
- Test on a development device and retain a recovery build
- Record reproduction steps and logs for every failure
STEP / 06
Use it as a wearable device
Wear or carry the device long enough to check outdoor readability, one-handed controls, connection stability, and battery behavior. Return the highest-impact issues to TRAE for another focused edit, build, and installation cycle.

- Prioritize real context over a desk demo
- Address only a small set of important issues per iteration
- Keep source and play backups for every stable version