hwc-forms-validation

Handle Hotwire form workflows: form submission lifecycle, inline editing, validation errors, typeahead/autocomplete, modal forms, and external form controls. Prefer this skill when the core problem is correctness and UX of form interaction. Use hwc-navigation-content for pagination/tabs/filter navigation, hwc-realtime-streaming for WebSocket/Turbo Stream broadcasting, hwc-media-content for image/video/audio behavior, hwc-ux-feedback for generic loading/transition polish, and hwc-stimulus-fundamentals for framework-level Stimulus APIs not tied to forms.

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 instruction-only skill: a concrete 5-step workflow with a validation checkpoint, terse guardrails, and exemplary progressive disclosure to verified reference files. The only gaps are an under-specified context-preservation step and a missing explicit validation-retry feedback loop.

Suggestions

Expand step 5 ("Preserve user context during rerenders") with a concrete method, e.g. a Stimulus pattern or specific DOM focus/selection-restoration technique, so the guidance is executable rather than a hint.

Add an explicit validation-retry feedback loop, e.g. "If 422, the frame rerenders with errors; fix inputs and resubmit — do not redirect," to lift workflow clarity to a full checkpoint loop.

Consider one tiny inline snippet showing the 422/303 controller response shape so the most common case is copy-paste ready.

Dimension	Reasoning	Score
Conciseness	Lean body that assumes Claude's competence — never explains what Turbo Frames or Stimulus are — with every section (workflow, guardrails, references, escalation) earning its tokens.	5 / 5
Actionability	Concrete, executable specifics like "Return 422 for validation failures and 303 for successful redirects", "turbo:submit-end", and the HTML "form" attribute, but step 5 ("Preserve user context during rerenders (focus/caret/selection)") stays a high-level hint without an implementation method.	4 / 5
Workflow Clarity	A clear 5-step sequenced workflow with a validation checkpoint (the 422 rerender step), but no explicit error-recovery feedback loop spelling out how to handle and resubmit a failed validation.	4 / 5
Progressive Disclosure	Clear overview with a dedicated "Load References Selectively" section mapping each topic to a specific one-level-deep file plus an INDEX.md catalog; all six referenced files plus INDEX.md are present on disk.	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.

The description is exemplary: it names a comprehensive set of concrete form-handling capabilities, provides an explicit trigger clause, includes synonym coverage, and demarcates boundaries against five neighbor skills. No vague fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists six concrete actions — "form submission lifecycle, inline editing, validation errors, typeahead/autocomplete, modal forms, and external form controls" — giving comprehensive coverage rather than just several.	5 / 5
Completeness	Explicitly answers both what ("Handle Hotwire form workflows: ...") and when ("Prefer this skill when the core problem is correctness and UX of form interaction") with a concrete trigger phrase.	5 / 5
Trigger Term Quality	Covers natural terms users would say ("form submission", "inline editing", "validation errors", "modal forms") plus synonyms ("typeahead/autocomplete"), matching the comprehensive-synonym anchor.	5 / 5
Distinctiveness Conflict Risk	Carves a clear form-correctness/UX niche and explicitly routes adjacent concerns to five named neighbor skills (e.g. "Use hwc-navigation-content for pagination/tabs/filter navigation"), minimizing conflict risk.	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-forms-validation/SKILL.md
Commit: 99fac3d

Reviewed: 6 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.