Conventions & Workflow

Every oi-lab/oi-laravel-* package is independent, but they are all built to the same in-house standard, distilled from the whole ecosystem. That standard is what makes the packages feel consistent: learn the pattern once and every package becomes predictable — same naming, same configuration, same testing, same AI tooling, same release flow.

This section documents that transversal approach.

In this section

• Common conventions — naming, composer.json, service providers, configuration, model resolution, and the spatie/laravel-data boundary. The rules every package follows.
• Skills & AI — every package ships an AI-assistant skill and injects rules into your CLAUDE.md, so your coding assistant knows how to use it. How the skill system works and how to keep it in sync.
• Publishing & updates — how packages are released (package:release, per-package git repos, Packagist) and how you keep installed packages and their skills up to date.
• Contributing & support — licensing, where the code lives, and how to report issues or contribute.

Why it matters to you

Even if you only ever install one package, this shared standard is why it behaves the way the others do: configuration is published under a predictable tag, models can be swapped through config, structured data crosses the package boundary as typed spatie/laravel-data objects, and your AI assistant already knows the package's API. The consistency is the feature.