zenstack-v3
Skill2 starsChanged 8 months agoMITView on GitHub
ZenStack v3 schema-first ORM for TypeScript. Use when working with ZModel schemas, ZenStack ORM CRUD operations, access control policies (@@allow/@@deny), database migrations, server adapters (Next.js, Express), runtime plugins, computed fields, polymorphism, typed JSON, or migrating from Prisma/ZenStack v2. Triggers on: ZModel, ZenStack, zenstack, .zmodel files, @@allow, @@deny, auth(), PolicyPlugin, ZenStackClient, @zenstackhq/orm, zen generate, zen migrate.
- Installs packages
In this repository11 other files it gives its agents.
- concept-artSkill
- corporate-vpSkill
- eval-driven-game-developmentSkill
- game-designerSkill
- multi-agent-chatSkill
- product-illustratorSkill
- software-architectureSkill
- ue5-characterSkill
- ue5-cinematicsSkill
- ue5-gamedevSkill
- ue5-level-designSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 358
Zmodel files allow circular imports: - don't worry about circular imports in zmodel
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
ZenStack v3 — AI Coding Agent Skill
Critical Context
ZenStack v3 is a COMPLETE REWRITE. It removed Prisma as a runtime dependency and built its own ORM on Kysely. The schema language remains a "Prisma superset" but the runtime is entirely different.
Do NOT confuse with v2:
- v2 used
@zenstackhq/runtime→ v3 uses@zenstackhq/orm - v2 CLI was
zenstackpackage → v3 is@zenstackhq/cli - v2 had
abstract model→ v3 usestype+with(mixins) - v2 used
enhance(prisma, ...)→ v3 usesdb.$use(new PolicyPlugin()) - v2 generated into node_modules → v3 generates to
zenstack/folder
Supported databases: PostgreSQL, MySQL, SQLite only.
Quick Start
Installation
npm install @zenstackhq/schema @zenstackhq/orm
npm install --save-dev @zenstackhq/cli
# Plus a database driver:
npm install better-sqlite3 # or pg, mysql2Minimal Schema
// zenstack/schema.zmodel
datasource db {
provider = 'sqlite'
url = 'file:./dev.db'
}
model User {
id Int @id @default(autoincrement())
email String @unique
posts Post[]
}
model Post {
id Int @id @default(autoincrement())
title String
published Boolean @default(false)
author User @relation(fields: [authorId], references: [id])
authorId Int
}Generate & Create Client
npx zen generateimport { ZenStackClient } from '@zenstackhq/orm';
import { SqliteDialect } from '@zenstackhq/orm/dialects/sqlite';
import SQLite from 'better-sqlite3';
import { schema } from './zenstack/schema';
export const db = new ZenStackClient(schema, {
dialect: new SqliteDialect({ database: new SQLite('./dev.db') }),
});Basic CRUD
// Create
const user = await db.user.create({
data: { email: 'alice@test.com', posts: { create: { title: 'Hello' } } },
include: { posts: true },
});
// Read
const posts = await db.post.findMany({
where: { published: true },
orderBy: { createdAt: 'desc' },
include: { author: true },
});
// Update
await db.post.update({
where: { id: 1 },
data: { published: true },
});
// Delete
await db.post.delete({ where: { id: 1 } });
// Transaction
const [u, p] = await db.$transaction(async (tx) => {
const u = await tx.user.create({ data: { email: 'bob@test.com' } });
const p = await tx.post.create({ data: { title: 'Hi', authorId: u.id } });
return [u, p];
});Access Control
Setup
npm install @zenstackhq/plugin-policyplugin policy {
provider = '@zenstackhq/plugin-policy'
}
model Post {
id Int @id @default(autoincrement())
title String
published Boolean @default(false)
author User @relation(fields: [authorId], references: [id])
authorId Int
@@deny('all', auth() == null)
@@allow('read', published)
@@allow('all', auth().id == authorId)
}Runtime
import { PolicyPlugin } from '@zenstackhq/plugin-policy';
const authDb = db.$use(new PolicyPlugin());
const userDb = authDb.$setAuth({ id: currentUserId });
// All queries on userDb enforce access policiesEvaluation: deny wins → allow wins → denied by default.
Operations: create, read, update, post-update, delete, all (excludes post-update).
Key Functions
auth()— current user (type from@@authmodel orUsermodel)check(relation, operation?)— delegate to relation's policiesnow()— current datetime- Collection predicates:
relation?[cond](some),relation,relation^[cond](none)
Schema Patterns
Mixins
type Timestamped {
createdAt DateTime @default(now())
updatedAt DateTime @updatedAt
}
model Post with Timestamped {
id Int @id @default(autoincrement())
title String
}Polymorphism (MTI)
model Content {
id Int @id @default(autoincrement())
name String
type String
@@delegate(type)
}
model Post extends Content {
body String
}
model Video extends Content {
url String
}Typed JSON
type Address {
street String
city String
zip Int
}
model User {
id Int @id
address Address @json
}Computed Fields
model User {
id Int @id
postCount Int @computed
}const db = new ZenStackClient(schema, {
dialect: ...,
computedFields: {
User: {
postCount: (eb) =>
eb.selectFrom('Post')
.whereRef('Post.authorId', '=', 'id')
.select(({ fn }) => fn.countAll<number>().as('count')),
},
},
});Query Builder ($qb)
Escape hatch to full Kysely when ORM API isn't enough:
const result = await db.$qb
.selectFrom('User')
.leftJoin('Post', 'Post.authorId', 'User.id')
.select(['User.id', 'User.email', 'Post.title'])
.execute();Mix into ORM filters with $expr:
await db.user.findMany({
where: {
$expr: (eb) =>
eb.selectFrom('Post')
.whereRef('Post.authorId', '=', 'User.id')
.select(({ fn }) => eb(fn.countAll(), '>=', 2).as('v'))
}
});Server Adapters
Next.js (App Router)
// app/api/model/[...path]/route.ts
import { NextRequestHandler } from '@zenstackhq/server/next';
import { RPCApiHandler } from '@zenstackhq/server/api';
import { schema } from '~/zenstack/schema';
const handler = NextRequestHandler({
apiHandler: new RPCApiHandler({ schema }),
getClient: (req) => authDb.$setAuth(getSessionUser(req)),
useAppDir: true,
});
export { handler as GET, handler as POST, handler as PUT, handler as PATCH, handler as DELETE };Express.js
import { ZenStackMiddleware } from '@zenstackhq/server/express';
import { RPCApiHandler } from '@zenstackhq/server/api';
app.use('/api/model', ZenStackMiddleware({
apiHandler: new RPCApiHandler({ schema }),
getClient: (req) => authDb.$setAuth(getUser(req)),
}));CLI Commands
| Command | Purpose |
zen generate | Compile ZModel → TypeScript |
zen db push | Push schema to DB (dev only) |
zen db pull | Introspect DB → ZModel |
zen migrate dev | Create + apply migration (dev) |
zen migrate deploy | Apply pending migrations (prod) |
zen migrate reset | Drop + reapply all (dev only) |
zen migrate status | Check migration status |
Plugins
Schema Plugins
plugin policy {
provider = '@zenstackhq/plugin-policy'
}
plugin prisma {
provider = '@core/prisma'
output = '../prisma/schema.prisma'
}Runtime Plugins
const enhanced = db.$use({
id: 'my-plugin',
onQuery: {
$allModels: {
async $allOperations({ args, proceed }) {
console.log('query intercepted');
return proceed(args);
},
},
},
});Hook types: Query API hooks, Entity mutation hooks, Kysely query hooks.
Reference Files
For detailed documentation, see:
references/schema-language.md— models, relations, enums, attributes, mixins, polymorphism, typed JSONreferences/access-control.md— policies, auth(), field-level policies, runtime behaviorreferences/orm-api.md— CRUD, filters, transactions, computed fields, query builderreferences/plugins-and-cli.md— plugin system, CLI commands, code generationreferences/server-adapters.md— Next.js, Express, REST API, client-side hooksreferences/migration.md— migrating from Prisma and from v2
Common Gotchas
- No Prisma at runtime — don't import from
@prisma/client - Install DB driver yourself — ZenStack doesn't bundle drivers
$use()and$setAuth()return new clients — they're immutable- Raw SQL bypasses access control —
$executeRaw,$queryRaw,sqltag - Cascade deletes/triggers bypass access control — DB-internal operations
selectandincludeare mutually exclusive — can't use bothpost-updatemust be explicit —alldoesn't include it- v3 generates to
zenstack/folder — not intonode_modules - Computed fields are DB-side — not client-side like Prisma extensions
- Only PostgreSQL, MySQL, SQLite — no MongoDB, CockroachDB, etc.
- Use multiple schema files — use a zmodel file per model/enum/type in a ./schema folder
- Zmodel files allow circular imports - don't worry about circular imports in zmodel
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

