peapod-platform-impl

Sterne0

Forks0

Aktualisiert7. Februar 2026 um 14:57

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.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

Quelle

HKTITAN

HKTITAN/PeaToPea

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	peapod-platform-impl
description	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.

PeaPod Platform Implementation

When working on a protocol implementation for a specific OS:

Reference the right .tasks file: .tasks/02-windows.md, .tasks/03-android.md, .tasks/04-linux.md, .tasks/05-ios.md, or .tasks/06-macos.md. Implement the checklist items; do not put platform I/O (sockets, VPN, proxy) inside pea-core.
Use pea-core as dependency: The implementation crate (e.g. pea-windows) depends on pea-core. Call into pea-core for protocol logic, chunking, scheduling, and integrity; the implementation handles discovery, traffic interception, and local transport.
Wire format and discovery: Keep the same wire format and discovery protocol as defined in pea-core and .tasks/07-protocol-and-interop.md. All platforms must interoperate (e.g. Windows and Android in the same pod).
Platform-specific mechanisms: Use the correct OS mechanism for traffic interception (e.g. system proxy or WinDivert on Windows, VPNService on Android, Network Extension on iOS/macOS). Document any platform constraints in the implementation or .tasks.

Mehr aus diesem Repository

gleiches Repository

architecture-guide

HKTITAN/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.

2026-02-090

commit-and-cursor

HKTITAN/PeaToPea

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).

2026-02-070

peapod-build-test

HKTITAN/PeaToPea

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).

2026-02-070

peapod-tasks

HKTITAN/PeaToPea

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.

2026-02-070

name	peapod-platform-impl
description	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.

PeaPod Platform Implementation

When working on a protocol implementation for a specific OS:

Reference the right .tasks file: .tasks/02-windows.md, .tasks/03-android.md, .tasks/04-linux.md, .tasks/05-ios.md, or .tasks/06-macos.md. Implement the checklist items; do not put platform I/O (sockets, VPN, proxy) inside pea-core.
Use pea-core as dependency: The implementation crate (e.g. pea-windows) depends on pea-core. Call into pea-core for protocol logic, chunking, scheduling, and integrity; the implementation handles discovery, traffic interception, and local transport.
Wire format and discovery: Keep the same wire format and discovery protocol as defined in pea-core and .tasks/07-protocol-and-interop.md. All platforms must interoperate (e.g. Windows and Android in the same pod).
Platform-specific mechanisms: Use the correct OS mechanism for traffic interception (e.g. system proxy or WinDivert on Windows, VPNService on Android, Network Extension on iOS/macOS). Document any platform constraints in the implementation or .tasks.