Generates comprehensive role-based permission matrices in markdown or SQL format for pages, components, and data access patterns. This skill should be used when designing authorization systems, documenting permissions, creating RBAC tables, or planning access control. Use for RBAC, role permissions, access control, authorization matrix, permission mapping, or security policies.
View on GitHubhopeoverture/worldbuilding-app-skills
role-permission-table-builder
plugins/role-permission-table-builder/skills/role-permission-table-builder/SKILL.md
January 21, 2026
Select agents to install to:
npx add-skill https://github.com/hopeoverture/worldbuilding-app-skills/blob/main/plugins/role-permission-table-builder/skills/role-permission-table-builder/SKILL.md -a claude-code --skill role-permission-table-builderInstallation paths:
.claude/skills/role-permission-table-builder/# Role Permission Table Builder Generate and maintain comprehensive role-based access control (RBAC) permission matrices for worldbuilding applications. ## Overview To build role permission systems: 1. Define user roles and hierarchies 2. Identify protected resources (pages, components, data, actions) 3. Create permission matrices mapping roles to resources 4. Generate implementation code for middleware and components 5. Document permission policies for team reference ## Role Definitions ### Standard Roles Define common application roles: - **Guest**: Unauthenticated users (read-only public content) - **User**: Basic authenticated users (read own data, limited writes) - **Creator**: Content creators (create/edit entities, manage own content) - **Editor**: Content editors (edit any content, moderate submissions) - **Admin**: System administrators (full access, user management) - **Super Admin**: Platform owners (all permissions, system configuration) ### Custom Roles To define worldbuilding-specific roles: - **World Owner**: Creator of worldbuilding project - **Collaborator**: Invited contributor to world - **Viewer**: Read-only access to private world - **Game Master**: Special permissions for RPG campaigns - **Publisher**: Can publish worlds publicly Consult `references/role-hierarchy.md` for role inheritance patterns. ## Permission Matrix ### Page-Level Permissions To define page access: | Page Route | Guest | User | Creator | Editor | Admin | | --------------------- | ----- | ---- | ------- | ------ | ----- | | / | [OK] | [OK] | [OK] | [OK] | [OK] | | /login | [OK] | [OK] | [OK] | [OK] | [OK] | | /dashboard | [ERROR] | [OK] | [OK] | [OK] | [OK] | | /worlds/create | [ERROR] | [OK] | [OK] | [OK] | [OK] | | /worlds/[id] | ๐ | ๐ | [OK] | [OK] | [OK] | | /worlds/[id]/edi