PeerTalk
SDK for logging and networking across modern and retro Macs
PeerTalk is currently under development. The project serves both as a production SDK and as a working example of Claude Code's advanced features (MCP servers, skills, hooks, and tools). You can follow along or build it yourself using the implement skill.
The Project
PeerTalk is an SDK for logging and networking over UDP and TCP, designed to work across modern macOS and Classic Mac OS systems. The logging system provides consistent debugging and diagnostics regardless of platform, whilst the networking layer abstracts away the differences between modern BSD sockets, MacTCP, and OpenTransport.
But PeerTalk is also a teaching project. The repository is set up as a real-world example showing how to write project-specific MCP servers, hooks, skills, and tools for Claude Code. The MCP servers inject Classic Mac OS API documentation and build logs as context. Hooks run compatibility checks when networking code changes. The implement skill breaks the SDK development into structured phases with verification steps.
The Setup
The repository includes a starter template with all the Claude Code tooling configured:
- MCP servers providing project-specific context
- Custom skills for iterative development workflows
- Hooks automating common tasks
- The implement skill with step-by-step development plans
Anyone with Claude Code and basic knowledge can clone the project and have a go at building the SDK themselves. The implementation plan is there, the tools are configured, and the implement skill guides you through it step by step.
Tech Stack
Learnings from CSend
CSend taught me that getting retro and modern systems talking to each other is definitely possible with Claude's help, especially when you feed it the right documentation. But the code was rough around the edges. I wanted to do it properly this time - clean abstractions, proper error handling, and a design that others could actually use in their own projects.
The Anthropic workshop gave me the tools to structure the development process better. Using skills to break down the work, MCP servers to maintain context, and hooks to automate repetitive tasks makes iterative development much smoother than the ad-hoc approach I took with CSend.
Current Status
The project structure, planning documents, and Claude Code tooling are in place. The SDK implementation is progressing iteratively using patterns from a workshop hosted by Anthropic that I attended. You can follow the progress in the repository or try building it yourself using the implement skill.