Skip to content

Laravel Boost compatibility#7

Open
seomikewaltman wants to merge 4 commits intopbakaus:mainfrom
seomikewaltman:main
Open

Laravel Boost compatibility#7
seomikewaltman wants to merge 4 commits intopbakaus:mainfrom
seomikewaltman:main

Conversation

@seomikewaltman
Copy link

Current Functionality

Running /teach-impeccable appends the design context directly to the CLAUDE.md or AGENTS.md files

Updated Functionality

Running /teach-impeccable adds an option for Laravel Boost users. Instead of appending the CLAUDE.md or AGENTS.md files it will create an .ai/guidelines/design-context.md file. Laravel users run php artisan boost:update and it will append the .ai/.../design-context.md right into the CLAUDE.md or AGENTS.md files.

Reference

To augment Laravel Boost with your own custom AI guidelines, add .blade.php or .md files to your application's .ai/guidelines/* directory. These files will automatically be included with Laravel Boost's guidelines when you run boost:install.

🔗 Larval boost reference

This makes Impeccable compatible for Laravel users ;)

Local testing with Laravel

  1. Install Laravel Herd
  2. Create a site through Herd with a starter kit (toggle Install Laravel Boost on)
  3. Open a terminal cd ~/Herd/site-you-created
  4. Run php artisan boost:install - select the options that apply, will generate a CLAUDE.md and/or AGENTS.md
  5. Run claude and /teach-impeccable - select the Laravel Boost option instead of write to CLAUDE.md creates .ai/guidelines/design-context.md
  6. Run php artisan boost:update - CLAUDE.md has appended context from .ai/guidelines/design-context.md in it 👍🏼

@vercel
Copy link

vercel bot commented Feb 3, 2026

@seomikewaltman is attempting to deploy a commit to the Paul Bakaus' projects Team on Vercel.

A member of the Team first needs to authorize it.

@pbakaus
Copy link
Owner

pbakaus commented Mar 4, 2026

Apologies Mike, I somehow missed notifications on Impeccable PRs! Thanks for your submission. Could you please rebase or merge the latest from origin/main, and see if this fix or improvement still applies? Thanks!

# Conflicts:
#	dist/claude-code/.claude/commands/teach-impeccable.md
@seomikewaltman
Copy link
Author

Apologies Mike, I somehow missed notifications on Impeccable PRs! Thanks for your submission. Could you please rebase or merge the latest from origin/main, and see if this fix or improvement still applies? Thanks!

Done and smoke tested! It builds out the .ai/guidelines/design-context.md as expected. It'll integrate perfectly into Laravel projects :)

@pbakaus
Copy link
Owner

pbakaus commented Mar 10, 2026

Hey Mike,

the issues I have with this PR is that it steers Impeccable too hard towards Laravel:

Claude identified issue summary:

  • Adds framework-specific logic to a general-purpose tool — Every user running /teach-impeccable would now be asked about Laravel Boost, even if they don't use Laravel. This adds friction for 99% of users.
  • Modifies dist file directly — Changes .claude/skills/teach-impeccable/SKILL.md (a built output), but only for the claude-code provider. The other 5 providers would be out of sync. Only the source/ change should be committed; dist should be regenerated via bun run build.
  • Design concern — A better approach would be a separate skill or a plugin system rather than baking one framework's workflow into the core onboarding flow.

Is there something here that can be generalized?

@seomikewaltman
Copy link
Author

Hey Mike,

the issues I have with this PR is that it steers Impeccable too hard towards Laravel:

Claude identified issue summary:

  • Adds framework-specific logic to a general-purpose tool — Every user running /teach-impeccable would now be asked about Laravel Boost, even if they don't use Laravel. This adds friction for 99% of users.
  • Modifies dist file directly — Changes .claude/skills/teach-impeccable/SKILL.md (a built output), but only for the claude-code provider. The other 5 providers would be out of sync. Only the source/ change should be committed; dist should be regenerated via bun run build.
  • Design concern — A better approach would be a separate skill or a plugin system rather than baking one framework's workflow into the core onboarding flow.

Is there something here that can be generalized?

I think so. I can adjust the prompt to check for a composer.json and laravel/boost package. IF found then write to the .ai/guidelines/... if not then append the appropriate CLAUDE.md or AGENTs.md file etc.

Default mode would be the current functionality, no friction or extra question prompts.

…e location

Replace the manual storage choice (Step 3/4) with automatic detection —
checks composer.json for laravel/boost dependency. If found, writes to
.ai/guidelines/design-context.md; otherwise writes to the AI config file.
Keeps the skill at 3 steps with zero friction.
@seomikewaltman seomikewaltman requested a review from pbakaus as a code owner March 13, 2026 20:12
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.

2 participants