hwc-navigation-content
Build Hotwire navigation and content-discovery flows: Turbo Frame pagination, tabbed navigation, lazy loading, faceted filtering/search, cache lifecycle, scroll restoration, and visit/render control. Prefer this skill when the core problem is request/response navigation state and browser history behavior. Use hwc-forms-validation for form validation and inline edit flows, hwc-realtime-streaming for WebSocket/Turbo Stream push updates, hwc-media-content for image/video/audio features, hwc-ux-feedback for generic loading/progress/transition polish, and hwc-stimulus-fundamentals for Stimulus APIs not centered on navigation.
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 with specific concrete actions, includes natural trigger terms developers would use, explicitly states when to prefer it, and proactively disambiguates from related skills. The boundary-drawing with sibling skills is particularly strong and reduces conflict risk significantly. The description uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: Turbo Frame pagination, tabbed navigation, lazy loading, faceted filtering/search, cache lifecycle, scroll restoration, and visit/render control. These are all concrete, well-defined capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (Turbo Frame pagination, tabbed navigation, lazy loading, etc.) and 'when' ('Prefer this skill when the core problem is request/response navigation state and browser history behavior'). It also explicitly delineates boundaries by naming related skills for adjacent concerns. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'pagination', 'tabbed navigation', 'lazy loading', 'faceted filtering', 'search', 'scroll restoration', 'browser history', 'Turbo Frame', 'Hotwire'. These cover a wide range of terms a developer would naturally use when seeking help with navigation flows. | 3 / 3 |
Distinctiveness Conflict Risk | Exceptionally distinctive — it explicitly names five sibling skills and explains when to use each one instead, creating very clear boundaries. The focus on 'request/response navigation state and browser history behavior' carves out a precise niche unlikely to conflict with other skills. | 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 is a well-structured orchestration skill that excels at conciseness and progressive disclosure—it serves as an effective routing layer to detailed reference files and neighbor skills. Its main weakness is the lack of concrete, executable code examples in the body itself; the actionability depends entirely on the referenced files. The workflow is reasonable but could benefit from more explicit validation checkpoints or feedback loops.
Suggestions
Add at least one concrete code example in the body (e.g., a minimal Turbo Frame tab navigation snippet with the correct data attributes and event listener) to improve actionability without relying solely on references.
Integrate a validation checkpoint into the core workflow (e.g., after step 3: 'Verify: navigate forward/back and confirm URL, frame content, and active state all update correctly') to strengthen the feedback loop.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line earns its place. No unnecessary explanations of what Turbo Drive or Turbo Frames are—assumes Claude already knows the framework. The guardrails are terse but meaningful, and the reference list is compact with clear one-line descriptions. | 3 / 3 |
Actionability | The workflow and guardrails provide specific conceptual guidance (e.g., 'update active state on load/render events, not click intent events'), but there are no concrete code examples, executable snippets, or specific attribute/event names beyond brief mentions like `data-turbo-action`. The actionability relies entirely on the referenced files. | 2 / 3 |
Workflow Clarity | The 5-step core workflow provides a reasonable sequence for approaching navigation tasks, and step 5 mentions validation across navigation paths. However, there are no explicit validation checkpoints or feedback loops within the workflow itself—validation is mentioned as a final step rather than integrated with error recovery. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure: a concise overview with clearly signaled, one-level-deep references to specific topic files. Each reference is labeled by use case, and there's a clear instruction to open only the relevant file. Neighbor skill escalation paths are also well-organized. | 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.