The guide
Section 01
Laravel Boost ships AI guidelines and agent skills for the Laravel ecosystem — short, composable instruction files that give coding agents like Claude Code, Cursor, and Codex working context about a package before they touch its code. Boost bundles guidelines for the framework itself and for popular packages, but it also reads guidelines straight out of any third-party package's vendor/ directory.
That means if you maintain a package, you can ship your own guidelines and skills inside it. When someone installs your package and runs boost:install, your guidelines load alongside Laravel's built-in ones — no action required on their end beyond having Boost installed.
This guide covers how to add that to a package you maintain, and how to add a badge to your README once you have.
Where Boost looks in your package
Boost discovers two kinds of resources from packages, each in its own conventional path:
resources/
boost/
guidelines/
core.blade.php
skills/
my-feature/
SKILL.md
Both are optional and independent — you can ship guidelines without skills, or skills without guidelines.
Adding guidelines
Add a resources/boost/guidelines/core.blade.php file to your package. Boost only reads this single file per package, so anything you want an agent to know upfront belongs here.
A guideline should give a short overview of what the package does, any required file structure or conventions, and how to use its main features — ideally with runnable examples. Boost guidelines support a <code-snippet> Blade component wrapped in @verbatim/@endverbatim so the example code isn't parsed as Blade itself:
## My Package
This package provides [brief description of functionality].
### Features
- Feature 1: a short, clear description.
- Feature 2: a short, clear description. Example usage:
@verbatim
<code-snippet name="How to use Feature 2" lang="php">
$result = MyPackage::featureTwo($param1, $param2);
</code-snippet>
@endverbatim
Keep it concise and actionable. This file is loaded upfront for every agent session in a consuming project, so it competes for the same context budget as everything else Boost loads — write what an agent genuinely needs to generate correct code against your package, not a README.
If your guidelines get long, split them into partials. Register a Blade view namespace for resources/boost/partials in your service provider and @include the partials from core.blade.php, the same way you'd compose any other Blade view.
Adding skills
Skills are different from guidelines: instead of loading upfront, they're loaded on demand when an agent decides a task is relevant to them. They're a better fit for anything detailed enough that you wouldn't want it sitting in context for every unrelated change.
Add one folder per skill under resources/boost/skills/:
resources/boost/skills/my-feature-development/SKILL.md
SKILL.md follows the Agent Skills format: YAML frontmatter with required name and description fields, followed by Markdown instructions.
---
name: my-package-development
description: Build and work with MyPackage features, including its components and workflows.
---
# MyPackage Development
## When to use this skill
Use this skill when working with MyPackage features — creating new components, wiring up workflows, or modifying existing integrations.
## Features
- Feature 1: a short, clear description.
- Feature 2: a short, clear description. Example usage:
$result = MyPackage::featureTwo($param1, $param2);
When a consumer runs boost:install and chooses to install skills, Boost detects your package in their composer.json and offers your skill for installation automatically — the same mechanism that installs livewire-development when livewire/livewire is present.
What happens on the consumer's side
None of this requires the consumer to do anything beyond the normal Boost setup:
composer require laravel/boost --dev
php artisan boost:install
boost:install scans installed packages, finds your resources/boost/guidelines/core.blade.php and resources/boost/skills/*/SKILL.md, and includes them with Laravel's own guidelines and skills. Running php artisan boost:update --discover later will pick up guidelines and skills from packages installed after the initial setup.
You don't publish anything, register a service provider hook, or add config. The convention-based paths are enough.
Adding the badge
Once your package ships guidelines or skills under resources/boost/, you can add a badge to your README to advertise it to users browsing your package.
Go to badge.laravel.cloud/preview, select Laravel Boost from the badge type selector, choose a style, and copy the snippet. The Markdown version looks like this:
[](https://github.com/laravel/boost)
Three styles are available: the default gradient, flat, and for-the-badge. Place it near your other badges at the top of the README.
The badge is static — it doesn't verify anything about your package's contents. It's a signal to readers that the package ships AI guidelines, not a guarantee Boost enforces. Make sure the resources/boost/ files are actually there and current before adding it.
Why it's worth doing
A handful of users are already running an AI agent on every change they make to their codebase, package included. Without guidelines, those agents are guessing at your API from whatever code they happen to read — which means more wrong first attempts, more time spent correcting generated code, and more issues filed that are really just usage mistakes. A core.blade.php that states your conventions plainly, and a skill for the parts that need more than a paragraph, closes that gap before it costs anyone time. It's a small amount of upfront writing that pays off on every AI-assisted integration of your package from then on.
End of guide · 2026
← Back to the archive