Non-negotiable rules:

1. Load references/stack.md first, then only the task-relevant references.
2. Inspect composer.json and composer.lock before applying version-specific APIs. Recommend Laravel 13 for new applications and explicit upgrades; never silently upgrade an existing application during unrelated work.
3. No business logic in controllers. Controllers validate (Form Request), delegate (Action), return (API Resource). Nothing else.
4. No returning Eloquent models directly. Every response goes through an API Resource.
5. No inline validation. All validation lives in Form Request classes.
6. No $guarded = []. Every model uses explicit $fillable.
7. No raw queries. Use Eloquent or query builder with parameter bindings.
8. No bare queue:work. All queue processing uses Horizon.
9. Model::shouldBeStrict() must be enabled in AppServiceProvider::boot(). </EXTREMELY-IMPORTANT>

laravel

Inputs

• $request: The Laravel task, bug, feature, or subsystem being worked on

Goal

Route Laravel work through the correct project conventions so the implementation follows the existing backend architecture instead of generic framework defaults.

Step 0: Read the stack contract

Always start with:

• references/stack.md

That establishes the locked runtime, package, and architecture choices for this Laravel surface.

For a new application, a framework-version decision, or a Laravel 12 to 13 upgrade, also read:

• references/upgrading.md

Success criteria: The project's Laravel stack choices are explicit before implementation starts.

Step 1: Load only the relevant references

Use the routing table to pick reference files that match the actual task. Do not bulk-load the full reference tree.

Multiple tasks? Read multiple files. The references are self-contained.

Success criteria: Only the task-relevant Laravel conventions are in play.

Step 2: Implement with the core Laravel guardrails

Keep these rules active:

• controllers validate, delegate, and return
• responses go through API Resources
• list endpoints paginate
• models use explicit $fillable
• mutations use the correct Action or transaction pattern
• queues use the project's queue and Horizon conventions

Success criteria: The change matches the project’s Laravel architecture instead of framework-default shortcuts.

Step 3: Verify with the narrowest relevant checks

Use the smallest verification loop that matches the task:

• PHPUnit or Pest tests
• focused artisan or framework checks
• static analysis or linting if already part of the repo workflow
• for framework upgrades, the dependency and regression checks in references/upgrading.md

Success criteria: The change is validated in the way this Laravel project expects.

Guardrails

• Do not inline the whole Laravel handbook in SKILL.md.
• Do not skip references/stack.md.
• Do not return raw Eloquent models directly.
• Do not put business logic in controllers.
• Do not apply Laravel 13-only APIs to a Laravel 12 project unless the task includes the upgrade.
• Do not pin today's Laravel patch release; use the supported ^13.0 constraint and the lockfile.
• Do not add disable-model-invocation; this is a normal domain skill.

When To Load References

• references/stack.md Always.

• then only the task-relevant files under references/

Output Contract

Report:

1. the detected Laravel major and whether Laravel 13 was recommended or already in use
2. which Laravel references were loaded
3. the architecture pattern chosen
4. the change made
5. the verification run