Skills
.Work. You
Rest

aim-gateway-domain

Community

Define AIM Gateway boundaries and APIs.

Software Engineering#rest api#websocket#grpc#gateway#api contract#protocol governance#aim
Authorhellopoisonx
Version1.0.0
Installs0

System Documentation

What problem does it solve?

It prevents accidental leakage of public REST/WebSocket endpoints from non-gateway services and keeps AIM client-facing contracts consistent across gateway and related protocols.

Core Features & Use Cases

  • External interface boundary governance: Enforces that only the gateway domain exposes public REST APIs and the WebSocket entry, while other domains must use internal gRPC/Kafka and must not publish REST/WS ports in Docker.
  • Gateway contract documentation: Centralizes REST proxy boundaries, WebSocket frame responsibilities, and gRPC push semantics (message, presence, typing, notifications, kick, drain).
  • Change tracking for client-facing schemas: Maintains a recent-changes log that highlights updates like friend tags, unified search, read receipts, typing/presence pipelines, and schema field alignment.

Quick Start

Use the aim-gateway-domain references to review the external interface rules and the relevant REST/WebSocket/gRPC contract documents before implementing or modifying any gateway-related feature.

Dependency Matrix

Required Modules

None required

Components

references

💻 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-gateway-domain
Download link: https://github.com/hellopoisonx/aim/archive/main.zip#aim-gateway-domain

Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
View Source Repository

Agent Skills Search Helper

Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.