Define and wire Connect-RPC API endpoints in the Shorts backend.
npx skills add https://github.com/castlemilk/shorted.com.au --skill api-endpoints
Please help me install this Agent Skill. Skill: api-endpoints Source: https://github.com/castlemilk/shorted.com.au/tree/main/.claude/skills/api-endpoints Command: npx skills add https://github.com/castlemilk/shorted.com.au --skill api-endpoints
Defining and wiring new Connect-RPC API endpoints in the Shorts backend is a structured, repeatable process that minimizes integration errors and accelerates feature delivery.
Define the new protobuf method, run code generation, implement the corresponding store and service handlers, and add tests.
High-intent search queries and answers about installing and using this skill.
To add new Connect-RPC endpoints, you define new protobuf methods and messages in proto files, run code generation, and implement the corresponding store and service handlers. This structured process minimizes integration errors across the API surface.
Expanding a protobuf-driven API surface involves defining new methods in proto files, regenerating Go types and TypeScript clients using code generation, and wiring the backend handlers. This ensures client SDKs remain in sync with backend services.
You generate Go and TypeScript client code from protobuf definitions by running buf generate after updating your proto files. This automatic code generation creates the necessary types and clients to keep your frontend and backend synchronized.
Yes, creating new RPC methods requires manually updating store and service implementations. After defining the protobuf and regenerating code, you must wire the end-to-end backend handlers and add tests to ensure reliability.
Use Connect-RPC for backend API expansion when you need a structured, repeatable process to add new features and extend APIs. It is ideal for projects requiring protobuf-driven definitions and automatic generation of client SDKs.
Automatic code generation handles creating types and clients, but it does not implement the actual business logic. You must manually wire the store methods and RPC handlers, and add tests to ensure the new endpoints function reliably.
ArtisanCloudGenerate protobuf definitions and Go stubs for PowerX services.
viqueenGenerate unit and integration tests for Go backend services with Connect-RPC and gRPC.
nahisahoDesign RESTful, GraphQL, and gRPC APIs with OpenAPI and Protobuf definitions.
vesvietAutomate gRPC client implementation for Go microservices with Kratos and Wire.
