policies

Centralize Laravel Eloquent model authorization using policy classes.

3|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/codebar-ag/coding-guidelines --skill policies
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: policies
Source: https://github.com/codebar-ag/coding-guidelines/tree/main/resources/boost/skills/policies
Command: npx skills add https://github.com/codebar-ag/coding-guidelines --skill policies

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes all authorization logic for a given Eloquent model, preventing duplicated checks and ensuring consistent access control across controllers and requests.

Core Features & Use Cases

  • Centralizes authorization logic per model in a single policy class
  • Enforces standard methods for each ability (viewAny, view, create, update, delete, etc.)
  • Automatically discovers and registers policies in Laravel's AuthServiceProvider

Quick Start

Define a policy for each model, register it in AuthServiceProvider, and start enforcing it in controllers and form requests.

Frequently Asked Questions about policies

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

FAQPage Schema
How do I centralize authorization logic for Laravel Eloquent models?

Centralize Laravel authorization by defining policy classes for each Eloquent model, enforcing consistent access control across controllers and requests without duplicating checks.

What is the best way to organize per-model access control in Laravel controllers?

Organize per-model access control by creating dedicated policy classes that define standard abilities like view, create, update, and delete, keeping your Laravel controllers clean.

How do I register and discover policies in Laravel's AuthServiceProvider?

Register policies in Laravel's AuthServiceProvider to map Eloquent models to their policy classes, enabling automatic policy discovery and consistent authorization enforcement.

What standard methods do I need to define in a Laravel policy class?

Define standard methods like viewAny, view, create, update, and delete in a Laravel policy class to enforce specific Eloquent model access control abilities.

When should I use Laravel policies instead of inline authorization checks?

Use Laravel policies when you need to centralize authorization logic for an Eloquent model, preventing duplicated checks and ensuring consistent access control across controllers and requests.

Can I enforce Laravel policies inside form requests and controllers?

Yes, Laravel policies enforce per-model access control across controllers and form requests, ensuring consistent authorization checks for abilities like create and update.