> For the complete documentation index, see [llms.txt](https://docs.opensoutheners.com/oss/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opensoutheners.com/oss/extended-laravel/readme.md).

# Getting started

## Why this package?

Laravel and PHP has some lacks, which is fine (they are not designed to be perfect fit for every possible case). Therefore this package serve to fill that gap.

The package is just a bunch of functions that we most often reuse in plenty of our own open source packages as well as our work.

## Key features

* All make commands available through the framework opens the generated file (`APP_IDE` environment variable must be configured).
* Helpers functions from our other package [**extended-php**](https://github.com/open-southeners/extended-php) are [available through this one](/oss/extended-laravel/function-helpers.md) in multiple ways.
* Custom Eloquent attributes casts and validation rules
* Added useful commands like `horizon:flush`, `make:builder`, `queue:batches`, `cache:clearLocks`, `vendor:check`

## Installation

Grab this package using composer:

```bash
composer require open-southeners/laravel-helpers
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.opensoutheners.com/oss/extended-laravel/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.