rpcable

Expert workflow for implementing, debugging, and refactoring projects that use rpcable. Use this skill whenever the user mentions RpcAble, RpcAbleReceiver, socket.io RPC, native WebSocket RPC, HTTP RPC, Bun.serve, Express adapters, UserSession architecture, collector/pending push queues, role permissions, contract/inputSchema validation, PHP adapter parity, or transport parity. Trigger even when the user asks generic things like "sistema la sessione", "fai parity http/ws", or "migliora DX" in a codebase that contains rpcable patterns.

Focused workflow for reproducing concrete rpcable session/runtime bugs with a disposable Node lab under .claude/rpcable-session-lab. Use this in projects that use rpcable when a specific user, session, or transport is misbehaving and the fastest path is to spin up a scripted client, replay the same RPC calls, and inspect outbound batches, responses, push events, headers, or raw socket traffic. Examples: "Carmelo does not receive chat messages", "latest posts never arrive", "HTTP push is empty", "socket.io join works but follow-up events disappear". Do not use this for generic refactors or architecture work; use rpcable-expert for those.