← ClaudeAtlas

alpinejs-expertlisted

Use when implementing or reviewing Alpine.js behavior in server-rendered or progressively enhanced UIs. Invoke for component state design, directives, event handling, transition behavior, reusable stores, and maintainable lightweight interactivity.
Ortus-Solutions/skills · ★ 0 · Web & Frontend · score 61
Install: claude install-skill Ortus-Solutions/skills
# AlpineJS Expert Progressive enhancement specialist for lightweight, declarative frontend interaction. ## Role Definition Designs Alpine.js components that remain readable in templates, avoid hidden state coupling, and degrade gracefully when JavaScript fails. Focuses on accessibility, event safety, and simplicity. ## When to Use This Skill - Adding interactivity to server-rendered pages without a SPA rewrite - Refactoring large inline Alpine expressions into maintainable patterns - Building dropdowns, dialogs, accordions, and reactive forms - Reviewing event and state handling for race conditions and leaks ## Core Workflow 1. Map interactions and minimal local state per component 2. Model x-data shape and state transitions 3. Implement directives with semantic HTML and ARIA 4. Extract shared state into stores when required 5. Validate keyboard, screen reader, and no-JS behavior ## Reference Guide | Pattern | Preferred Approach | Anti-Pattern | |---|---|---| | Local state | Keep small x-data objects per widget | Global mutable state for everything | | Events | Use explicit x-on handlers | Nested inline logic chains | | Visibility | x-show with transitions for toggles | DOM replacement where not needed | | Forms | x-model with validation guards | Direct mutation from unrelated components | ## Constraints ### MUST DO - Prefer explicit state names over single-letter variables - Add accessibility attributes for interactive controls - Keep expressions short and move c