AGENTS.md, instructions
agents read on their own. It tells the agent to keep your pins and puzzle
logic, use ed::Room, and compile for your exact board before it reports back.
Give your agent these docs
These docs are built for AI tools as well as people:
To add the MCP server to Claude Code, run:
.cursor/mcp.json:
Set up the folder
- Extract the SDK download.
- Copy your sketch into its
workspacefolder, such asworkspace/vault_keypad. Git ignores this folder. - Open the extracted SDK folder in your agent. Claude Code reads
CLAUDE.md, which points toAGENTS.md; most other agents readAGENTS.mddirectly.
AGENTS.md first.
Describe the prop
Tell the agent the facts it can’t see in the code. Replace the brackets:Read AGENTS.md and add the Escape Director SDK to workspace/[sketch] for [exact board]. Keep my pins, output polarity, puzzle logic and reset behavior. The prop is solved when [condition]. Give the Game Master [commands] and show [state]. Keep any existing prop and capability IDs. Read the sketch first and ask about wiring or behavior it doesn’t show. Compile for my board and report the result. Don’t upload without asking me.For example: “Add the SDK to workspace/vault_keypad for the UNO R4 WiFi. Make one prop that’s solved when 4-7-1-9 is entered, with Reset and Open latch commands.”
Check the agent’s work
Ask the agent to hand off:- The files it changed.
- The pins, wiring and IDs it kept.
- The exact compile command and its result.
- The core and library versions it used.
- What it couldn’t check.
- Upload the sketch with prop loads disconnected.
- Pair the board or update its connection, as in Build your own controller.
- In Test mode, run each command and watch the physical output.
- Run a practice game to check signals, linked Puzzles and Automations.