webhook-dashboard-ux-maintainer

Maintain dashboard UX with ARIA attributes and debounced autosave flows.

Updated May 18, 2025
One-click install
npx skills add https://github.com/ki2pixel/render_signal_server --skill webhook-dashboard-ux-maintainer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: webhook-dashboard-ux-maintainer
Source: https://github.com/ki2pixel/render_signal_server/tree/main/.windsurf/skills/webhook-dashboard-ux-maintainer
Command: npx skills add https://github.com/ki2pixel/render_signal_server --skill webhook-dashboard-ux-maintainer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps the dashboard UI accessible, stable, and coherent during iterative changes to prevent UX regressions and ensure consistent behavior.

Core Features & Use Cases

  • Enforces WCAG-compliant UI patterns (ARIA roles, keyboard focus visibility, and responsive layouts) across dashboard components.
  • Supports autosave flows with visible status indicators and debounce to prevent data loss during edits.
  • Provides clear guidelines for modular ES6 frontend components (status banners, timeline, routing rules builder) to streamline maintenance.
  • Includes workflow references for manual testing and documentation updates in Memory Bank.

Quick Start

Update the dashboard UI following the workflow and verify ARIA attributes, autosave debounce, and test coverage.

Frequently Asked Questions about webhook-dashboard-ux-maintainer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain WCAG accessibility compliance when updating dashboard frontend components?

To maintain WCAG compliance in dashboard frontend components, apply ARIA roles, ensure keyboard focus visibility, and verify responsive layouts across status banners, timelines, and routing rules builders during UI updates.

How do I implement autosave in a frontend dashboard without losing data during edits?

Implement autosave in frontend dashboards using debounced save behavior combined with visible status indicators, preventing data loss during edits and ensuring reliable, testable UI performance.

What is the best way to structure modular ES6 dashboard components for UX maintenance?

Structure modular ES6 dashboard components by following clear guidelines for status banners, timelines, webhooks panels, and routing rules builders to streamline maintenance and ensure coherent behavior during iterative changes.

Why does my dashboard UX regress after iterative frontend updates?

Dashboard UX regresses after iterative updates when accessibility patterns and autosave flows are not consistently enforced, causing misaligned ARIA attributes and broken debounced save behavior across modified components.

Do I need manual testing workflows to verify dashboard ARIA attributes and autosave debounce?

Yes, you need manual testing workflows referenced in Memory Bank documentation to verify ARIA attributes, autosave debounce behavior, and test coverage after updating dashboard UI modules.