skills.rest
Hankanman
HankanmanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

zenstack-relation-naming-discovery

Inspect ZenStack and Prisma schemas to identify actual relation field names.

1|Updated Jan 23, 2026
Search Tags:#typescript#debugging#prisma#schema-discovery#relation-naming#zenstack
One-click install
npx skills add https://github.com/Hankanman/claude-config --skill zenstack-relation-naming-discovery
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: zenstack-relation-naming-discovery
Source: https://github.com/Hankanman/claude-config/tree/main/config/skills/zenstack-relation-naming-discovery
Command: npx skills add https://github.com/Hankanman/claude-config --skill zenstack-relation-naming-discovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ZenStack/Prisma projects sometimes expose relation field names that differ between the schema and generated client. This skill helps you discover the actual field names on model instances to fix type errors and runtime issues efficiently.

Core Features & Use Cases

  • Inspect schema definitions to determine the actual relation field names used by ZenStack.
  • Verify against generated TypeScript types to confirm exact field names on model instances.
  • Validate through a targeted query by including suspected relations and inspecting the resulting data keys.
  • Update application code to reference the real field names, reducing TS errors and runtime failures.

Quick Start

Run a quick discovery by checking your ZenStack schema for relation field names, compare with generated types, and test a small query to confirm the actual field names in your runtime data.

Frequently Asked Questions about zenstack-relation-naming-discovery

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

FAQPage Schema
How do I find the actual ZenStack relation field names causing TypeScript errors?▼

To resolve ZenStack relation field name TypeScript errors, inspect your zmodel or prisma schema definitions to cross-check the generated types and confirm the exact relation field names on model instances.

Why does my Prisma query fail to access a relation property at runtime?▼

Runtime failures accessing Prisma relations often occur when schema relation field names differ from the generated client, requiring you to run a targeted query including suspected relations and inspecting the resulting data keys.

What is the best way to verify ZenStack relation names across my database models?▼

The best way to verify ZenStack relation names is to inspect schema definitions, compare them against generated TypeScript types, and execute a targeted query to validate the actual field names present in the runtime data.

How do I fix missing relation field errors in my TypeScript schema discovery process?▼

Fix missing relation field errors during schema discovery by inspecting your zmodel definitions, cross-checking the generated TypeScript types, and updating application code to reference the validated actual field names.

Can I use ZenStack schema definitions to debug mismatched Prisma relation names?▼

Yes, you can inspect ZenStack schema definitions to debug mismatched Prisma relation names by cross-checking them against generated TypeScript types and validating the exact field names with targeted database queries.

Related Skills

Explore More Software Engineering Skills→
HeldinhowHeldinhow
4

prisma-orm

Manage type-safe database access and migrations for TypeScript/JavaScript applications using Prisma ORM.

Community
Intermediate
freedomw1987freedomw1987
2

patch-route-field-silently-dropped

Diagnose and resolve PATCH/POST field drops from Prisma relation key mismatches.

Community
Advanced
boringdataboringdata
476

bsl-query-expert

Queries BSL semantic models and displays results with charts.

Community
Advanced
freedomw1987freedomw1987
2

prisma-relation-debugging

Diagnose Prisma relation errors from schema and code mismatches.

Community
Intermediate