Laravel Nativephp Boost Laravel Package

Getting Started

• Install the package with Composer and follow the README’s requirements/banner section first; v1.0.1 explicitly documents supported PHP/Laravel versions and Laravel Boost 2.x compatibility.
• Publish any package config or stubs if the README instructs it, then run the package’s planning-guide generation command.
• First use case: generate the planning guide immediately after installing Laravel Boost 2.x, then open the generated file to confirm it landed at the expected path. v1.0.1 fixes the generated planning-guide path, so this is the first thing to verify after upgrading.
• Look next at the package’s config file for output path, template/stub selection, and any Boost integration settings.

Implementation Patterns

• Bootstrap workflow: install the package alongside Laravel Boost 2.x, publish config, generate the planning guide, and commit the generated guide so the team and AI tooling share the same project context.
• Regeneration workflow: treat the planning guide as generated documentation. Regenerate it after major architecture changes, new modules, or onboarding updates rather than editing it by hand.
• Boost integration: ensure the application’s Boost setup points at the generated guide. Since v1.0.1 adds Boost 2.x support, verify the installed Boost major version before relying on the integration.
• Custom templates: if the package exposes publishable stubs/views, publish them and keep project-specific wording in version control. Re-publish only when the package’s upstream template changes.
• CI/onboarding checks: add a lightweight check that the generated guide exists at the configured path and is current enough for onboarding. This catches path regressions like the one fixed in v1.0.1.

Gotchas and Tips

• Regenerate after upgrading to v1.0.1. The planning-guide path fix means previously generated files may sit at the old location. Delete stale guides and regenerate, then update any docs or Boost config that referenced the old path.
• Check Boost version constraints. v1.0.1 supports Laravel Boost 2.x; older Boost versions may not be compatible. Confirm composer show before debugging generation issues.
• Clear config caches after changing paths. If the output path is configurable, run php artisan config:clear after edits, and confirm whether the path is relative to the project root or the package’s configured base directory.
• Read the release banner/requirements. The new banner and requirements section is the quickest way to catch PHP/Laravel minimums before installing in older projects.
• Debugging generation: verify publishable assets are present, check filesystem permissions on the target directory, and inspect the command output for the resolved path. If the guide appears missing, search the project for the filename before assuming generation failed.
• Extension point: prefer publishing and overriding templates/config over editing vendor files. This keeps upgrades to future 1.x releases straightforward.