Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add zarpay/rails-template --skill hwc-ux-feedbackgit clone --depth 1 https://github.com/zarpay/rails-templateWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/zarpay/rails-template/hwc-ux-feedback)<a href="https://agentmods.dev/skills/zarpay/rails-template/hwc-ux-feedback"><img src="https://agentmods.dev/badge/skills/zarpay/rails-template/hwc-ux-feedback/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/zarpay/rails-template/hwc-ux-feedback"><img src="https://agentmods.dev/badge/skills/zarpay/rails-template/hwc-ux-feedback.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00119 | $0.00589 |
| Opus 5 | $0.00060 | $0.00295 |
| Sonnet 5 | $0.00024 | $0.00118 |
| Haiku 4.5 | $0.00012 | $0.00059 |
Grade A, and why
hwc-ux-feedback scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
100% identical to hwc-ux-feedback — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Experience & Feedback
Implement cross-cutting feedback and perceived-performance patterns in Hotwire.
Core Workflow
- Identify feedback need: loading, submit activity, progress reporting, optimistic updates, or transitions.
- Prefer built-in Turbo semantics first (
busy, progress bar hooks, submit/render lifecycle events). - Add optimistic updates only with a clear reconciliation strategy.
- Keep transition logic bounded to explicit lifecycle events and cache/preview-safe paths.
- Verify UX behavior on slow network, back/forward cache restores, and submission failures.
Guardrails
- Do not use fixed timeouts as a proxy for network or render completion.
- Gate animations/transitions for previews and cache restores.
- Keep submit locking/unlocking symmetric between start and end events.
- Separate UX feedback logic from domain-specific form/media/navigation implementations.
Load References Selectively
Open only the file needed for the current request.
- Turbo progress bar reuse:
references/2023-07-18-turbo-drive-progress-bar.md - Form activity indicators:
references/2023-06-06-turbo-drive-form-activity-indicators.md - Render interception and page transitions:
references/2023-04-25-turbo-drive-render-interception.md - Swiper-like transition behavior:
references/2024-11-19-turbo-drive-swiper-view-transitions.md - Frame busy spinner patterns:
references/2026-01-20-turbo-frames-loading-spinner.md - Optimistic UI with Turbo morph reconciliation:
references/2024-03-26-optimistic-ui-with-turbo-8-morphs.md - ULID-based optimistic identity strategy:
references/2024-08-13-turbo-drive-ulid.md
Use references/INDEX.md for the full catalog.
Escalate to Neighbor Skills
- Form validation and submit correctness concerns: use
hwc-forms-validation - Navigation/history/cache flow concerns: use
hwc-navigation-content - Real-time push updates and stream actions: use
hwc-realtime-streaming - Media-specific playback/upload concerns: use
hwc-media-content - General Stimulus API/controller fundamentals: use
hwc-stimulus-fundamentals
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/2023-04-25-turbo-drive-render-interception.md 2.8 KB
- references/2023-06-06-turbo-drive-form-activity-indicators.md 3.5 KB
- references/2023-07-18-turbo-drive-progress-bar.md 5.2 KB
- references/2024-03-26-optimistic-ui-with-turbo-8-morphs.md 5.3 KB
- references/2024-08-13-turbo-drive-ulid.md 2.8 KB
- references/2024-11-19-turbo-drive-swiper-view-transitions.md 2.8 KB
- references/2026-01-20-turbo-frames-loading-spinner.md 5.4 KB
- references/INDEX.md 1.3 KB
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 47 lines · 119 tokens per session scan A d8ee23667e92
hwc-ux-feedback is a skill published in the GitHub repository zarpay/rails-template (9 stars, last pushed 28d ago), licensed MIT. It adds 119 tokens to every session and 589 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to hwc-ux-feedback, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
waitlist-page
A simple waitlist page for collecting email addresses from people interested in a new product or early-access release.
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.