connectrpc-architectlisted
Install: claude install-skill ralvarez-ai/ralvaskills
# ConnectRPC Architecture
ConnectRPC (`connectrpc.com/connect`) serves **Connect**, **gRPC** and **gRPC-Web** from one generated `http.Handler` — one `.proto`, no gateway in front of the browser. Pair with [protobuf-architect](../../encoding/protobuf-architect/SKILL.md) for schema design. Go skeletons in [RECIPES.md](RECIPES.md); pinned deps in [STACK.md](STACK.md). Other languages follow the same protocol-level conventions with idiomatic substitutions.
## 1. The value proposition — one handler, three protocols
A single `buf`-generated handler is mounted once and answers all three wire protocols:
| Protocol | Wire | Callers | Notes |
|---|---|---|---|
| **Connect** | `POST` + JSON or Protobuf, HTTP/1.1 or 2 | Any HTTP client, browsers | No proxy; `curl`-able with `-H 'Content-Type: application/json'` |
| **gRPC** | Length-prefixed Protobuf, HTTP/2 | gRPC clients, backend-to-backend | Same `grpc-status` trailers as vanilla gRPC |
| **gRPC-Web** | Protobuf, trailers encoded in the body | Browsers via `@connectrpc/connect-web` | No proxy/gateway required |
**House position:**
- **`.proto` is the RPC contract** — the source of truth for the RPC surface, exactly as for [grpc-architect](../grpc-architect/SKILL.md).
- **Connect is the primary adapter.** New Go services generate the Connect handler and mount it as the RPC entrypoint.
- **Keep a native gRPC adapter from the same proto as deliberate insurance.** Registering the same implementation on a `*grpc.Server` costs one mo