AGENT SKILLS · ÉQUIPEMENT DE MISSION / middleapi

middleapi · Agent Skills

4 skills with substantive source documentation and an official publisher or observed installation demand. Read each skill’s original documentation through its card.

middleapi
Communauté

orpc

Build, serve, and call end-to-end typesafe APIs with oRPC v2. Use for any task in a project that depends on @orpc/ packages, even a one-procedure change: defining procedures with the os builder (.input/.output/.handler, any Standard Schema validator), assembling routers, middleware and context, typesafe errors with ORPCError, serving via RPCHandler on any runtime adapter, calling from server-side clients (call, createRouterClient) or client-side clients (createORPCClient with RPCLink), integrati

installations
2
GitHub Stars
5,7 k
Mis à jour
8 oct.
middleapi
Communauté

orpc-contract

Design oRPC v2 APIs contract-first, defining the API shape with oc from @orpc/contract, implementing it with implement from @orpc/server, and consuming the contract from typesafe clients. Use when a project depends on @orpc/contract, when defining a contract with oc, implementing a contract with implement, sharing an API contract between server and client packages, generating a contract from an existing OpenAPI spec, or publishing a typed API client to npm. Biases toward retrieval from the oRPC

installations
2
GitHub Stars
5,7 k
Mis à jour
8 oct.
middleapi
Communauté

orpc-migrate

Migrate existing codebases to current oRPC, covering tRPC to oRPC (incremental wrapping via the @orpc/trpc integration or a full rewrite with the concept mapping) and oRPC v1 to v2 (package renames, breaking changes, and a safe order of operations). Use when asked to migrate from tRPC to oRPC, convert or wrap a tRPC router, upgrade oRPC v1 to v2, fix oRPC v2 breaking changes, or swap @trpc/ packages for @orpc/ equivalents. Biases toward retrieval from the oRPC docs over pre-trained knowledge. No

installations
2
GitHub Stars
5,7 k
Mis à jour
8 oct.
middleapi
Communauté

orpc-openapi

Expose an oRPC router as a spec-compliant OpenAPI HTTP API. Use when a project depends on @orpc/openapi, or for defining REST-style routes on oRPC procedures (openapi() metadata or .route with method, path, successStatus), serving them with OpenAPIHandler alongside RPCHandler, coercing query and path strings with Smart Coercion, calling an OpenAPI-shaped API with OpenAPILink, generating an OpenAPI 3.2 (or 3.1, 3.0) document with OpenAPIGenerator, or serving Scalar or Swagger docs with the OpenAP

installations
2
GitHub Stars
5,7 k
Mis à jour
8 oct.