aim-proto-domain
CommunityDefine AIM protobuf contracts across services
System Documentation
What problem does it solve?
It solves the problem of keeping AIM’s cross-platform, cross-service protobuf protocol consistent and evolvable by centralizing the wire-level contract and the rules that govern field meanings, framing, and compatibility.
Core Features & Use Cases
- Protocol contract documentation: Captures frame types, field-number semantics, and service-to-service RPC expectations so gateway, core, and clients remain interoperable.
- Backward-compatibility guidance: Documents rules like presence/target user fallbacks and “append-only” field numbering/meaning constraints.
- Usage guidance for proto generation: Provides the correct protoc commands and checks to prevent duplicated output or go_package issues.
Use it when you need to review or implement changes to AIM’s websocket binary frames, gateway/core gRPC push APIs, and message semantics such as mentions, system messages, conversation_type, typing, presence, and read receipts.
Quick Start
Review the protocol contract and update rules in references/protocol-rules.md before generating or changing any shared protobuf definitions.
Dependency Matrix
Required Modules
None requiredComponents
💻 Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: aim-proto-domain Download link: https://github.com/hellopoisonx/aim/archive/main.zip#aim-proto-domain Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
Agent Skills Search Helper
Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.