Building a Jira Clone with KickJS and Prisma: Lessons from Supporting Prisma 5, 6, and 7

How we built a decorator-driven Node.js framework adapter for Prisma ORM, what worked, and what didn't. We recently shipped Prisma support for KickJS , our decorator-driven Node.js framework built on Express 5 and TypeScript. The goal was to make kick g module --repo prisma generate a fully working DDD module with Prisma repositories — no manual wiring needed. Along the way, we built a full Jira-style project management API as a reference app, migrated it across Prisma 5/6 and Prisma 7, and ran into some interesting type safety challenges. Here's what we learned. What We Built The @forinda/kickjs-prisma adapter provides: PrismaAdapter — lifecycle adapter that registers PrismaClient in the DI container PrismaQueryAdapter — translates parsed query strings into Prisma findMany arguments PrismaModelDelegate — typed interface for model CRUD operations (more on this below) CLI integration — kick g module users --repo prisma generates a complete DDD module with working Prisma repositories The