hwc-stimulus-fundamentals
Cover Stimulus controller fundamentals: lifecycle hooks, values and valueChanged callbacks, targets and target callbacks, outlets, action parameters, keyboard events, and controller architecture patterns. Prefer this skill when the request is primarily about Stimulus APIs and controller design independent of a specific Hotwire domain. Use hwc-forms-validation for form-specific workflows, hwc-navigation-content for Turbo navigation concerns, hwc-realtime-streaming for Turbo Streams/WebSocket patterns, hwc-media-content for media integrations, and hwc-ux-feedback for loading/progress/transition UX patterns.
89
86%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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 clearly defines its scope around Stimulus controller fundamentals with specific API concepts listed. It excels at completeness by providing both 'what' and 'when' guidance, and goes further by explicitly delineating boundaries with five related skills, making it highly distinctive. The trigger terms are natural and comprehensive for developers working with the Stimulus framework.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and concepts: lifecycle hooks, values and valueChanged callbacks, targets and target callbacks, outlets, action parameters, keyboard events, and controller architecture patterns. | 3 / 3 |
Completeness | Clearly answers both 'what' (Stimulus controller fundamentals with specific topics listed) and 'when' ('Prefer this skill when the request is primarily about Stimulus APIs and controller design independent of a specific Hotwire domain'). Also explicitly delineates boundaries by naming other skills for adjacent concerns. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Stimulus controller', 'lifecycle hooks', 'values', 'valueChanged', 'targets', 'outlets', 'action parameters', 'keyboard events', 'controller architecture'. These are the exact terms a developer working with Stimulus would use. | 3 / 3 |
Distinctiveness Conflict Risk | Exceptionally distinctive — not only defines its own clear niche (Stimulus APIs and controller design), but explicitly names five sibling skills and when to use them instead, greatly reducing conflict risk. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is well-organized, concise, and demonstrates excellent progressive disclosure with clear references and neighbor skill escalation. Its main weakness is the lack of any concrete code examples—for a skill about Stimulus controller fundamentals, at least one executable controller snippet would make the guidance significantly more actionable. The workflow is principled but could benefit from explicit validation checkpoints.
Suggestions
Add at least one minimal but complete Stimulus controller code example demonstrating the core patterns (lifecycle hooks, values, targets, actions) to improve actionability.
Include a concrete validation step in the workflow, such as verifying controller connection in the browser console or checking that value callbacks fire as expected.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line serves a purpose. No unnecessary explanations of what Stimulus is or how controllers work in general. The content assumes Claude already knows the framework and focuses on decision rules and constraints. | 3 / 3 |
Actionability | The guidance is specific in terms of principles and guardrails (e.g., 'Guard callbacks that can run before connect() completes'), but lacks any concrete code examples or executable snippets. For a controller fundamentals skill, at least one minimal controller example showing the patterns would significantly improve actionability. | 2 / 3 |
Workflow Clarity | The core workflow provides a reasonable sequence for designing a controller, but it reads more like a checklist of principles than a step-by-step process with validation checkpoints. There are no explicit verification steps or feedback loops for catching errors during controller implementation. | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise overview, clearly signaled one-level-deep references to specific topic files, an index file for the full catalog, and well-organized escalation to neighbor skills. Navigation is intuitive and references are selective. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- lucianghinda/superpowers-ruby
- Commit
cb03f92
- 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.