hwc-forms-validation
Handle Hotwire form workflows: form submission lifecycle, inline editing, validation errors, typeahead/autocomplete, modal forms,…
Handle media-heavy Hotwire features: image/video/audio uploads, previews, playback controls, progress tracking, and third-party media integrations (for example WaveSurfer, Swiper, Picture-in-Picture, Blurhash). Prefer this skill when the core problem is media rendering, playback
$ npx -y skills add thehotwireclub/hotwire_club-skills --skill hwc-media-content --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/hwc-media-contentContext preview
The summary Claude sees to decide when to auto-load this skill.
Handle media-heavy Hotwire features: image/video/audio uploads, previews, playback controls, progress tracking, and third-party media integrations (for example WaveSurfer, Swiper, Picture-in-Picture, Blurhash). Prefer this skill when the core problem is media rendering, playback
name: hwc-media-content description: >- Handle media-heavy Hotwire features: image/video/audio uploads, previews, playback controls, progress tracking, and third-party media integrations (for example WaveSurfer, Swiper, Picture-in-Picture, Blurhash). Prefer this skill when the core problem is media rendering, playback state, or media library integration. Use hwc-realtime-streaming for server-pushed Turbo Stream updates, hwc-navigation-content for non-media pagination/tab/lazy-navigation flows, hwc-forms-validation for form validation and inline-edit behavior, hwc-ux-feedback for generic loading/transition patterns, and hwc-stimulus-fundamentals for Stimulus primitives not specific to media.
Implement media-centric Hotwire features with Stimulus and Turbo Frames.
1. Identify media mode: upload/preview, playback controls, progress persistence, or embedded library integration. 2. Keep media state in Stimulus values; bridge third-party APIs through value callbacks and targets. 3. Use browser-native APIs first (`URL.createObjectURL`, Picture-in-Picture, IntersectionObserver, MediaSession). 4. Clean up all allocated resources in `disconnect()` (observers, blob URLs, player instances, timers). 5. Persist only intentional client state (for example playback progress) and reconcile on load.
Open only the file needed for the current request.
Use `references/INDEX.md` for the full catalog.
Claude skills for building modern web applications with Hotwire (Turbo and Stimulus). These skills are extracted from the Hotwire Club knowledge base and organized into 6 topic-based skills covering common patterns and best practices.
Handle Hotwire form workflows: form submission lifecycle, inline editing, validation errors, typeahead/autocomplete, modal forms,…
Build Hotwire navigation and content-discovery flows: Turbo Frame pagination, tabbed navigation, lazy loading, faceted…
Implement real-time Hotwire behavior: Turbo Streams over WebSocket/SSE, custom stream actions, inline stream tags, live list…
Cover Stimulus controller fundamentals: lifecycle hooks, values and valueChanged callbacks, targets and target callbacks,…
Implement cross-cutting Hotwire UX feedback patterns: loading states, busy indicators, progress bars, optimistic UI, render…