Dashboard Visible-State Regressions

Identify and validate visible-state regressions in dashboard UI across routes and HTMX swaps.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/JDL440/nfl-eval --skill dashboard-visible-state-regressions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Dashboard Visible-State Regressions
Source: https://github.com/JDL440/nfl-eval/tree/main/.squad/skills/dashboard-visible-state-regressions
Command: npx skills add https://github.com/JDL440/nfl-eval --skill dashboard-visible-state-regressions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dashboard teams struggle to identify and pin down visible-state regressions when UI surfaces are added, removed, or swapped via HTMX, causing flaky test outcomes and misaligned dashboards.

Core Features & Use Cases

  • Identify when UI elements change visibility, order, or presence across routes and states.
  • Differentiate intentional surface changes from regression-related changes to maintain reliable dashboards.
  • Preserve operator-visible test seams and provide guidance for maintaining stable rendering in production.

Quick Start

Review the current dashboard render across key routes and confirm visible elements match the approved shell to stabilize tests.

Frequently Asked Questions about Dashboard Visible-State Regressions

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

FAQPage Schema
How do I fix flaky dashboard UI tests caused by HTMX swaps?

Fix flaky dashboard UI tests caused by HTMX swaps by inspecting render shells and asserting stable IDs and badges, which differentiates intentional surface changes from actual regressions.

What is a visible-state regression in an HTMX dashboard?

A visible-state regression occurs when dashboard UI elements change visibility, order, or presence across routes and states due to HTMX partial renders, causing misaligned dashboards and unreliable test outcomes.

How do I test dashboard UI elements across different routes and states?

Test dashboard UI elements across routes and states by reviewing the current render against the approved shell, inspecting render shells, and documenting expected state banners to guide reliable tests.

How do I document expected state banners for dashboard regression testing?

Document expected state banners by codifying how to inspect render shells and assert stable IDs and badges, ensuring operator-visible test seams are preserved for reliable dashboard rendering in production.

Can I use this approach to differentiate intentional UI changes from regressions?

Yes, you can differentiate intentional surface changes from regression-related changes by validating visible-state regressions and confirming visible elements match the approved render shell across key routes.

Why do my dashboard partial renders cause misaligned UI surfaces?

Dashboard partial renders cause misaligned UI surfaces when HTMX swaps alter the visibility, order, or presence of elements, leading to flaky test outcomes that require stable ID assertions to resolve.