鱼皮AI导航
鱼皮AI导航
  • 主页
  • 社区
  • AI工具
  • AI知识库
  • AI提示词
  • MCP
  • Skills
  • AI学习资源
  • AI资讯
  • GitHub开源
登录/注册

epic-permissions

提供基于角色的细粒度访问控制能力,支持按动作、实体和访问范围三元组定义权限,实现服务端强制校验与客户端条件渲染的统一权限管理,适用于多角色协作系统中的路由保护、操作限制及界面动态展示。

测试与安全
访问 GitHub
文档Skills.MD
name
epic-permissions
description
Guide on RBAC system and permissions for Epic Stack
categories["permissions","rbac","access-control"]

Epic Stack: Permissions

When to use this skill

Use this skill when you need to:

  • Implement role-based access control (RBAC)
  • Validate permissions on server-side or client-side
  • Create new permissions or roles
  • Restrict access to routes or actions
  • Implement granular permissions (own vs any)

Patterns and conventions

Permissions Philosophy

Following Epic Web principles:

Explicit is better than implicit - Always explicitly check permissions. Don't assume a user has access based on implicit rules or hidden logic. Every permission check should be visible and clear in the code.

Example - Explicit permission checks:

▼
typescript
复制代码
// ✅ Good - Explicit permission check export async function action({ request }: Route.ActionArgs) { const userId = await requireUserId(request) // Explicitly check permission - clear and visible await requireUserWithPermission(request, 'delete:note:own') // Permission check is explicit and obvious await prisma.note.delete({ where: { id: noteId } }) } // ❌ Avoid - Implicit permission check export async function action({ request }: Route.ActionArgs) { const userId = await requireUserId(request) const note = await prisma.note.findUnique({ where: { id: noteId } }) // Implicit check - not clear what permission is being checked if (note.ownerId !== userId) { throw new Response('Forbidden', { status: 403 }) } // What permission does this represent? Not explicit }

Example - Explicit permission strings:

▼
typescript
复制代码
// ✅ Good - Explicit permission string const permission: PermissionString = 'delete:note:own' // Clear: action (delete), entity (note), access (own) await requireUserWithPermission(request, permission) // ❌ Avoid - Implicit or unclear permissions const canDelete = checkUserCanDelete(user, note) // What permission is this checking? Not explicit

RBAC Model

Epic Stack uses an RBAC (Role-Based Access Control) model where:

  • Users have Roles
  • Roles have Permissions
  • A user's permissions are the union of all permissions from their roles

Permission Structure

Permissions follow the format: action:entity:access

Components:

  • action: The allowed action (create, read, update, delete)
  • entity: The entity being acted upon (user, note, etc.)
  • access: The access level (own, any, own,any)

Examples:

  • create:note:own - Can create own notes
  • read:note:any - Can read any note
  • delete:user:any - Can delete any user (admin)
  • update:note:own - Can update only own notes

Prisma Schema

Models:

