claude-import-livewire-components

Builds and reviews Livewire components using version-aware Livewire, Flux, and Alpine conventions.

Updated Aug 25, 2017
One-click install
npx skills add https://github.com/loki495/dotfiles --skill claude-import-livewire-components-loki495
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: claude-import-livewire-components
Source: https://github.com/loki495/dotfiles/tree/main/ai/codex-skills/claude-import-livewire-components
Command: npx skills add https://github.com/loki495/dotfiles --skill claude-import-livewire-components-loki495

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Livewire syntax and best practices vary significantly across versions, and mixing conventions from the wrong version leads to broken components. This Skill ensures components are built or reviewed against the correct installed Livewire version and the project's existing component style. ## Core Features & Use Cases - Version-Aware Component Generation: Detects the installed Livewire version before choosing syntax, so generated components match what the project actually runs. - Convention-Aligned Reviews: Reviews Livewire components against Andres's established conventions covering Livewire, Flux, Alpine.js, and optimistic-update patterns. - Use Case: When adding a new interactive form to a Laravel application, use this Skill to generate a Livewire component that follows the project's Flux UI patterns and uses optimistic updates consistent with existing components. ## Quick Start Ask the assistant to create a new Livewire component for a contact form following the project's Livewire and Flux conventions.

Frequently Asked Questions about claude-import-livewire-components

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Livewire component that matches my installed version?▼

Detect the installed Livewire version first, then choose syntax accordingly, since Livewire 2 and Livewire 3 differ in component structure and directives. This Skill reads the version-aware conventions and inspects existing components before generating code.

How to review Livewire components for convention compliance?▼

Review components against the project's established Livewire, Flux, and Alpine conventions, checking that syntax matches the installed version and that optimistic-update patterns are applied consistently with existing components.

Does this work with Flux UI and Alpine.js in Livewire projects?▼

Yes, the conventions explicitly cover Flux UI components and Alpine.js interactions alongside Livewire. Components are built or reviewed to integrate these libraries following the project's established patterns.

Why do Livewire components break after a version upgrade?▼

Livewire major versions change component syntax, directive names, and lifecycle hooks. Components written for an older version fail silently or throw errors, which is why version detection must happen before choosing syntax.

What are optimistic updates in Livewire components?▼

Optimistic updates modify the UI immediately before server confirmation, typically using Alpine.js state alongside Livewire requests. This Skill applies the project's specific optimistic-update conventions when building interactive components.