PHPackages                             maarheeze/boost-guidelines - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility & Helpers](/categories/utility)
4. /
5. maarheeze/boost-guidelines

ActiveLibrary[Utility & Helpers](/categories/utility)

maarheeze/boost-guidelines
==========================

laravel boost integration for .ai guidelines

1.3.0(3mo ago)3409MITPHPPHP >=8.1

Since Apr 17Pushed 2mo agoCompare

[ Source](https://github.com/maarheeze/boost-guidelines)[ Packagist](https://packagist.org/packages/maarheeze/boost-guidelines)[ RSS](/packages/maarheeze-boost-guidelines/feed)WikiDiscussions main Synced 3w ago

READMEChangelog (6)Dependencies (5)Versions (7)Used By (0)

Boost Guidelines
================

[](#boost-guidelines)

Laravel Boost loads AI context from your application's own files. But when you install a Composer package, any guidelines that package ships for AI agents don't appear automatically — you'd have to copy them by hand.

This plugin solves that. It scans all installed vendor packages for guideline files and merges them into your Boost context automatically.

Why `.ai/guidelines/`
---------------------

[](#why-aiguidelines)

Laravel Boost's built-in path for third-party guidelines is `resources/boost/guidelines/` — a Boost-specific convention. This plugin adds support for `.ai/guidelines/`, a tool-agnostic path that many AI tools (Claude Code, Cursor, and others) already understand.

By using `.ai/guidelines/`, package authors write their AI guidelines once in a neutral location — and those guidelines work across all supporting tools, not just Boost.

For Application Developers
--------------------------

[](#for-application-developers)

Install once:

```
composer require maarheeze/boost-guidelines --dev
php artisan boost:install
php artisan boost:update --discover
```

Any installed package that ships `.ai/guidelines/*.md` files will now be discovered automatically and merged into your Boost context. No further configuration required.

For Package Authors
-------------------

[](#for-package-authors)

Add a `.ai/guidelines/` directory at the root of your package:

```
your-package/
└── .ai/guidelines/
    ├── general.md
    └── usage.md

```

Write plain Markdown — describe conventions, gotchas, required patterns, or anything an AI agent should know when working with your package. Any application with this plugin installed will pick these up automatically.

For Teams: Shared Guidelines Repository
---------------------------------------

[](#for-teams-shared-guidelines-repository)

You can create a Composer package that contains nothing but guideline files, and require it as a dev dependency in every project that should inherit those guidelines:

```
your-org/guidelines/
└── .ai/guidelines/
    ├── php.md
    ├── architecture.md
    └── git.md

```

```
composer require your-org/guidelines --dev
```

This is the cleanest way to share organisation-wide conventions, team standards, or cross-project context — version-controlled and distributed through Composer like any other dependency.

How It Works
------------

[](#how-it-works)

1. Packages provide Markdown guideline files in a well-known path (`.ai/guidelines/*.md`)
2. This plugin scans all installed vendor packages for matching files
3. The discovered guidelines are grouped by package and rendered into your Boost context
4. Your AI agent (Claude Code, Cursor, etc.) reads them automatically via Boost

Installation
------------

[](#installation)

```
composer require maarheeze/boost-guidelines --dev
php artisan boost:install
php artisan boost:update --discover
```

To publish the configuration file:

```
php artisan vendor:publish --tag=boost-guidelines-config
```

Configuration
-------------

[](#configuration)

After publishing, edit `config/boost-guidelines.php`:

```
return [

    'paths' => [
        '.ai/guidelines',
        'resources/boost',
    ],

    'only' => [
        // 'maarheeze/guidelines',
    ],

    'except' => [
        // 'some-vendor/some-package',
    ],

];
```

### `paths`

[](#paths)

A list of sub-paths within each vendor package to scan for Markdown guideline files. All `*.md` files found inside a matching directory are included.

You can add multiple paths to support packages that use different conventions:

```
'paths' => [
    '.ai/guidelines',
    'resources/boost',
],
```

### `only`

[](#only)

An allowlist of packages. When non-empty, only guidelines from the listed packages are loaded. All others are ignored. Use the full `vendor/package` name.

```
'only' => [
    'maarheeze/guidelines',
    'acme/laravel-helpers',
],
```

### `except`

[](#except)

A blocklist of packages. Guidelines from listed packages are always excluded, even if they match a configured path. Applied after `only`.

```
'except' => [
    'some-vendor/noisy-package',
],
```

Example
-------

[](#example)

Given these installed packages:

```
vendor/
├── maarheeze/guidelines/
│   └── .ai/guidelines/
│       └── php.md
└── acme/helpers/
    └── .ai/guidelines/
        └── laravel.md

```

Both `php.md` and `laravel.md` are discovered and merged into your Boost context, grouped under their respective package name.

###  Health Score

42

—

FairBetter than 88% of packages

Maintenance85

Actively maintained with recent releases

Popularity20

Limited adoption so far

Community6

Small or concentrated contributor base

Maturity47

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~1 days

Total

6

Last Release

94d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/734972e64c460b2142b0b04b4f40aa30077c5dd1915411b486ec72efcae3c3bf?d=identicon)[wietsewarendorff](/maintainers/wietsewarendorff)

---

Top Contributors

[![wietsewarendorff](https://avatars.githubusercontent.com/u/313525?v=4)](https://github.com/wietsewarendorff "wietsewarendorff (12 commits)")

###  Code Quality

TestsPHPUnit

Static AnalysisPHPStan

Type Coverage Yes

### Embed Badge

![Health badge](/badges/maarheeze-boost-guidelines/health.svg)

```
[![Health](https://phpackages.com/badges/maarheeze-boost-guidelines/health.svg)](https://phpackages.com/packages/maarheeze-boost-guidelines)
```

###  Alternatives

[psalm/plugin-laravel

Psalm plugin for Laravel

3345.3M347](/packages/psalm-plugin-laravel)[aedart/athenaeum

Athenaeum is a mono repository; a collection of various PHP packages

255.2k](/packages/aedart-athenaeum)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)