hotwire-patterns
Implements Hotwire patterns with Turbo Frames, Turbo Streams, and Stimulus controllers. Use when building interactive UIs, real-time updates, form handling, partial page updates, or when user mentions Turbo, Stimulus, or Hotwire.
Install with Tessl CLI
npx tessl i github:fernandezbaptiste/rails_ai_agents --skill hotwire-patterns94
Does it follow best practices?
Validation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that follows best practices. It uses third person voice, lists specific technologies and capabilities, includes an explicit 'Use when...' clause with both functional triggers (interactive UIs, real-time updates) and keyword triggers (Turbo, Stimulus, Hotwire). The description is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Turbo Frames, Turbo Streams, and Stimulus controllers' along with specific use cases like 'interactive UIs, real-time updates, form handling, partial page updates'. | 3 / 3 |
Completeness | Clearly answers both what ('Implements Hotwire patterns with Turbo Frames, Turbo Streams, and Stimulus controllers') and when ('Use when building interactive UIs, real-time updates, form handling, partial page updates, or when user mentions Turbo, Stimulus, or Hotwire'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Turbo', 'Stimulus', 'Hotwire', 'interactive UIs', 'real-time updates', 'form handling', 'partial page updates' - these are all terms developers naturally use when working with this technology. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche targeting the Hotwire/Turbo/Stimulus ecosystem specifically. The technology-specific terms (Turbo Frames, Turbo Streams, Stimulus) create distinct triggers unlikely to conflict with generic JavaScript or other frontend framework skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that efficiently covers Hotwire patterns with excellent actionability through complete, executable code examples. The decision tables for pattern selection are particularly valuable. The main weakness is the workflow checklist lacks explicit validation steps and error recovery guidance for debugging common issues.
Suggestions
Enhance the workflow checklist with explicit validation steps, e.g., 'Verify frame ID matches in browser DevTools before proceeding' after the markup step
Add a troubleshooting workflow that sequences the debugging tips into a diagnostic process with specific commands to run
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables for quick reference, minimal prose, and assuming Claude understands Rails/JavaScript fundamentals. No unnecessary explanations of what Hotwire is beyond the one-line definition. | 3 / 3 |
Actionability | Provides fully executable ERB, Ruby, and JavaScript code examples that are copy-paste ready. Includes complete controller code, view templates, and test specs with realistic implementations. | 3 / 3 |
Workflow Clarity | Includes a workflow checklist which is helpful, but lacks explicit validation checkpoints or feedback loops. The checklist is more of a reminder than a sequenced process with error recovery steps. | 2 / 3 |
Progressive Disclosure | Well-structured with clear overview, quick start, decision tables, and explicit references to detailed documentation (turbo-frames.md, turbo-streams.md, stimulus.md). Content is appropriately split with one-level-deep navigation. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.