hwc-forms-validation
Handle Hotwire form workflows: form submission lifecycle, inline editing, validation errors, typeahead/autocomplete, modal forms,…
Implement cross-cutting Hotwire UX feedback patterns: loading states, busy indicators, progress bars, optimistic UI, render interception, and view/page transitions. Prefer this skill when the core goal is perceived performance and user feedback, independent of a single feature
$ npx -y skills add thehotwireclub/hotwire_club-skills --skill hwc-ux-feedback --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/hwc-ux-feedbackContext preview
The summary Claude sees to decide when to auto-load this skill.
Implement cross-cutting Hotwire UX feedback patterns: loading states, busy indicators, progress bars, optimistic UI, render interception, and view/page transitions. Prefer this skill when the core goal is perceived performance and user feedback, independent of a single feature
name: hwc-ux-feedback description: >- Implement cross-cutting Hotwire UX feedback patterns: loading states, busy indicators, progress bars, optimistic UI, render interception, and view/page transitions. Prefer this skill when the core goal is perceived performance and user feedback, independent of a single feature domain. Use hwc-forms-validation for form correctness and validation behavior, hwc-navigation-content for navigation/history/cache mechanics, hwc-realtime-streaming for push/stream orchestration, hwc-media-content for media-specific behavior, and hwc-stimulus-fundamentals for base Stimulus API questions.
Implement cross-cutting feedback and perceived-performance patterns in Hotwire.
1. Identify feedback need: loading, submit activity, progress reporting, optimistic updates, or transitions. 2. Prefer built-in Turbo semantics first (`busy`, progress bar hooks, submit/render lifecycle events). 3. Add optimistic updates only with a clear reconciliation strategy. 4. Keep transition logic bounded to explicit lifecycle events and cache/preview-safe paths. 5. Verify UX behavior on slow network, back/forward cache restores, and submission failures.
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,…
Handle media-heavy Hotwire features: image/video/audio uploads, previews, playback controls, progress tracking, and third-party…
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,…