stimulus-agent

Create accessible Stimulus controllers with JSDoc for Turbo Rails applications.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/reckerswartz/resume_builder --skill stimulus-agent-reckerswartz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stimulus-agent
Source: https://github.com/reckerswartz/resume_builder/tree/main/.windsurf/skills/stimulus-agent
Command: npx skills add https://github.com/reckerswartz/resume_builder --skill stimulus-agent-reckerswartz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Stimulus controllers can become verbose and hard to maintain without a consistent pattern and clear documentation. This Skill provides a framework for generating clean, accessible Stimulus controllers that follow conventions, include JSDoc-style comments, and integrate smoothly with Turbo and ViewComponents.

Core Features & Use Cases

  • Create and document Stimulus controllers with targets, values, and actions.
  • Ensure accessibility (ARIA, keyboard navigation) and progressive enhancement.
  • Integrate controllers with Turbo streams and Rails components for robust UI behavior.

Quick Start

Create an accessible Stimulus controller following the conventions in this Skill to add interactive behavior to a Rails + Turbo app.

Frequently Asked Questions about stimulus-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create accessible Stimulus controllers for a Rails application?

To create accessible Stimulus controllers, you need a consistent pattern that incorporates ARIA attributes, keyboard navigation, and JSDoc-style comments. This approach ensures your Stimulus controllers maintain accessibility standards while integrating smoothly with Rails.

How do I integrate Stimulus controllers with Turbo streams in Hotwire?

Integrating Stimulus controllers with Turbo streams involves defining clear targets, values, and actions within your controller logic. This ensures robust UI behavior and seamless communication between Turbo Rails updates and your client-side Stimulus components.

What is the best way to document Stimulus controller targets and actions?

The best way to document Stimulus controller targets and actions is using JSDoc-style comments. Documenting your controllers this way satisfies convention requirements, clarifies component integrations, and makes complex Stimulus logic easier to maintain.

Does this approach to building Stimulus controllers support progressive enhancement?

Yes, building Stimulus controllers with this pattern supports progressive enhancement. It ensures accessible markup and keyboard navigation are layered on top of standard Rails views, providing a robust UI experience even before JavaScript fully loads.

Why do my Stimulus controllers become hard to maintain in larger Rails apps?

Stimulus controllers become hard to maintain when they lack a consistent pattern and clear JSDoc documentation. Applying a standardized framework for targets, values, and actions prevents verbose code and simplifies long-term maintenance.

Can I use Stimulus controllers with Rails ViewComponents?

Yes, you can use Stimulus controllers with Rails ViewComponents. This combination allows you to build encapsulated, accessible UI components that integrate smoothly with Turbo streams and follow strict Stimulus conventions.