composer-packages

# composer-packages ## When to use Use this skill when creating, maintaining, or publishing Composer library packages — including Laravel packages with service providers, Artisan commands, and config publishing. ## Procedure: Work with Composer packages 1. Read the package's `composer.json` for structure and dependencies. 2. Check if it's a Laravel package (look for `extra.laravel.providers`). 3. Read the package's `README.md` and `CHANGELOG.md`. 4. Check the `agents/` directory in the package for package-specific docs. ## Known packages Check the project's `composer.json` for organization-specific packages. Check `agents/overrides/skills/composer-packages.md` for the package registry and known packages list. ## Package structure ``` my-package/ ├── src/ # Source code │ ├── App/ │ │ └── Providers/ # Laravel service providers │ └── ... ├── config/ # Publishable config files ├── tests/ # Package tests ├── composer.json # Package manifest ├── README.md # Documentation ├── CHANGELOG.md # Version history └── agents/ # Package-specific agent docs ``` ## composer.json essentials ### Required fields ```json { "name": "vendor/my-package", "type": "library", "description": "Clear, concise description", "require": { "php": "^8.2" }, "autoload": { "psr-4": { "Vendor\\MyPackage\\": "src/" } } } ``` #...