Getting Started

Install the package with Composer:

composer require <vendor>/<package>:^0.2.2

Confirm your Prism constraint is compatible. As of v0.2.2 the package supports both Prism 0.99 and 0.100. If another dependency requires Prism 0.100, this release removes the previous ^0.99.0 installation block.
Look first at:
- composer.json — confirm the package’s Prism constraint uses an OR range such as ^0.99 || ^0.100.
- The package service provider — check for config publishing, bindings, and auto-discovery.
- The README and config/ directory — identify the package’s public API and configuration keys.

Run the package’s migrations or publish its config if required:

php artisan vendor:publish --provider="Vendor\\Package\\PackageServiceProvider"

First use case: wire the package into a small Prism-backed flow, such as a queued job or artisan command, and run it against a fake/test provider before using a real LLM provider.

Implementation Patterns

Use the package behind an application service. Keep Prism calls inside your own service, job, or action class rather than scattering them through controllers. This makes it easier to swap providers, add retries, and test without hitting external APIs.
Pin Prism deliberately. If your application depends on Prism features introduced in 0.100, require ^0.100; if you need to support both, use ^0.99 || ^0.100. Do not rely on ^0.99 alone to pull in 0.100.
Test against both supported Prism minors. The package’s own CI now covers 0.99 and 0.100; mirror that in application CI if you support both. A small matrix job is usually enough:
```
strategy:
  matrix:
    prism: ['^0.99', '^0.100']
```
Use Prism fakes in feature tests. Exercise the package through your application service and assert on prompts, tool calls, and responses without making real provider requests.
Queue long-running LLM work. Wrap Prism calls in jobs with timeouts and retries; keep HTTP/controller requests short.
Keep provider configuration environment-driven. Bind Prism providers through config and the container so local, staging, and production can use different providers or fake implementations.
Adopt the Dependabot widen strategy for Composer updates. The v0.2.2 release notes show Composer updates using widen, which is appropriate for libraries that need to support multiple dependency ranges.

Composer caret ranges pin the minor on 0.x. ^0.99.0 does not allow 0.100; it effectively means >=0.99.0 <0.100.0. Use ^0.99 || ^0.100 or an explicit range when supporting both.
Run composer why-not when installation fails. If Composer refuses to install alongside another package, use:
```
composer why-not prism-php/prism 0.100
```
This quickly identifies the package still pinning the older minor.
Use --with-all-dependencies when upgrading. If Prism is already locked, a normal composer update may not move it:
```
composer update <vendor>/<package> prism-php/prism --with-all-dependencies
```
Prism 0.100 may have behavioral differences. Even where the API is compatible, test response handling, streaming, tool calls, and error paths against both minors if you claim support for both.
Dependabot configuration can fail silently. The release notes mention an unsupported github-actions cooldown option that disabled all version updates. Validate Dependabot config and check that update PRs are actually being opened after changes.
Check the package’s service provider for extension points. Config publishing, container bindings, and macros are the usual places to customize behavior without forking.
Keep an eye on future Prism minor releases. Since 0.x minors can introduce breaking changes, review Prism’s changelog before widening the constraint beyond 0.100.