what’s the best way to create a repository pattern that is not dependent on prisma’s data structures? For instance, I want to create a repository with a “create” method:

async create(data: Prisma.AutoCreateConfigurationCreateInput) {
  return await prismaClient.autoCreateConfiguration.create({
    data,
  });
}

The problem with the above code is that the method signature has a direct dependency on “prisma” which seems like an anti-pattern since the whole point of repositories are to abstract away the data access implementation details. Anyone have any good patterns they use here?