Load starter kit guidelines and gate full-app guidance on structure - #991
Open
pushpak1300 wants to merge 1 commit into
Open
Load starter kit guidelines and gate full-app guidance on structure#991pushpak1300 wants to merge 1 commit into
pushpak1300 wants to merge 1 commit into
Conversation
pushpak1300
marked this pull request as ready for review
August 31, 2026 14:55
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Boost currently gives every project the full-app Laravel guidance. On the new slim agent starter kit (
laravel/agent-kit), most of it is wrong: the kit has nopackage.json, noapp/Models, and noapp/Http, yet the composed guidelines still tell agents about Vite manifest errors, model factories, and Eloquent API Resources. There was also no way to give a starter kit its own guidance without shipping override files inside the kit skeleton.This builds on laravel/roster#71. Starter kits declare their identity in composer.json:
GuidelineComposerreads it throughProjectManager::starterKit()and composes.ai/kits/<name>/core.blade.phpas akits/<name>section. An unknown kit with no guideline directory is ignored, and the existing customization points apply unchanged: a project file at.ai/guidelines/kits/agent-kit/core.blade.phpreplaces the bundled guideline, andboost.guidelines.excluderemoves it.Separately, the Laravel core guideline now only renders sections whose subject exists in the project: the Vite error section requires a
package.json, model creation guidance requiresapp/Models, and the API resources section requiresapp/Http. Any slim app benefits from this, agent kit or not.Decisions made along the way:
extra.laravel.starter-kitrather than the composernamefield (users rename it) or a package fingerprint (addinglaravel/aito a full app must not change its Laravel guidance).kits/directory mapping andagent-kitname normalization stay in Boost.laravel/rosteris bumped to^1.1becausestarterKit()is not in v1.0.0. A v1.1.0 tag is needed for stable installs; until thenminimum-stability: devresolves1.x-dev.Tests cover kit guideline inclusion, absence without a declaration, unknown kits, the
.ai/guidelinesoverride path, and both sides of thepackage.jsongate.🤖 Generated with Claude Code