trpc
tRPC end-to-end type safety, procedures, routers, middleware, and React integration.
npx skills add a5c-ai/babysitter --skill trpc --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# tRPC Skill Expert assistance for building type-safe APIs with tRPC. ## Capabilities - Create type-safe procedures and routers - Implement middleware for auth/validation - Set up tRPC with Next.js/React - Handle subscriptions - Configure error handling - Build type-safe client hooks ## Usage Invoke this skill when you need to: - Build end-to-end type-safe APIs - Integrate with React/Next.js - Replace REST with type-safe RPC - Implement real-time features ## Patterns ### Router Definition ```typescript // server/trpc/routers/user.ts import { z } from 'zod'; import { router, publicProcedure, protectedProcedure } from '../trpc'; import { TRPCError } from '@trpc/server'; export const userRouter = router({ list: protectedProcedure .input(z.object({ page: z.number().min(1).default(1), limit: z.number().min(1).max(100).default(10), search: z.string().optional(), })) .query(async ({ ctx, input }) => { const users = await ctx.prisma.user.findMany({ where: input.search ? { name: { contains: input.search } } : undefined, skip: (input.page - 1) * input.limit, take: input.limit, }); return users; }), byId: protectedProcedure .input(z.string()) .query(async ({ ctx, input }) => { const user = aw
- Capabilities
- Usage
- Patterns
- Router Definition
- React Integration
- Best Practices
- Target Processes
What does the trpc skill do?
tRPC end-to-end type safety, procedures, routers, middleware, and React integration.
How do I install it?
Run `npx skills add a5c-ai/babysitter --skill trpc --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From a5c-ai/babysitter, a repository with 1,642 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.