The problem is not limited to artisan commands. I don't have php, composer and node installed. Everything is ran in containers. So instead of 'npm ...' I use 'lando npm ...'.

• 'php artisan make...' -> 'lando atrisan make...'
• 'npm run build' -> 'lando npm run build'
• 'composer dump-autoload' -> 'lando composer dump-autoload'

I'm working an a new project with Laravel 13. I'm using Lando as my development environment and everything is running in Docker containers. After installing boost I edited the mcp.json so it's using the proper command to start the MCP server.

Because every service has to be called within Lando I created a custom guideline and skill to make sure Copilot uses the correct commands. Without manually changing the commands in the .github/guidelines and AGENTS.md from 'php artisan...' to 'lando artisan...', Copilot does use lando to make use of the services. It's working great!

So what's the problem? Well, a second developer is going to help me, and he doesn't use Lando. So the guideline to use the 'lando' command doesn't work for him. This should only apply to my development environment.

Is there any convention to use local guidelines and let laravel/boost update the AGENTS.md based on local guidelines?