zenstack
ZenStack access policies and enhanced Prisma ORM. Use when defining access control rules (@@allow/@@deny), integrating with tRPC, setting up auth(), or working with ZModel schemas.
What this skill does
# ZenStack Skill
ZenStack is a TypeScript toolkit that enhances Prisma ORM with flexible Authorization layer (RBAC/ABAC/PBAC/ReBAC) and auto-generated type-safe APIs.
## When to Use
- Defining access control policies in ZModel
- Setting up ZenStack with Prisma/tRPC/Next.js
- Implementing RBAC, ABAC, or multi-tenant authorization
- Generating tRPC routers from ZModel
- Adding field-level validation
## Quick Start
### Installation
```bash
npm install zenstack @zenstackhq/runtime
npx zenstack init
```
### Generate from ZModel
```bash
npx zenstack generate
```
## Access Policy Syntax
### Model-Level Policies
```zmodel
model Post {
id Int @id @default(autoincrement())
title String
published Boolean @default(false)
author User @relation(fields: [authorId], references: [id])
authorId Int
// Deny anonymous access
@@deny('all', auth() == null)
// Published posts readable by anyone
@@allow('read', published)
// Author has full access
@@allow('all', auth().id == authorId)
}
```
### Operations
| Operation | Description |
|-----------|-------------|
| `'all'` | All CRUD operations |
| `'create'` | Create only |
| `'read'` | Read only |
| `'update'` | Update only |
| `'delete'` | Delete only |
| `'create,read'` | Multiple operations |
### Policy Rules
- **@@deny takes precedence over @@allow**
- Policies are evaluated at runtime
- `auth()` returns current user or null
### RBAC Example
```zmodel
model Post {
id Int @id @default(autoincrement())
title String
// Only admins have full access
@@allow('all', auth().role == 'ADMIN')
// Users can read
@@allow('read', auth().role == 'USER')
}
```
### ABAC Example
```zmodel
model Resource {
id Int @id @default(autoincrement())
name String
published Boolean @default(false)
owner User @relation(fields: [ownerId], references: [id])
ownerId Int
// Reputation-based creation
@@allow('create', auth().reputation >= 100)
// Published resources are public
@@allow('read', published)
// Owner has full access
@@allow('read,update,delete', owner == auth())
}
```
### Multi-Tenant Example
```zmodel
model Organization {
id Int @id @default(autoincrement())
name String
members User[]
posts Post[]
}
model Post {
id Int @id @default(autoincrement())
title String
org Organization @relation(fields: [orgId], references: [id])
orgId Int
// Only org members can access
@@allow('all', org.members?[id == auth().id])
}
```
## Field-Level Policies
```zmodel
model User {
id Int @id
email String @allow('read', auth().id == id)
password String @deny('read', true) // Never readable
salary Int @allow('read', auth().role == 'HR')
}
```
### Field-Level Attributes
- `@allow('read', condition)` — Allow field read
- `@allow('update', condition)` — Allow field update
- `@deny('read', condition)` — Deny field read
- `@deny('update', condition)` — Deny field update
## Data Validation
```zmodel
model User {
id String @id @default(cuid())
name String @length(min: 3, max: 20)
email String @email
age Int? @gte(18)
password String @length(min: 8, max: 32)
url String @url
}
```
### Validation Attributes
| Attribute | Description |
|-----------|-------------|
| `@email` | Valid email format |
| `@url` | Valid URL format |
| `@length(min, max)` | String length |
| `@gt(n)` / `@gte(n)` | Greater than (or equal) |
| `@lt(n)` / `@lte(n)` | Less than (or equal) |
| `@regex(pattern)` | Regex match |
| `@startsWith(str)` | String prefix |
| `@endsWith(str)` | String suffix |
## tRPC Integration
### Plugin Configuration
```zmodel
plugin trpc {
provider = '@zenstackhq/trpc'
output = 'src/server/routers/generated'
}
```
### Context Setup
```typescript
import { enhance } from '@zenstackhq/runtime';
import { prisma } from './db';
import { getSession } from './auth';
export const createContext = async ({ req, res }) => {
const session = await getSession(req, res);
return {
session,
// Enhanced Prisma client with access policies
prisma: enhance(prisma, { user: session?.user }),
};
};
```
### Using Generated Routers
```typescript
import { createTRPCRouter } from './trpc';
import { createRouter } from './routers/generated/routers';
export const appRouter = createTRPCRouter({
...createRouter(createTRPCRouter, procedure),
});
```
## Enhanced Prisma Client
```typescript
import { PrismaClient } from '@prisma/client';
import { enhance } from '@zenstackhq/runtime';
const prisma = new PrismaClient();
// Create enhanced client with user context
const db = enhance(prisma, { user: currentUser });
// All queries now respect access policies
const posts = await db.post.findMany(); // Only returns allowed posts
```
## Common Patterns
### Soft Delete with Policy
```zmodel
model Post {
id Int @id
deleted Boolean @default(false)
deletedAt DateTime?
// Hide soft-deleted posts
@@deny('read', deleted)
// Allow owner to "delete" (soft delete)
@@allow('update', auth().id == authorId && future().deleted)
}
```
### Time-Based Access
```zmodel
model Content {
id Int @id
publishedAt DateTime?
// Only show published content
@@allow('read', publishedAt != null && publishedAt <= now())
}
```
### Hierarchical Access
```zmodel
model Document {
id Int @id
parent Document? @relation("children", fields: [parentId], references: [id])
parentId Int?
children Document[] @relation("children")
// Access if user can access parent
@@allow('read', parent == null || parent.canRead(auth()))
}
```
## CLI Commands
```bash
# Initialize ZenStack in project
npx zenstack init
# Generate Prisma schema and artifacts
npx zenstack generate
# Format ZModel file
npx zenstack format
```
## Examples
### Example: Add RBAC to Existing Model
**Input:**
```
Add role-based access control to my Post model
```
**Output:**
```zmodel
model Post {
id Int @id @default(autoincrement())
title String
published Boolean @default(false)
author User @relation(fields: [authorId], references: [id])
authorId Int
// Deny anonymous access
@@deny('all', auth() == null)
// Admins have full access
@@allow('all', auth().role == 'ADMIN')
// Authors can manage their own posts
@@allow('all', auth().id == authorId)
// Anyone can read published posts
@@allow('read', published)
}
```
### Example: Multi-tenant Data Isolation
**Input:**
```
Isolate data by organization in a SaaS app
```
**Output:**
```zmodel
model Organization {
id Int @id
members User[]
posts Post[]
}
model Post {
id Int @id
org Organization @relation(fields: [orgId], references: [id])
orgId Int
// Only org members can access posts
@@allow('all', org.members?[id == auth().id])
}
```
### Example: Soft Delete Pattern
**Input:**
```
Implement soft delete that hides deleted records automatically
```
**Output:**
```zmodel
model Post {
id Int @id
deleted Boolean @default(false)
deletedAt DateTime?
authorId Int
// Hide soft-deleted from normal queries
@@deny('read', deleted)
// Allow "delete" = set deleted flag
@@allow('update', auth().id == authorId && future().deleted)
}
```
### Example: v3 Migration Script
**Input:**
```
Update my package.json for ZenStack v3
```
**Output:**
```json
{
"scripts": {
"generate": "zen generate",
"db:push": "zen db push",
"migrate:dev": "zen migrate dev",
"migrate:deploy": "zen migrate deploy"
}
}
```
## Tips
### Tip 1: Deny by Default Pattern
Start strict, then open up:
```zmodel
model Secret {
id Int @id
value String
// Start with deny all
@@deny('all', true)
// Then wRelated in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.