hotwire
Hotwire, Turbo & Stimulus for Rails
Expert patterns for JavaScript and Hotwire integration with Ruby on Rails.
Core Principles
- Use latest versions based on Gemfile
- Follow Rails conventions and best practices
- Use Context7 MCP or hotwire.dev for documentation
- Test JavaScript with RSpec system specs (Capybara + Cuprite)
- Review existing Stimulus controllers before creating new ones
Stimulus Controllers
Guidelines
- Keep controllers simple and focused
- Make controllers generic when possible, specific only when needed
- Never have controllers communicate with each other
- Integrate into ERB templates using Rails conventions
More from aviflombaum/claude-code-in-avinyc
ux-ui
UX/UI design principles for clean, intuitive interfaces. Use when designing layouts, improving usability, planning information architecture, or ensuring accessibility. Triggers on "user experience", "usability", "information architecture", "accessibility", "interaction design".
12interview
Interview about a plan file to refine it through in-depth questioning. Use when you have a plan that needs validation, refinement, or deeper exploration before implementation. Triggers on "interview me about", "refine this plan", "question this spec".
9tailwind
Tailwind CSS patterns, utilities, and component styling for Rails. Use when styling with Tailwind, creating responsive layouts, or building UI components. Triggers on "tailwind", "style with", "css classes", "responsive layout".
9write
Write technical blog posts, tutorials, and documentation in Flatiron School's engaging style. Use for explaining code patterns, debugging stories, or turning complex topics into clear narratives. Triggers on "write a blog post", "tutorial about", "explain how", "technical writing".
8write-test
Writes comprehensive RSpec tests for Rails applications. Use when writing model specs, request specs, system specs, job specs, mailer specs, channel specs, or storage specs. Triggers on "write tests for", "add specs to", "test the User model", "create request specs", "write RSpec", "add test coverage".
8analyze
Analyze completed development work to identify automation and systematization opportunities. Use after finishing features, fixing bugs, or completing code reviews. Triggers on "analyze for automation", "what can we automate", "compound opportunities", "systematize".
8