▼
prisma
复制代码
model Permission { id String @id @default(cuid()) action String // e.g. create, read, update, delete entity String // e.g. note, user, etc. access String // e.g. own or any description String @default("") roles Role[] @@unique([action, entity, access]) } model Role { id String @id @default(cuid()) name String @unique description String @default("") users User[] permissions Permission[] } model User { id String @id @default(cuid()) // ... roles Role[] }

Validate Permissions Server-Side

Require specific permission:

▼
typescript
复制代码
import { requireUserWithPermission } from '#app/utils/permissions.server.ts' export async function action({ request }: Route.ActionArgs) { const userId = await requireUserWithPermission( request, 'delete:note:own', // Throws 403 error if doesn't have permission ) // User has the permission, continue... }

Require specific role:

▼
typescript
复制代码
import { requireUserWithRole } from '#app/utils/permissions.server.ts' export async function loader({ request }: Route.LoaderArgs) { const userId = await requireUserWithRole(request, 'admin') // User has admin role, continue... }

Conditional permissions (own vs any) - explicit:

▼
typescript
复制代码
export async function action({ request }: Route.ActionArgs) { const userId = await requireUserId(request) // Explicitly determine ownership const note = await prisma.note.findUnique({ where: { id: noteId }, select: { ownerId: true }, }) const isOwner = note.ownerId === userId // Explicitly check the appropriate permission based on ownership await requireUserWithPermission( request, isOwner ? 'delete:note:own' : 'delete:note:any', // Explicit permission string ) // Permission check is explicit and clear // Proceed with deletion... }

Validate Permissions Client-Side

Check if user has permission:

▼
typescript
复制代码
import { userHasPermission, useOptionalUser } from '#app/utils/user.ts' export default function NoteRoute({ loaderData }: Route.ComponentProps) { const user = useOptionalUser() const isOwner = user?.id === loaderData.note.ownerId const canDelete = userHasPermission( user, isOwner ? 'delete:note:own' : 'delete:note:any', ) return ( <div> {canDelete && ( <button onClick={handleDelete}>Delete</button> )} </div> ) }

Check if user has role:

▼
typescript
复制代码
import { userHasRole } from '#app/utils/user.ts' export default function AdminRoute() { const user = useOptionalUser() const isAdmin = userHasRole(user, 'admin') if (!isAdmin) { return <div>Access Denied</div> } return <div>Admin Panel</div> }

Create New Permissions

En Prisma Studio o seed:

▼
typescript
复制代码
// prisma/seed.ts await prisma.permission.create({ data: { action: 'create', entity: 'post', access: 'own', description: 'Can create their own posts', roles: { connect: { name: 'user' }, }, }, })

Permiso con múltiples niveles de acceso:

▼
typescript
复制代码
await prisma.permission.createMany({ data: [ { action: 'read', entity: 'post', access: 'own', description: 'Can read own posts', }, { action: 'read', entity: 'post', access: 'any', description: 'Can read any post', }, ], })

Assign Roles to Users

When creating user:

▼
typescript
复制代码
const user = await prisma.user.create({ data: { email, username, roles: { connect: { name: 'user' }, // Assign 'user' role }, }, })

Assign multiple roles:

▼
typescript
复制代码
await prisma.user.update({ where: { id: userId }, data: { roles: { connect: [ { name: 'user' }, { name: 'moderator' }, ], }, }, })

Permissions and Roles Seed

Seed example:

▼
typescript
复制代码
// prisma/seed.ts // Create permissions const permissions = await Promise.all([ // User permissions prisma.permission.create({ data: { action: 'create', entity: 'note', access: 'own', description: 'Can create own notes', }, }), prisma.permission.create({ data: { action: 'read', entity: 'note', access: 'own', description: 'Can read own notes', }, }), prisma.permission.create({ data: { action: 'update', entity: 'note', access: 'own', description: 'Can update own notes', }, }), prisma.permission.create({ data: { action: 'delete', entity: 'note', access: 'own', description: 'Can delete own notes', }, }), // Admin permissions prisma.permission.create({ data: { action: 'delete', entity: 'user', access: 'any', description: 'Can delete any user', }, }), ]) // Create roles const userRole = await prisma.role.create({ data: { name: 'user', description: 'Standard user', permissions: { connect: permissions.slice(0, 4).map(p => ({ id: p.id })), }, }, }) const adminRole = await prisma.role.create({ data: { name: 'admin', description: 'Administrator', permissions: { connect: permissions.map(p => ({ id: p.id })), }, }, })

Permission Type

Type-safe permission strings:

▼
typescript
复制代码
import { type PermissionString } from '#app/utils/user.ts' // Tipo: 'create:note:own' | 'read:note:own' | etc. const permission: PermissionString = 'delete:note:own'

Parsear permission string:

▼
typescript
复制代码
import { parsePermissionString } from '#app/utils/user.ts' const { action, entity, access } = parsePermissionString('delete:note:own') // action: 'delete' // entity: 'note' // access: ['own']

Common examples

Example 1: Proteger action con permiso

▼
typescript
复制代码
// app/routes/users/$username/notes/$noteId.tsx export async function action({ request }: Route.ActionArgs) { const userId = await requireUserId(request) const formData = await request.formData() const { noteId } = Object.fromEntries(formData) const note = await prisma.note.findFirst({ select: { id: true, ownerId: true, owner: { select: { username: true } } }, where: { id: noteId }, }) if (!note) { throw new Response('Not found', { status: 404 }) } const isOwner = note.ownerId === userId // Validate permiso según si es propietario o no await requireUserWithPermission( request, isOwner ? 'delete:note:own' : 'delete:note:any', ) await prisma.note.delete({ where: { id: note.id } }) return redirect(`/users/${note.owner.username}/notes`) }

Example 2: Mostrar UI condicional basada en permisos

▼
typescript
复制代码
export default function NoteRoute({ loaderData }: Route.ComponentProps) { const user = useOptionalUser() const isOwner = user?.id === loaderData.note.ownerId const canDelete = userHasPermission( user, isOwner ? 'delete:note:own' : 'delete:note:any', ) const canEdit = userHasPermission( user, isOwner ? 'update:note:own' : 'update:note:any', ) return ( <div> <h1>{loaderData.note.title}</h1> <p>{loaderData.note.content}</p> {(canEdit || canDelete) && ( <div className="flex gap-2"> {canEdit && ( <Link to="edit"> <Button>Edit</Button> </Link> )} {canDelete && ( <DeleteNoteButton noteId={loaderData.note.id} /> )} </div> )} </div> ) }

Example 3: Ruta solo para admin

▼
typescript
复制代码
// app/routes/admin/users.tsx export async function loader({ request }: Route.LoaderArgs) { await requireUserWithRole(request, 'admin') const users = await prisma.user.findMany({ select: { id: true, email: true, username: true, }, }) return { users } } export default function AdminUsersRoute({ loaderData }: Route.ComponentProps) { return ( <div> <h1>All Users</h1> {loaderData.users.map(user => ( <div key={user.id}>{user.username}</div> ))} </div> ) }

Example 4: Create new permission and assign it

▼
typescript
复制代码
// Migración o seed async function setupPostPermissions() { // Create post permissions const createOwn = await prisma.permission.create({ data: { action: 'create', entity: 'post', access: 'own', description: 'Can create own posts', }, }) const readAny = await prisma.permission.create({ data: { action: 'read', entity: 'post', access: 'any', description: 'Can read any post', }, }) // Assign to user role await prisma.role.update({ where: { name: 'user' }, data: { permissions: { connect: [ { id: createOwn.id }, { id: readAny.id }, ], }, }, }) }

Common mistakes to avoid

  • ❌ Implicit permission checks: Always explicitly check permissions - make permission requirements visible in code
  • ❌ Not validating permissions on server-side: Always validate permissions in action/loader, never trust client-side only
  • ❌ Forgetting to verify own vs any: Explicitly determine if user is owner before validating permission
  • ❌ Not using correct helpers: Use requireUserWithPermission for server-side and userHasPermission for client-side - explicit helpers
  • ❌ Not creating unique permissions: Use @@unique([action, entity, access]) in schema - explicit permission structure
  • ❌ Assuming permissions instead of verifying: Always verify explicitly, even if you think user has the permission
  • ❌ Not handling 403 errors: Helpers throw errors that must be handled by ErrorBoundary
  • ❌ Not using types: Use PermissionString type for type-safety - explicit types
  • ❌ Hidden permission logic: Don't hide permission checks in utility functions - make them explicit at the call site

References

  • Epic Stack Permissions Docs
  • Epic Web Principles
  • RBAC Explained
  • app/utils/permissions.server.ts - Server-side permission utilities
  • app/utils/user.ts - Client-side permission utilities
  • prisma/schema.prisma - Permission and Role models
  • prisma/seed.ts - Permission seed examples
测试与安全

快捷安装

复制到终端去安装 Skill

npxskillsaddepicweb-dev/epic-stack--skill"epic-permissions"
站长:程序员鱼皮 老鱼简历 商务合作 增值电信业务经营许可证
2026 鱼皮AI导航 | 沪ICP备19026706号-6
站长:程序员鱼皮 老鱼简历 商务合作 增值电信业务经营许可证
2026 鱼皮AI导航 | 沪ICP备19026706号-6
🔥热门工具
朱雀AI检测朱雀AI检测
朱雀AI检测助手朱雀AI检测助手
LovartLovart
老鱼简历老鱼简历
WritePass官网WritePass官网
面多多面多多
CursorCursor
星月写作星月写作
朱雀AI检测助手朱雀AI检测助手
零感AI零感AI
Skills 推荐
debug
debug 是一个系统化定位软件缺陷根因的技能,适用于用户报告 'fix'、'broken'、'error' 等问题或测试意外失败时。它通过可验证的假设、最小复现、因果链分析和回归测试,确保在修复前准确定位根本原因。
webapp-testing
提供本地 Web 应用的端到端测试能力,支持页面导航、元素交互、表单填写、动态等待、断言验证、截图捕获、浏览器日志收集及网络请求拦截,适用于前端功能验证与 UI 行为调试。
tdd-process
严格遵循测试驱动开发的红绿重构循环,强制执行先写测试、失败要有意义、实现最小化、验证全覆盖的全流程,确保每次代码变更都由可执行的测试用例驱动并经编译、检查与全量验证确认。
smoke-test
自动化创建 Mastra 项目并完成 Studio 全流程冒烟测试,涵盖项目初始化、环境配置、本地服务启动及 Chrome 浏览器中对 Agents、Tools、Workflows、Scorers 等核心模块的功能验证与截图记录。
property-based-testing
通过生成随机输入验证代码在各类边界条件下的行为一致性,适用于序列化、解析、归一化及纯函数等场景,能有效发现隐含缺陷并提升测试覆盖率,尤其适合需要高可靠性的算法与智能合约验证。