Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
create-laravel-package
create-laravel-package
alizharb/agent-skills
claude-code
package-development
composer
service-providers
config-publishing
testbench
ci
pest

Use when creating a Laravel package with Composer metadata, service provider, config publishing, commands, tests, CI, and release docs.

Install
php artisan boost:add-skill alizharb/agent-skills

Save this content to: .claude/skills/create-laravel-package/SKILL.md

# Create Laravel Package

## When To Use

Use this skill when starting or converting a repository into a reusable Laravel package.

## Workflow

1. Inspect existing package conventions, composer metadata, namespaces, and service providers.
2. Add or update `composer.json` with author, license, autoloading, support links, keywords, and Laravel auto-discovery.
3. Create a service provider that registers config, commands, views, translations, assets, or migrations only when needed.
4. Add config publishing and avoid forcing application files into the host app.
5. Add Pest/Testbench tests for package boot, command registration, config publishing, and core behavior.
6. Add CI for Composer validation, Pint, PHPStan, and tests.
7. Document installation, usage, configuration, testing, and release process.

## Verification

- Run `composer validate`.
- Run `vendor/bin/pint --test`.
- Run `vendor/bin/pest`.
- Run `vendor/bin/phpstan analyse`.

## Common Mistakes

- Hardcoding app paths instead of publishing configuration.
- Missing Laravel auto-discovery.
- Shipping examples that do not match supported Laravel versions.

Create Laravel Package

When To Use

Use this skill when starting or converting a repository into a reusable Laravel package.

Workflow

  1. Inspect existing package conventions, composer metadata, namespaces, and service providers.
  2. Add or update composer.json with author, license, autoloading, support links, keywords, and Laravel auto-discovery.
  3. Create a service provider that registers config, commands, views, translations, assets, or migrations only when needed.
  4. Add config publishing and avoid forcing application files into the host app.
  5. Add Pest/Testbench tests for package boot, command registration, config publishing, and core behavior.
  6. Add CI for Composer validation, Pint, PHPStan, and tests.
  7. Document installation, usage, configuration, testing, and release process.

Verification

  • Run composer validate.
  • Run vendor/bin/pint --test.
  • Run vendor/bin/pest.
  • Run vendor/bin/phpstan analyse.

Common Mistakes

  • Hardcoding app paths instead of publishing configuration.
  • Missing Laravel auto-discovery.
  • Shipping examples that do not match supported Laravel versions.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
3mdikram/worldmoneywords
snowsoft/config
itmosoft/laravel-subscriptions
larva/laravel-ai-qwen
diephp/sequences
users-au/socialite-provider
twidpay/twid-logger
mrnewport/laravel-plaid
mrnewport/laravel-repo
mrnewport/laravel-docsign
mrnewport/laravel-stow
mrnewport/laravel-flow
mrnewport/laravel-priceable
mrnewport/laravel-nestedterms
fredmeng/laravel-apidoc-generator
itstructure/laravel-multilingual-tools
pdustdar/elasticsearch
markupai/php-sdk
rlacerda83/lumem-microservice-shipment
uni-method/symfony-lib