inspect-display

Walk through running web app routes to detect functional gaps, mock-data leaks, and broken routes.

1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/steve-piece/bytheslice --skill inspect-display
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: inspect-display
Source: https://github.com/steve-piece/bytheslice/tree/main/skills/inspect-display
Command: npx skills add https://github.com/steve-piece/bytheslice --skill inspect-display

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the problem of "drift" between what is claimed to be finished in a project checklist and the actual state of the running application, catching regressions, mock-data leaks, and broken routes that per-slice reviews miss.

Core Features & Use Cases

  • Cross-Cutting Audit: Automatically walks every route of a running web application to verify functionality and visual integrity.
  • Drift Detection: Identifies discrepancies between the master checklist and the live runtime environment.
  • Use Case: Run this before a UAT or client demo to ensure that no unrelated pages have broken and that no mock data is accidentally leaking into production-ready surfaces.

Quick Start

Invoke the inspect-display skill to perform a full platform-wide visual audit of the currently running application.

Frequently Asked Questions about inspect-display

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

FAQPage Schema
How do I perform a visual audit of a running web application to catch regressions?

A visual audit navigates every route of a running web app to capture screenshots and check functional gaps. It validates the runtime reality against your declared checklist status to catch regressions and mock-data leaks.

What is visual drift detection in web apps and when do I need it?

Visual drift detection identifies discrepancies between your master checklist and the live runtime environment. You need it before a UAT or client demo to ensure no unrelated pages have broken and no mock data leaks into production-ready surfaces.

Can I run a read-only smoke test across all routes without modifying my web app?

Yes, you can perform a read-only visual walkthrough across all discovered routes without performing destructive mutations. It uses browser-based MCP tools to navigate, screenshot, and analyze the application state safely.

How do I detect mock-data leaks in my web application before a client demo?

To detect mock-data leaks, perform a cross-cutting audit that walks every route of your running web application. This validates runtime reality against declared checklist status and identifies any mock data leaking into production-ready surfaces.

Does a platform-wide visual regression test require browser-based MCP tools?

Yes, a platform-wide visual regression test requires browser-based MCP tools. These tools are necessary to navigate, screenshot, and analyze the application state across all discovered routes without performing destructive mutations.