Generate Connect RPC CRUD handlers from proto service definitions.
npx skills add https://github.com/reliant-labs/forge --skill api-reliant-labs
Please help me install this Agent Skill. Skill: api Source: https://github.com/reliant-labs/forge/tree/main/internal/templates/project/skills/forge/api Command: npx skills add https://github.com/reliant-labs/forge --skill api-reliant-labs
This Skill helps you write production-grade Connect RPC handlers by standardizing proto-driven CRUD behavior, RBAC enforcement, pagination semantics, and consistent error handling so clients receive correct codes without leaking internals.
Use the api Skill to implement a new Connect service by adding your proto definitions (CRUD naming, optional List filters, required_roles, and pagination fields) and then writing any hand-crafted handler methods in the service layer’s handler location using connect.NewError for precise error codes.
High-intent search queries and answers about installing and using this skill.
To generate Connect RPC handlers from proto service definitions, define your RPCs using standardized CRUD naming, optional List filters, required_roles, and pagination fields to unlock auto-generated handler code, RBAC enforcement, and AIP-158 cursor pagination.
To map internal errors to Connect RPC codes, use connect.NewError with appropriate Connect codes like InvalidArgument, NotFound, PermissionDenied, Unauthenticated, or Internal, ensuring server details are kept out of client responses for safety.
To implement cursor-based pagination for Connect RPC List methods, define pagination fields in your proto service definition, which enables AIP-158 cursor pagination semantics automatically within the generated handler conventions for your List endpoints.
To structure Connect RPC handlers for maintainability, implement them as thin wire-format glue that validates inputs, extracts auth context via middleware, converts proto types to internal inputs, calls service-layer contracts, and wraps errors consistently with unit and integration tests.
To ensure data consistency for multi-step mutations in Connect RPC handlers, use ORM operations from your internal database layer within explicit transactions, guaranteeing that complex state changes remain atomic and consistent.
To enforce role-based access control in Connect RPC endpoints, define per-method required_roles within your proto service definitions, which translates into RBAC-gated endpoints that extract and validate auth context via middleware during request handling.
reliant-labsTranslate proto requests to internal service calls with svcerr error wrapping.
viqueenGenerate unit and integration tests for Go backend services with Connect-RPC and gRPC.
figueroaignacioSet up Express.js servers with middleware, JWT authentication, and Sequelize database integration.
reliant-labsMigrate generated CRUD RPC handlers to delegate to forge/pkg/crud.
