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.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, token-efficient overview body that sequences the core workflow with a validation checkpoint and defers detail to clearly labeled, real reference files. The only gap is the absence of any inline executable code in the body itself.

Suggestions

Add one small inline Turbo Frame snippet (e.g. a frame with src and data-turbo-action) so the body demonstrates the concrete pattern before delegating to references.

Turn step 5 into an explicit validate→fix→retry feedback loop so destructive/batch navigation edge cases have a recovery path.

Show the canonical filter/pagination URL-state pattern inline to lift actionability from concrete API names toward copy-paste-ready guidance.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding of concepts Claude already knows (no "what is Turbo Drive" exposition); every line is actionable guidance or a reference pointer, matching the level-5 lean/efficient anchor.	5 / 5
Actionability	Names concrete APIs and attributes ("data-turbo-action", frame "src", "visit events") and routes each scenario to a specific reference file, but provides no inline executable code — deferring implementation to references. This fits level 4 (mostly actionable, minor gaps) rather than 5 (copy-paste code) and above 3 (no missing key details).	4 / 5
Workflow Clarity	A clear 5-step sequence ends with an explicit validation checkpoint ("Validate behavior across forward/back navigation and refresh paths"), fitting level 4; not 5 because there is no error-recovery feedback loop or checklist, and not 3 because validation is present rather than absent.	4 / 5
Progressive Disclosure	The body is a concise overview with nine one-level-deep references, each clearly labeled by use case (e.g. "Tabbed frame navigation: references/...") and all verified to exist, plus an INDEX.md pointer — matching the level-5 well-signaled one-level-deep anchor.	5 / 5
	Total	18 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that concisely states concrete capabilities, an explicit use-when trigger, and clear boundary routing to five neighbor skills. Coverage is comprehensive and conflict risk is low.

Dimension	Reasoning	Score
Specificity	Lists seven concrete actions ("Turbo Frame pagination, tabbed navigation, lazy loading, faceted filtering/search, cache lifecycle, scroll restoration, and visit/render control") — comprehensive coverage of the navigation/content domain, matching the level-5 anchor rather than the minor-gaps level 4.	5 / 5
Completeness	Explicitly states both what ("Build Hotwire navigation and content-discovery flows: ...") and when ("Prefer this skill when the core problem is request/response navigation state and browser history behavior") with concrete trigger phrases, hitting the level-5 anchor; not 4 because both halves are specific rather than vague.	5 / 5
Trigger Term Quality	Natural terms a Hotwire/Rails user would say appear with synonyms ("pagination", "tabbed navigation", "lazy loading", "faceted filtering/search", "scroll restoration", "browser history", "WebSocket/Turbo Stream push updates"), matching the comprehensive level-5 anchor.	5 / 5
Distinctiveness Conflict Risk	A clear Hotwire navigation niche plus explicit neighbor-skill routing ("Use hwc-forms-validation for ...", "hwc-realtime-streaming for ...") actively minimizes conflict risk, matching the level-5 distinct-triggers anchor.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: lucianghinda/superpowers-ruby
Path: skills/hwc-navigation-content/SKILL.md
Commit: 99fac3d

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

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.