CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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 tight, well-organized overview that routes Claude to the right reference per request and escalates overlapping domains correctly. Execution-level detail lives appropriately in the reference files rather than inline.

Suggestions

Add a brief validate→fix→retry loop around the final verification step so workflow_clarity reaches the top anchor.

Include one minimal inline code snippet (e.g. a Turbo Frame busy spinner) so the skill is immediately actionable without opening a reference first.

DimensionReasoningScore

Conciseness

The body is lean: a numbered workflow, terse guardrails, a selective reference list, and escalation routing — every line earns its place with no padding or explanation of concepts Claude already knows.

5 / 5

Actionability

As an instruction-only routing skill it names concrete Turbo semantics (busy, progress bar hooks, submit/render lifecycle events) and points to specific reference files, but copy-paste-ready patterns are deferred to those references rather than shown inline.

4 / 5

Workflow Clarity

The 5-step Core Workflow is clearly sequenced and ends with a verification checkpoint ("Verify UX behavior on slow network, back/forward cache restores, and submission failures"), though there is no explicit validate→fix→retry feedback loop.

4 / 5

Progressive Disclosure

SKILL.md is a clean overview with one-level-deep, well-signaled references — each cited file is real, described inline, and INDEX.md provides the full catalog — making navigation easy.

5 / 5

Total

18

/

20

Passed

Description

92%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 pairs concrete capabilities with explicit use-when guidance and clear neighbor-skill routing. The only minor gap is a few natural trigger synonyms a user might voice.

Suggestions

Add one or two common synonyms a user might say, such as "spinners" or "skeleton screens", to broaden natural trigger coverage.

Consider naming Hotwire/Turbo in the trigger clause itself ("Use when adding perceived-performance feedback to Hotwire/Turbo apps") so users who mention Turbo by name match it.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete capabilities — "loading states, busy indicators, progress bars, optimistic UI, render interception, and view/page transitions" — giving comprehensive coverage of the cross-cutting UX feedback domain rather than vague abstractions.

5 / 5

Completeness

It explicitly states what ("Implement cross-cutting Hotwire UX feedback patterns: ...") and when ("Prefer this skill when the core goal is perceived performance and user feedback"), answering both with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural user-facing terms like "loading states", "progress bars", "optimistic UI", "perceived performance", and "user feedback" are present with synonyms (view/page transitions), but a few common phrasings (e.g. "spinner", "skeleton") a user might say are absent.

4 / 5

Distinctiveness Conflict Risk

The skill carves a clear cross-cutting niche and explicitly routes five overlapping domains to neighbor skills (hwc-forms-validation, hwc-navigation-content, etc.), minimizing wrong-skill triggering.

5 / 5

Total

19

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
lucianghinda/superpowers-ruby
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.