skills.rest
AHMADJAN-New
AHMADJAN-NewCOMMUNITY
Explore all skills by this author →
GitHub

nazim-permissions

Manage Spatie permission patterns with `{resource}.{action}` naming and access checks.

Updated Nov 15, 2025
Search Tags:#authorization#frontend#backend#access control#permissions#spatie
One-click install
npx skills add https://github.com/AHMADJAN-New/nazim-web --skill nazim-permissions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nazim-permissions
Source: https://github.com/AHMADJAN-New/nazim-web/tree/main/.cursor/skills/nazim-permissions
Command: npx skills add https://github.com/AHMADJAN-New/nazim-web --skill nazim-permissions

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the management of permissions within the Nazim application, ensuring consistent and secure access control for users and features.

Core Features & Use Cases

  • Permission Naming Convention: Enforces a clear {resource}.{action} format for all permissions.
  • Frontend Visibility: Manages menu and feature visibility using useHasPermission hook, avoiding role-based fallbacks.
  • Backend Checks: Facilitates secure permission checks on the server-side using Spatie's hasPermissionTo method.
  • Use Case: When developing a new feature, use this Skill to ensure all associated permissions are correctly defined and applied for both frontend display and backend authorization.

Quick Start

Use the nazim-permissions skill to ensure all new permissions follow the resource.action format.

Frequently Asked Questions about nazim-permissions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage Spatie permissions for frontend and backend access control?▼

Manage Spatie permissions by using the useHasPermission hook for frontend visibility and the hasPermissionTo method for backend authorization checks. This approach ensures role-agnostic access control across your application.

What naming convention should I use for defining Spatie permissions?▼

Spatie permissions should use a strict resource.action naming convention. Defining permissions in this format ensures consistent access control mapping for both frontend display rules and backend authorization checks.

How do I control frontend menu visibility based on user permissions?▼

Control frontend menu visibility by implementing the useHasPermission hook to check user permissions directly. This method avoids role-based fallbacks and ensures features are only displayed if the user has the required access level.

Why should I avoid role-based checks for frontend feature visibility?▼

Avoiding role-based checks for frontend feature visibility ensures role-agnostic access control. Using the useHasPermission hook directly verifies if a user possesses the required permission, making your application's access control logic more secure and maintainable.

How do I perform backend authorization checks with Spatie permissions?▼

Perform backend authorization checks by utilizing Spatie's hasPermissionTo method on the server-side. This validates that a user possesses the required resource.action permission before granting access to specific backend features or data.

Related Skills

Explore More Software Engineering Skills→
PTKDrakePTKDrake
1

laravel-permission-development

Manage roles, permissions, and policy-based access control in Laravel.

Community
Advanced
juanjaragavijuanjaragavi

authentication

Manage authentication and authorization with Better Auth 1.x and Google OAuth.

Community
Advanced
kaxuna1kaxuna1

react

Blueprint React 18+ TypeScript components with React Query, Context, and Hook Form.

Community
Intermediate
SaidabbosSaidabbos

permission-system

Automate role-based access control in Laravel with Spatie Laravel Permission.

Community
Intermediate