tRPC router architecture, procedure design, and Vertical Slice Architecture patterns. Use when building tRPC APIs, designing procedures, or structuring backend slices.
71
Quality
56%
Does it follow best practices?
Impact
100%
1.47xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/framework/tech-trpc/SKILL.mdVertical slice directory structure
Feature directory
100%
100%
Operation subdirectories
0%
100%
One procedure per file
0%
100%
Repository per operation
0%
100%
No god-object repository
0%
100%
Feature router file
100%
100%
Root router wiring
100%
100%
Procedure file naming
0%
100%
Repository file naming
0%
100%
Shared procedures imported
100%
100%
No cross-layer directories
100%
100%
Without context: $0.4467 · 1m 35s · 27 turns · 34 in / 6,086 out tokens
With context: $1.0507 · 2m 38s · 51 turns · 1,415 in / 11,175 out tokens
Extracted schemas with output definitions
Search schema file
100%
100%
Detail schema file
100%
100%
Search input schema exported
100%
100%
Search output schema defined
100%
100%
Search procedure uses .output()
100%
100%
Detail input schema exported
100%
100%
Detail output schema defined
100%
100%
Detail procedure uses .output()
100%
100%
TypeScript types exported
100%
100%
No inline schema definitions
100%
100%
Procedures import from schema files
100%
100%
Without context: $0.4004 · 1m 32s · 25 turns · 30 in / 5,470 out tokens
With context: $0.8890 · 2m 51s · 45 turns · 1,848 in / 10,845 out tokens
Authorization levels and domain-specific errors
Get plan uses org procedure
100%
100%
Change plan uses admin procedure
100%
100%
Cancel uses admin procedure
100%
100%
No publicProcedure for auth routes
100%
100%
Domain-specific error classes
0%
100%
Error classes extend TRPCError
0%
100%
NOT_FOUND code used
100%
100%
Appropriate error codes
0%
100%
No generic errors thrown
0%
100%
Procedures import shared procedures
100%
100%
Feature router combines procedures
100%
100%
No cross-slice imports
100%
100%
Without context: $0.5518 · 2m 48s · 26 turns · 29 in / 10,202 out tokens
With context: $1.7491 · 4m 44s · 65 turns · 2,413 in / 19,743 out tokens
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.