tech-trpc

Create a reusable library of tiled, 2D game maps and share them with the world.

16|15|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/ravnhq/ai-toolkit --skill tech-trpc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-trpc
Source: https://github.com/ravnhq/ai-toolkit/tree/main/skills/tech-trpc
Command: npx skills add https://github.com/ravnhq/ai-toolkit --skill tech-trpc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides architecture patterns and rules to help teams design scalable, type-safe tRPC APIs. It codifies how to structure procedures, schemas, and repositories to reduce coupling and improve maintainability.

Core Features & Use Cases

  • Vertical Slice Architecture: organize features end-to-end, with each slice owning procedures, schemas, and tests.
  • One Procedure Per File: keep operations focused and testable.
  • No Cross-Slice Imports: promote loose coupling via events or shared services.
  • Repository Per Slice: keep data access scoped to each feature.
  • Domain-Specific Errors: provide precise error handling and codes for clients.
  • Use of Procedure Hierarchy: apply public, protected, organization, and admin procedures appropriately.

Quick Start

Install or configure the skill within your toolkit, then start modeling slices under features/ by defining create, read, update, delete procedures with associated schemas and repositories.

Frequently Asked Questions about tech-trpc

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure a scalable tRPC API to reduce coupling?▼

Use vertical slice architecture to structure tRPC APIs, organizing features end-to-end so each slice owns its procedures, schemas, and tests, which reduces coupling and improves maintainability.

What is the best way to organize tRPC procedures for testability?▼

Enforce a one-procedure-per-file rule to organize tRPC procedures, keeping operations focused and testable across feature slices.

How do I manage data access in a modular tRPC backend?▼

Assign a repository per slice to manage data access in modular tRPC backends, keeping data operations scoped to each specific feature rather than shared globally.

How do I implement precise error handling in tRPC APIs?▼

Define domain-specific errors to implement precise error handling in tRPC APIs, providing accurate error handling and codes for clients consuming the procedures.

Can I use procedure hierarchy to manage access control in tRPC?▼

Apply public, protected, organization, and admin procedures appropriately across feature slices to use procedure hierarchy for managing access control in tRPC.

Why should I avoid cross-slice imports in tRPC architecture?▼

Avoid cross-slice imports in tRPC architecture to promote loose coupling between features, relying instead on events or shared services for communication.