skills/hwc-realtime-streaming/SKILL.md
Implement real-time Hotwire behavior: Turbo Streams over WebSocket/SSE, custom stream actions, inline stream tags, live list updates, and cross-tab state synchronization. Prefer this skill when the core problem is push-based updates or stream action orchestration. Use hwc-navigation-content for pull-based pagination/tab/lazy-navigation flows, hwc-forms-validation for form lifecycle and validation, hwc-media-content for media upload/playback behavior, hwc-ux-feedback for generic loading/progress/transitions, and hwc-stimulus-fundamentals for non-stream Stimulus fundamentals.
npx skillsauth add lucianghinda/superpowers-ruby hwc-realtime-streamingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Implement push-driven Hotwire behavior with Turbo Streams and Stimulus.
append/prepend/replace/update/remove/before/after/refresh before custom actions.Open only the file needed for the current request.
references/2023-08-01-turbo-streams-inline-stream-tags.mdreferences/2023-08-15-turbo-streams-custom-stream-actions.mdreferences/2023-10-10-turbo-streams-custom-stream-actions-video-playlist-management.mdreferences/2024-01-30-turbo-streams-custom-stream-actions-localstorage.mdreferences/2025-06-10-turbo-streams-list-animation-view-transitions.mdreferences/2024-03-12-hotwire-combobox-with-real-time-data.mdreferences/2023-11-21-stimulus-inter-tab-communication.mdUse references/INDEX.md for the full catalog.
hwc-navigation-contenthwc-forms-validationhwc-media-contenthwc-ux-feedbackhwc-stimulus-fundamentalsdevelopment
Use when writing, reviewing, or debugging pure Ruby code — idiomatic patterns, modern 3.x+ features (pattern matching, Data.define, endless methods), error handling conventions (raise vs fail, result objects), memoization, and performance idioms. For Rails use rails-guides. For testing use minitest. For code style use sandi-metz-rules.
testing
Official Rails documentation. Use when asked about any Rails-specific topic including ActiveRecord, routing, controllers, views, mailers, jobs, Action Cable, Action Text, Active Storage, migrations, validations, callbacks, associations, caching, security, or internals.
tools
--- name: ruby-upgrade description: Use when upgrading the Ruby interpreter version of a Bundler/Rails app — especially "upgrade to Ruby 4", "bump Ruby to 4.0", "audit Ruby 4 compatibility", "what breaks on Ruby 4", or a specific target like "Ruby 4.0.5". Triggers on Ruby-major risk symptoms: CGI.parse/CGI::Cookie removal, Net::HTTP implicit Content-Type dropped, demoted default gems (ostruct/logger/benchmark/irb), SortedSet, Set#inspect changes, native-extension recompile crashes, openssl 4 pin
development
Use when stuck after multiple debug attempts and want to escalate to a stronger one-shot model (GPT-5 Pro, Opus, Gemini Pro) — packages a self-contained "oracle prompt" with Ruby/Rails project briefing, verbatim error, what-was-tried, constraints, and just-enough attached files. Triggers include "ask the oracle", "write a letter to GPT-5", "I'm stuck, draft a prompt for another model", "/tmp/letter.md".