hwc-ux-feedback
Implement cross-cutting Hotwire UX feedback patterns: loading states, busy indicators, progress bars, optimistic UI, render interception, and view/page transitions. Prefer this skill when the core goal is perceived performance and user feedback, independent of a single feature domain. Use hwc-forms-validation for form correctness and validation behavior, hwc-navigation-content for navigation/history/cache mechanics, hwc-realtime-streaming for push/stream orchestration, hwc-media-content for media-specific behavior, and hwc-stimulus-fundamentals for base Stimulus API questions.
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 (Hotwire UX feedback patterns), lists specific concrete capabilities, provides explicit trigger guidance for when to use it, and proactively disambiguates from five related skills. The description is well-structured, uses third-person voice, and balances comprehensiveness with clarity. It serves as a strong example of how to write a description within a large skill ecosystem.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: loading states, busy indicators, progress bars, optimistic UI, render interception, and view/page transitions. These are clearly defined, actionable UX patterns rather than vague abstractions. | 3 / 3 |
Completeness | Clearly answers both 'what' (cross-cutting Hotwire UX feedback patterns with specific examples) and 'when' ('Prefer this skill when the core goal is perceived performance and user feedback, independent of a single feature domain'). Also explicitly delineates boundaries by naming related skills to use instead for adjacent concerns. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'loading states', 'busy indicators', 'progress bars', 'optimistic UI', 'view transitions', 'page transitions', 'perceived performance', 'user feedback'. These are terms developers naturally use when seeking help with these patterns. | 3 / 3 |
Distinctiveness Conflict Risk | Exceptionally distinctive — explicitly differentiates itself from five related skills (hwc-forms-validation, hwc-navigation-content, hwc-realtime-streaming, hwc-media-content, hwc-stimulus-fundamentals) with clear boundary descriptions for each, making conflict very unlikely. | 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-structured as a routing/overview document with excellent progressive disclosure and conciseness. Its main weakness is the lack of any inline concrete code examples or executable snippets—all actionable detail is deferred to reference files. The workflow is reasonable but could benefit from explicit validation checkpoints rather than a single final verification step.
Suggestions
Add at least one or two inline code/markup examples for the most common patterns (e.g., a Turbo busy attribute usage or a progress bar hook) so the skill is actionable without opening a reference file.
Integrate validation checkpoints into the workflow steps (e.g., after step 3, 'Verify optimistic state reverts correctly on server error') rather than deferring all verification to the final step.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is lean and purposeful. No unnecessary explanations of what Hotwire/Turbo is or how it works—assumes Claude's competence. Guardrails and workflow steps are terse but informative. | 3 / 3 |
Actionability | The workflow and guardrails provide clear directional guidance (e.g., 'prefer built-in Turbo semantics first', 'keep submit locking/unlocking symmetric'), but there are no concrete code examples, commands, or copy-paste-ready snippets. The actionability relies entirely on the referenced files, which is a delegation rather than inline instruction. | 2 / 3 |
Workflow Clarity | The 5-step core workflow provides a reasonable sequence, and step 5 mentions verification scenarios (slow network, back/forward cache, submission failures). However, there are no explicit validation checkpoints or feedback loops for error recovery—verification is listed as a final step rather than integrated with checkpoints throughout. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure: a concise overview with clearly signaled, one-level-deep references to specific topic files. The 'Load References Selectively' section with explicit file paths and the 'Escalate to Neighbor Skills' section provide clear navigation without nesting. | 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.