Use when adding or changing P2P message types, payloads, or wire protocol behavior.
When adding or changing P2P message types, payloads, or wire protocol behavior, follow these steps.
lib/p2p.ts (or shared types used by P2P and stores). Ensure message payloads are clearly typed.documentation/protocol.md to match: message names, fields, when sent, who sends. Keep the doc as the single source of truth for the wire protocol.Ask the user if the change should be backward-compatible with existing clients. If so, consider version fields or optional fields and document in documentation/protocol.md.
Use this skill when the user adds or changes P2P messages, wire protocol behavior, or asks to keep protocol and docs in sync.