home / skills / laravel / boost / livewire-development

livewire-development skill

safe

/tests/Fixtures/vendor-skills/livewire-development

This skill optimizes Laravel Livewire development by applying vendor overrides and best practices to boost local AI-assisted workflows.

npx playbooks add skill laravel/boost --skill livewire-development

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

219 B

---
name: livewire-development
description: Vendor-overridden Livewire skill
---

# Livewire Development (Vendor Override)

This skill was discovered from a vendor package and should override the built-in .ai/ version.

Overview

This skill augments Livewire development by prioritizing vendor-provided overrides and integrating them into a local AI-powered Laravel workflow. It helps you detect and apply vendor-specific Livewire components, configurations, and templates so the project behavior matches the vendor intent. Use it to ensure the local development environment respects vendor customizations while still offering automation and suggestions.

How this skill works

The skill scans the Laravel project to locate vendor packages that include Livewire assets and checks for files intended to override core or default components. It maps vendor-provided views, components, and config to the application, highlights conflicts with built-in or local overrides, and offers guided actions to apply, revert, or merge vendor changes. It can run common Artisan and Livewire commands to validate the result and generate precise suggestions for adjustments.

When to use it

When a vendor package includes Livewire components or views that should override defaults.
During onboarding to a project that relies on vendor overrides for UI or behavior.
When upgrading vendor packages and you need to reconcile new overrides with local changes.
While debugging unexpected Livewire behavior that might originate from vendor files.
Before deploying to ensure vendor overrides are applied consistently across environments.

Best practices

Commit vendor override mappings and decision notes to version control so future maintainers understand applied overrides.
Run the skill’s conflict report after composer updates or when installing new vendor packages.
Prefer merging with clear comments rather than blind overwrites when vendor changes conflict with local code.
Use the skill’s validation commands (Artisan and Livewire tests) to confirm functional parity after applying overrides.
Keep vendor patches minimal and document rationale in changelogs or PR descriptions.

Example use cases

A merchant theme supplies custom Livewire components; apply and test those overrides automatically.
A vendor patch fixes a Livewire state bug; detect and merge the patch into your app while preserving local tweaks.
During an upgrade, identify vendor-provided view changes that conflict with local templates and generate merge suggestions.
On a fresh clone, ensure vendor overrides are registered so the UI matches staging and production behavior.

FAQ

Will this replace local files without confirmation?

No. The skill highlights conflicts and offers apply/revert/merge actions so you can choose before changes are made.

Does it run database or migration changes?

It can suggest and run Artisan commands if you approve, but it does not automatically perform destructive operations without confirmation.