Skip to content

feat: Improve Laravel Boost AI Skills Integration - #2157

Open
rupeshstha wants to merge 1 commit into
nWidart:masterfrom
rupeshstha:boost/add-laravel-boost-skills
Open

feat: Improve Laravel Boost AI Skills Integration#2157
rupeshstha wants to merge 1 commit into
nWidart:masterfrom
rupeshstha:boost/add-laravel-boost-skills

Conversation

@rupeshstha

@rupeshstha rupeshstha commented Apr 24, 2026

Copy link
Copy Markdown
Contributor

Improve Laravel Boost AI Skills Integration

This PR revisits the Laravel Boost AI skills integration introduced in #2156, bringing it into full alignment with the conventions used across the Boost ecosystem (e.g. laravel/octane, laravel/pennant).

What Changed

The skills and guidelines have been relocated from .ai/laravel-modules/ to resources/boost/ — the canonical discovery path that laravel/boost scans when a package is opted into via boost:update --discover.

The skill file has been migrated from .blade.php to .md (pure Markdown), consistent with how other third-party packages deliver their skill content. Frontmatter has also been aligned to ensure the name and description are correctly parsed by the Boost skill loader.

resources/boost/
├── guidelines/
│   └── core.blade.php
└── skills/
    └── laravel-modules-development/
        ├── SKILL.md
        └── rules/
            ├── architecture.md
            ├── configuration.md
            ├── generators.md
            └── testing.md

What to expect

Once nwidart/laravel-modules is opted into Boost (boost:update --discover or added to boost.json), running php artisan boost:install will:

  • Populate skill directories for all supported AI agents - Claude Code, Cursor, GitHub Copilot, Gemini, Junie, and others with the full skill and all reference files
  • Write activation entries to the corresponding guidelines files (CLAUDE.md, AGENTS.md, .cursor/rules/, etc.) so any AI assistant automatically loads the skill when working with modules

The skill covers:

  • All module:make-* generators and flags
  • Module management, database operations, and publishing commands
  • Naming conventions, service provider architecture, and module.json structure
  • Auto-discovery configuration (auto-discover.migrations, auto-discover.translations)
  • Inter-module communication via events/listeners
  • Inertia.js support (--inertia, module:make-inertia-page, etc.)
  • Pest testing within modules
  • Common pitfalls and their solutions

Testing

Verified end-to-end: after composer update + php artisan boost:install, the skill appears in boost:list-skills output and activation entries are written across all supported agent guideline files.

Adds structured AI assistant context following the laravel/boost convention:

- resources/boost/guidelines/core.blade.php: always-on context injected
  into every AI session (module namespace, naming, disabled-module behavior,
  inter-module coupling rule, optimize:clear reminder)

- resources/boost/skills/laravel-modules-development/SKILL.md: on-demand
  skill with activation triggers, quick-reference index, and pointers to
  the rules/ sub-documents

- resources/boost/skills/laravel-modules-development/rules/: detailed
  reference documents loaded by the AI as needed:
  - architecture.md — directory structure, service providers, naming conventions,
    Module facade, inter-module communication, Blade directives, load order
  - generators.md — all module:make-* commands with options
  - configuration.md — config/modules.php options, auto-discovery, activators
  - testing.md — Pest test patterns, factories, running module tests

Removes the previous .ai/laravel-modules/ placement which was not read by
laravel/boost for third-party packages (only resources/boost/ is scanned).

When nwidart/laravel-modules is installed and a user runs
`php artisan boost:update --discover`, this package will appear as a
newly available skill to opt into.
@rupeshstha rupeshstha changed the title feat: Improve Laravel Boost AI skills and guidelines feat: Improve Laravel Boost AI Skills Integration Apr 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant