0064-laravel-policies

Laravel policies secure resource actions by defining methods for listing, viewing, creating, updating, and deleting. You write policy methods that delegate to a Permission enum, returning booleans based on user capability and resource attributes.

Enforce user permissions by combining ability checks with resource ownership constraints. You can add attributes like customer_id to verify ownership and use a Permission enum to centralize authorization strings for clear access control.

Authorize custom operations by composing existing policy logic. You implement non-standard actions within your policy class by combining the defined permission enums and resource state constraints to return a boolean authorization result.

Yes, you can centralize permission strings using a Permission enum. By calling the user can method with the enum, your Laravel policies can consistently delegate authorization checks across multiple resource actions and custom operations.

Enforce business-state rules by adding state constraints to your Laravel policy methods. You write logic that checks the model state, ensuring only resources matching specific conditions, such as pending orders, can be deleted.

You need a YAML-frontmatter entry point in SKILL.md to implement Laravel authorization policies. This setup defines the policy structure, ensuring resource actions like viewing and updating are protected by ownership and state constraints.