thoughtbot / thoughtbot/guides
Rails AI rules could benefit from Hotwire rules
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 9.6k
- Forks
- 1.3k
- PR merge metrics
- No merged PRs in 30d
Description
The Rails AI rules seem to work pretty well from my testing. I feel there is currently a gap in the Hotwire area that would benefit from some guidance and best practices.
There are two parts to Hotwire
- Turbo (Drive, Frames, Streams, Morph)
- Stimulus (a modest JavaScript framework "designed to augment your HTML with just enough behavior to make it shine")
This is a holding issue to gather what we've seen from AI that it doesn't do well / needs some guidance in regards to Hotwire.
In time we might find a separate rule for each (Turbo and Stimulus) is useful, but perhaps to start we can combine into a single Hotwire rules file as they are closely related.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing rails/ai-rules/CLAUDE.md and collecting the reported gaps in AI guidance for Turbo and Stimulus. Done means the gathered examples have been turned into agreed Hotwire rules, either as one combined file or separate Turbo and Stimulus rules.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, rails
- Domain
- documentation, frontend
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100