Filament Devtool Laravel Package

Getting Started

v0.1.5 is an additive release: it ships a copy of compose.yaml inside the package skeleton so Laravel Boost can detect Laravel Sail and add the Laravel Sail guideline. There are no indicated breaking changes, so existing installs should upgrade normally.

Start by:

1. Updating the package to v0.1.5 with Composer.
2. Running your normal Laravel Boost guideline install/update workflow.
3. Confirming the project root has a standard compose.yaml.
4. Inspecting the generated Boost guideline output to verify the Sail guideline was added.

For a new project, scaffold from the package skeleton, confirm compose.yaml is present, then run Boost. The first practical use case is asking your AI assistant to make a Sail-aware change, such as “add Redis to this project’s Sail services and update the environment configuration,” and letting the Sail guideline steer the response.

Where to look first: the package skeleton’s compose.yaml, your application root compose.yaml, and the guideline files generated by Laravel Boost.

Implementation Patterns

• New projects: Use the package skeleton so compose.yaml exists from the start, then run Laravel Boost to install the Sail guideline. This gives the assistant project-specific Sail context immediately.
• Existing projects: v0.1.5 does not automatically add compose.yaml to already-scaffolded apps. Add or restore a standard compose.yaml, or run Sail’s installer, then refresh Boost guidelines.
• Sail changes: Treat compose.yaml as the source of truth. When adding services, changing ports, or updating environment variables, make the Compose change first, then re-run Boost so the guideline reflects the current project shape.
• AI-assisted workflows: Use the Sail guideline for service additions, container debugging, Sail command explanations, onboarding docs, and review comments. Good prompts reference the actual compose.yaml and .env rather than asking generically about Docker.
• Onboarding: Document the Boost install/update command in the project README so new developers generate the same guideline set locally.
• CI hygiene: If generated guidelines are committed, add a check that compose.yaml exists and that Boost output is current after dependency or Compose changes.

Gotchas and Tips

• The v0.1.5 change is a skeleton improvement, not a migration. Existing apps must add compose.yaml themselves if they want Boost to detect Sail.
• Boost may skip the Sail guideline if the file is missing, renamed, or non-standard. Prefer the conventional root compose.yaml; avoid docker-compose.yml unless you also provide manual guidance.
• Re-run Boost after upgrading the package or changing Sail services. Stale guidelines are worse than no guideline because the assistant may suggest outdated containers or ports.
• Do not hand-edit generated guideline files as your primary customization path. Prefer package configuration or documented extension points, and keep custom project instructions separate.
• If your team uses a custom Compose filename or multiple Compose files, add explicit project guidance so the assistant knows which file is authoritative.
• Verify the Boost/MCP connection and permissions in the AI tool you use; guideline generation can succeed while the assistant still lacks access to project context.
• This is a minor release with no obvious deprecations, but still review the generated diff after upgrading and pin versions where reproducibility matters.