PeaToPea

Use when making architectural decisions, adding components, or understanding how PeaPod's pieces fit together. Provides context on the protocol design, component boundaries, and data flow to help agents make correct design choices.

Use when finishing a chunk of work or when the user asks to commit or to update Cursor context. Commit and push with a clear message; optionally add or update a rule, skill, or subagent in .cursor. Execute without prompting (autonomous mode).

Use when building, testing, or verifying pea-core or the workspace. Run cargo build and cargo test for pea-core from repo root; fix compilation or test failures. Execute without asking for confirmation (autonomous mode).

Use when implementing features or fixes that correspond to .tasks checklists. Open the relevant .tasks file (e.g. 01-pea-core, 02-windows), implement unchecked items, and mark completed items with [x]. Run fully autonomously: no confirmation for build, test, commit, or push.

Use when working on Windows, Android, Linux, iOS, or macOS protocol implementations (pea-windows, pea-android, etc.). Follow the corresponding .tasks file (02–06); ensure wire format and discovery match pea-core and .tasks/07.