agentleFS
lgzarturolgzarturo/codeconductor/.agents/skills/livewire-alpine-bridge/SKILL.md

livewire-alpine-bridge

Skill0 starsChanged 27 days agoMITView on GitHub

Schedules reactive frontend states cleanly using entangle directives in PHP and JS.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Lazy Syncing: Use .live modifier selectively.

    line 23

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Livewire Alpine Bridge

Core Principles

  1. State Entanglement: Synchronize states between Livewire properties and Alpine.js states using the @entangle directive.
  2. Minimize Network Roundtrips: Handle purely UI-related reactive interactions (modals, dropdowns, tab switches) strictly in Alpine.js without sending requests to the server.
  3. Lazy Syncing: Use .live modifier selectively. Rely on .defer or deferred synchronization for inputs to prevent heavy server load.

Implementation Pattern

<div x-data="{ open: @entangle('showModal') }">
    <button @click="open = true">Open Modal</button>
    
    <div x-show="open" @click.away="open = false">
        Modal Content
    </div>
</div>

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.