skills.rest
Luqman-Ud-Din
Luqman-Ud-DinCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

qa-detect-loading

Detect persistent loading states, blank pages, and SPA error content after navigation.

Updated May 22, 2026
Search Tags:#loading#spinner#spa routing#browser qa#404 detection#blank page
One-click install
npx skills add https://github.com/Luqman-Ud-Din/blackbox-qa-agent --skill qa-detect-loading
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-detect-loading
Source: https://github.com/Luqman-Ud-Din/blackbox-qa-agent/tree/main/skills/qa-detect-loading
Command: npx skills add https://github.com/Luqman-Ud-Din/blackbox-qa-agent --skill qa-detect-loading

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill finds pages that appear to load successfully but still hide broken experiences such as stuck spinners, empty screens, or SPA routes that render 404/error content.

Core Features & Use Cases

  • Stuck loading detection: Flags spinners, skeletons, progress bars, and other loading indicators that remain visible after the page should be settled.
  • Blank page detection: Identifies routes that render almost no visible text, helping catch broken navigation or failed rendering.
  • Error-content detection: Detects 404 and similar error states that appear even when the HTTP response was successful.
  • Use case: A route returns 200 but the app shows a “Not Found” screen or never dismisses its loader; this Skill surfaces the defect immediately for QA triage.

Quick Start

Use the qa-detect-loading skill to inspect the current page for persistent loading states, blank content, and SPA error screens after navigation.

Frequently Asked Questions about qa-detect-loading

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

FAQPage Schema
How do I detect stuck loading spinners and blank screens in an SPA?▼

Yes, a route can return a 200 response but still render a 404 error screen, which requires inspecting the DOM for error-pattern matches after navigation completes rather than relying on HTTP status codes.

How do I check for blank pages after SPA routing completes?▼

To check for blank pages after SPA routing, inspect the DOM after a wait period to measure body text length, identifying routes that render almost no visible text and catching failed rendering.

What is the best way to automate browser QA for persistent loading states?▼

Automating browser QA for persistent loading states involves post-load DOM inspection after navigation completes, checking whether spinners, skeletons, and progress bars remain visible when the page should be settled.

Does this approach work for catching 404 errors on pages that return HTTP 200?▼

Yes, it detects 404 and similar error states that appear even when the HTTP response was successful by matching error patterns in the DOM content after the page settles.

Can I use this to find broken navigation that renders no visible text?▼

Yes, you can find broken navigation by inspecting the DOM after a wait period to identify routes that render almost no visible text, surfacing blank-screen defects for QA triage.

Related Skills

Explore More Software Engineering Skills→
Shaarav4795Shaarav4795

web-design-reviewer

Inspect websites visually and fix responsive, accessibility, and layout issues in source code.

Community
Intermediate
clawpod-appclawpod-app
46

bug-report

Generate structured bug reports with reproduction steps and severity assessments.

Community
Intermediate
Luqman-Ud-DinLuqman-Ud-Din

qa-detect-forced-colors

Detect forced-colors accessibility failures in rendered web pages.

Community
Intermediate
nextplus896nextplus896

laravel-exceptions

Create Laravel custom exceptions with static factories and HTTP responses.

Community
Intermediate