dhpk-laravel-package-authorlisted

# Laravel package author Use this skill for code distributed as a Laravel package. A package ships more than classes: service providers, facades, configuration, migrations, routes, views, and assets are separate consumer contracts. ## Working sequence 1. Identify the supported Laravel and PHP range and every published surface. 2. Load `references/authoring-patterns.md` for the provider, binding, facade, matrix, publishing, discovery, or compatibility branch being changed. 3. Keep provider registration, public aliases, version branches, and published names explicit; pair each conditional branch with a test cell. 4. Validate the package as a real consumer, not only from its own repository. ## Contract branches - Provider lifecycle or deferred binding → `authoring-patterns.md` §Service provider. - Multi-major behavior → §Version-conditional bindings and the Testbench skill. - Facade or auto-discovery → §Facades and discovery metadata. - Config, views, assets, routes, or migrations → §Publishing recipes. - Released names or artifact compatibility → §Laravel-specific compatibility surface. ## When NOT to Use - Application controllers, jobs, or models that are not distributed to consumers. - Version-specific Laravel deprecations or new APIs; use the matching `laravel-N` module. - Semver, Composer manifest, or registry publication decisions; use `dhpk-composer-package-hygiene`. - Detailed per-cell Testbench setup; use `dhpk-laravel-testbench-matrix`. ## Output Retur