livewire-development — community livewire-development, fitapp, community, ide skills

v1.0.0

About this Skill

Perfect for Full Stack Agents needing advanced Livewire component development capabilities. Develops reactive Livewire 4 components. Activates when creating, updating, or modifying Livewire components; working with wire:model, wire:click, wire:loading, or any wire: directives; adding real-ti

TijmenWierenga TijmenWierenga
[0]
[0]
Updated: 3/11/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
7/11
Quality Score
45
Canonical Locale
en
Detected Body Locale
en

Perfect for Full Stack Agents needing advanced Livewire component development capabilities. Develops reactive Livewire 4 components. Activates when creating, updating, or modifying Livewire components; working with wire:model, wire:click, wire:loading, or any wire: directives; adding real-ti

Core Value

Empowers agents to create and modify Livewire components, leveraging wire: directives such as model, click, and loading, while implementing islands or async actions for enhanced user experience, utilizing Livewire 4 patterns and documentation.

Ideal Agent Persona

Perfect for Full Stack Agents needing advanced Livewire component development capabilities.

Capabilities Granted for livewire-development

Creating dynamic Livewire components with wire: directives
Implementing async actions for improved performance
Writing comprehensive tests for Livewire components

! Prerequisites & Limits

  • Requires Livewire 4 knowledge and setup
  • Specific to Livewire development, not applicable to other frameworks

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is livewire-development?

Perfect for Full Stack Agents needing advanced Livewire component development capabilities. Develops reactive Livewire 4 components. Activates when creating, updating, or modifying Livewire components; working with wire:model, wire:click, wire:loading, or any wire: directives; adding real-ti

How do I install livewire-development?

Run the command: npx killer-skills add TijmenWierenga/fitapp/livewire-development. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for livewire-development?

Key use cases include: Creating dynamic Livewire components with wire: directives, Implementing async actions for improved performance, Writing comprehensive tests for Livewire components.

Which IDEs are compatible with livewire-development?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for livewire-development?

Requires Livewire 4 knowledge and setup. Specific to Livewire development, not applicable to other frameworks.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add TijmenWierenga/fitapp/livewire-development. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use livewire-development immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

livewire-development

Install livewire-development, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Livewire Development

When to Apply

Activate this skill when:

  • Creating or modifying Livewire components
  • Using wire: directives (model, click, loading, sort, intersect)
  • Implementing islands or async actions
  • Writing Livewire component tests

Documentation

Use search-docs for detailed Livewire 4 patterns and documentation.

Project Conventions

These conventions are specific to this project. When proposing changes to these conventions, update .ai/guidelines/project-guidelines.md.

Authorization

Use $this->authorize() with policies in Livewire action methods. Use #[CurrentUser] for injecting the authenticated user instead of the Auth facade.

<!-- Livewire Authorization -->
php
1// Good 2use Illuminate\Container\Attributes\CurrentUser; 3 4public function saveReport(#[CurrentUser] User $user): void 5{ 6 $this->authorize('create', [InjuryReport::class, $this->injury]); 7 // ... 8} 9 10// Bad 11public function saveReport(): void 12{ 13 if (Auth::id() !== $this->injury->user_id) { 14 return; 15 } 16 // ... 17}

Authorize at the action level (e.g. saveReport, deleteReport), not in mount(). This keeps authorization close to the mutation and leverages policies consistently.

Mount Methods

Omit mount() when it only assigns typed public properties — Livewire handles this automatically.

Basic Usage

Creating Components

<!-- Component Creation Commands -->
bash
1 2# Single-file component (default in v4) 3 4{{ $assist->artisanCommand('make:livewire create-post') }} 5 6# Multi-file component 7 8{{ $assist->artisanCommand('make:livewire create-post --mfc') }} 9 10# Class-based component (v3 style) 11 12{{ $assist->artisanCommand('make:livewire create-post --class') }} 13 14# With namespace 15 16{{ $assist->artisanCommand('make:livewire Posts/CreatePost') }}

Converting Between Formats

Use php artisan livewire:convert create-post to convert between single-file, multi-file, and class-based formats.

Component Format Reference

FormatFlagStructure
Single-file (SFC)defaultPHP + Blade in one file
Multi-file (MFC)--mfcSeparate PHP class, Blade, JS, tests
Class-based--classTraditional v3 style class
View-based⚡ prefixBlade-only with functional state

Single-File Component Example

<!-- Single-File Component Example -->
php
1<?php 2use Livewire\Component; 3 4new class extends Component { 5 public int $count = 0; 6 7 public function increment(): void 8 { 9 $this->count++; 10 } 11} 12?> 13 14<div> 15 <button wire:click="increment">Count: @{{ $count }}</button> 16</div>

Livewire 4 Specifics

Key Changes From Livewire 3

These things changed in Livewire 4, but may not have been updated in this application. Verify this application's setup to ensure you follow existing conventions.

  • Use Route::livewire() for full-page components; config keys renamed: layoutcomponent_layout, lazy_placeholdercomponent_placeholder.
  • wire:model now ignores child events by default (use wire:model.deep for old behavior); wire:scroll renamed to wire:navigate:scroll.
  • Component tags must be properly closed; wire:transition now uses View Transitions API (modifiers removed).
  • JavaScript: $wire.$js('name', fn)$wire.$js.name = fn; commit/request hooks → interceptMessage()/interceptRequest().

New Features

  • Component formats: single-file (SFC), multi-file (MFC), view-based components.
  • Islands (@island) for isolated updates; async actions (wire:click.async, #[Async]) for parallel execution.
  • Deferred/bundled loading: defer, lazy.bundle for optimized component loading.
FeatureUsagePurpose
Islands@island(name: 'stats')Isolated update regions
Asyncwire:click.async or #[Async]Non-blocking actions
Deferreddefer attributeLoad after page render
Bundledlazy.bundleLoad multiple together

New Directives

  • wire:sort, wire:intersect, wire:ref, .renderless, .preserve-scroll are available for use.
  • data-loading attribute automatically added to elements triggering network requests.
DirectivePurpose
wire:sortDrag-and-drop sorting
wire:intersectViewport intersection detection
wire:refElement references for JS
.renderlessComponent without rendering
.preserve-scrollPreserve scroll position

Best Practices

  • Always use wire:key in loops
  • Use wire:loading for loading states
  • Use wire:model.live for instant updates (default is debounced)
  • Validate and authorize in actions (treat like HTTP requests)

Configuration

  • smart_wire_keys defaults to true; new configs: component_locations, component_namespaces, make_command, csp_safe.

Alpine & JavaScript

  • wire:transition uses browser View Transitions API; $errors and $intercept magic properties available.
  • Non-blocking wire:poll and parallel wire:model.live updates improve performance.

For interceptors and hooks, see reference/javascript-hooks.md.

Testing

<!-- Testing Example -->
php
1Livewire::test(Counter::class) 2 ->assertSet('count', 0) 3 ->call('increment') 4 ->assertSet('count', 1);

Verification

  1. Browser console: Check for JS errors
  2. Network tab: Verify Livewire requests return 200
  3. Ensure wire:key on all @foreach loops

Common Pitfalls

  • Missing wire:key in loops → unexpected re-rendering
  • Expecting wire:model real-time → use wire:model.live
  • Unclosed component tags → syntax errors in v4
  • Using deprecated config keys or JS hooks
  • Including Alpine.js separately (already bundled in Livewire 4)

Related Skills

Looking for an alternative to livewire-development or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

333.8k
0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

149.6k
0
AI

flags

Logo of vercel
vercel

The React Framework

138.4k
0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

98.6k
0
Developer