AI-assisted development

#Introduction

AI coding agents like Claude Code, Cursor, and GitHub Copilot can significantly accelerate your Filament development. Filament includes an Agent Skill for Laravel Boost that teaches AI agents how to write idiomatic Filament code and follow framework conventions. Laravel Boost even allows your agent to search the Filament documentation for answers when it encounters unfamiliar requirements.

#Installing Laravel Boost

Install Boost as a development dependency:

composer require laravel/boost --dev

Then run the interactive installer. Select Agent Skills, followed by filament/filament (skills) when prompted:

php artisan boost:install

The installer will detect your IDE and AI agents, generating the necessary configuration files. To verify installation, check your agent’s skills directory for filament-development/SKILL.md.

For more information about Laravel Boost, including available tools, documentation search, and IDE integration, see the Laravel AI documentation.

#Filament Blueprint

The Filament skill is designed primarily for implementing agents: it helps agents write correct Filament code once they know what to build. However, the quality of AI-generated code depends heavily on the quality of the plan. When an implementing agent has a clear, detailed specification, it can focus entirely on writing correct code rather than guessing at requirements or making assumptions about your intent.

For complex features, you may find that agents struggle with the planning phase: choosing the right components, structuring relationships, and anticipating edge cases. A vague plan leads to vague code, and you end up spending more time correcting the agent than you saved by using it.

Filament Blueprint is a premium extension that helps AI agents produce accurate, detailed implementation plans for Filament. Blueprint 2.x supports Filament v5.

Blueprint bridges the gap between what you want and what AI agents build. Instead of hoping an agent understands Filament’s conventions, Blueprint provides a structured planning skill that produces unambiguous specification documents.

A blueprint specifies everything an implementing agent needs:

• Models: Attributes, casts, relationships, and enums with exact syntax
• Resources: Full namespaces, scaffold commands, and configuration
• Forms: Field components, validation rules, and layout structure
• Tables: Columns, filters, actions, and sorting behavior
• Authorization: Plain-English policy rules that translate directly to code
• Testing: What to test and how to verify it works
• More: Reactive fields, wizards, imports/exports, bulk actions, widgets, multi-tenancy, and more

The planning skill covers details that agents commonly get wrong, like namespaces, method names, component selection, and nested layout calculations, so the implementing agent can write correct code on the first try.

The planning skill is designed for planning agents only, so it shouldn’t consume the implementing agent’s context window. The planning agent copies all necessary details (namespaces, documentation URLs to fetch, exact method syntax) into the blueprint itself, so the implementing agent has everything it needs without loading the planning skill.

If you’re interested in an example of a plan that GPT-6 Astra can write with and without Blueprint, visit the Blueprint Plan Example section.

#Installing Blueprint

Use Blueprint 2.x with Filament v5.

Once you have purchased a license for Blueprint, install it via Composer:

composer config repositories.filament composer https://packages.filamentphp.com/composer
composer config --auth http-basic.packages.filamentphp.com "YOUR_EMAIL_ADDRESS" "YOUR_LICENSE_KEY"
composer require filament/blueprint --dev

Then run the Boost installer. Select Agent Skills, followed by filament/blueprint (skills) when prompted:

php artisan boost:install

To verify installation, check your agent’s skills directory for planning-filament/SKILL.md, reviewing-filament-plans/SKILL.md, and filament-security-audit/SKILL.md.

#Using Blueprint

#Writing a blueprint

To create a blueprint, enable planning mode in your AI agent, ask it to use the planning-filament skill, and specify a Markdown file for the plan:

Using the planning-filament skill, create a Filament Blueprint for a SaaS invoicing
system using this application's Filament version. Write the plan as Markdown to
blueprints/invoicing.md.

Include managing customers and products, creating and editing invoices with line
items, sending invoices, and recording and tracking payments. Describe the user
flows, Filament components, and state transitions. Flag unresolved business choices.

#Implementing a blueprint

Read the saved plan and resolve its outstanding business choices. Then switch out of planning mode and give the implementing agent the saved blueprint and access to your application checkout:

Implement blueprints/invoicing.md in this application checkout. Follow the plan
and run the relevant tests. Report what was implemented and any checks that
could not be completed.

#Reviewing an implementation against a blueprint

After implementation, use Blueprint’s reviewing-filament-plans skill with the same saved blueprint and application checkout to check whether the implementation satisfies the plan:

Using the reviewing-filament-plans skill, review the implementation in
this checkout against blueprints/invoicing.md, including the current uncommitted
changes.
Report requirement traceability, confirmed deviations, and anything blocked
or not verified. Do not change application code.

The report traces plan requirements to code and test evidence using Conforms, Deviates, Blocked, and Not verified. It distinguishes inspected code and test assertions from executed tests or browser checks, and recommends the smallest correction and verification for each confirmed deviation. Existing focused tests run only when an isolated, safe harness is established.

This is a plan-conformance review, not a second planning pass or a general security audit. It does not invent requirements omitted from the blueprint or treat omissions in an update plan as deletions.

#Blueprint Plan Example

The following Filament v5 prompt was used with GPT-6 Astra in Amp’s standard astra mode, in independent threads with and without the planning-filament skill:

Produce an implementation plan for a Filament v5 application. The application is
a SaaS invoicing system with the following capabilities:

- Manage customers
- Manage products
- Create and edit invoices
- Add line items to invoices
- Send invoices to customers
- Record and track payments
  
The plan should:
- Describe the primary user flows end to end (for example: creating an invoice,
  sending it, recording a payment).
- Map each domain concept and flow to concrete Filament primitives (Resources,
  Relation Managers, Pages, Actions).
- Identify state transitions (such as draft → sent → paid) and the Actions that
  trigger them.

You can read the plans written for this prompt without Blueprint and with Blueprint, and compare their proposed implementation details. These are planning outputs, not implemented applications or verified test results. Review their assumptions and resolve the outstanding business choices before passing either plan to an implementing agent.

#Running a security audit

Blueprint also ships a Filament Security Audit skill that scans a Filament codebase against a catalogue of known security misconfigurations (authorization, file uploads, XSS, query scoping, dependency CVEs, etc.) and writes a per-finding remediation plan. Every entry names the exact file, component namespace, documentation URL, and pasteable fix, so an implementing agent can apply it without guessing.

Naming the skill explicitly in your prompt is the most reliable way to invoke it. The skill also responds to the keywords security-audit, security-review, harden, and pen-test when paired with a target like a panel, resource, page, or Livewire component:

Using the filament-security-audit skill, audit the admin panel and write
the remediation plan to SECURITY_AUDIT.md.

The agent will produce a Markdown report grouped by finding category, plus a table of every check performed (Finding / Pass / N/A) and recommended tests for each confirmed issue.

#Reporting issues with Blueprint

If you encounter any issues or have suggestions for improving Filament Blueprint, please open an issue or discussion on the Filament Blueprint Issues GitHub repository. If you have account or purchase-related questions, please email support@filamentphp.com.

Edit on GitHub

Still need help? Join our Discord community or open a GitHub discussion