skills.rest
MrSuttonmann
MrSuttonmannCOMMUNITY
Explore all skills by this author →
GitHub

frontend-smoke-verify

Run Playwright in-browser UI smoke tests for FlightJar frontend changes.

55|1|Updated Apr 18, 2026
Search Tags:#frontend#playwright#ui-testing#harness#smoke-test#console-errors#flightjar
One-click install
npx skills add https://github.com/MrSuttonmann/flightjar --skill frontend-smoke-verify
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: frontend-smoke-verify
Source: https://github.com/MrSuttonmann/flightjar/tree/main/.claude/skills/frontend-smoke-verify
Command: npx skills add https://github.com/MrSuttonmann/flightjar --skill frontend-smoke-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Frontend changes often require manual, time-consuming validation across viewports and environments. This skill streamlines that by booting a minimal FlightJar backend, injecting a fake snapshot, and validating the UI in-browser to surface console errors quickly.

Core Features & Use Cases

  • Boots the FlightJar backend in a Playwright harness with BEAST_HOST pointing at a dead host and disables certain live-data features to keep tests deterministic.
  • Injects a fake snapshot and opens the detail panel to exercise core rendering paths.
  • Verifies the panel and dialogs render without console errors across desktop and mobile viewports.
  • Use Case: when a frontend change is requested, to quickly smoke-check rendering, interactions, and error handling before broader testing.

Quick Start

Boot the FlightJar backend with the Playwright harness and run the in-browser smoke test against the UI.

Frequently Asked Questions about frontend-smoke-verify

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

FAQPage Schema
How do I run in-browser smoke tests for frontend UI changes?▼

Frontend smoke checks are automated by booting a minimal backend in a Playwright harness, injecting a fake snapshot, and validating panel rendering and interactions across desktop and mobile viewports to surface console errors.

How does Playwright detect console errors during UI verification?▼

Playwright captures console errors during UI verification by opening the detail panel and exercising core rendering paths, verifying that both panels and dialogs render without throwing console errors across targeted viewports.

Can I verify frontend changes across both desktop and mobile viewports?▼

Yes, frontend changes are verified across both desktop and mobile viewports by running the Playwright harness, which exercises core rendering paths and validates that panel interactions remain error-free on each viewport size.

How do I keep frontend smoke tests deterministic when live data is unavailable?▼

To keep frontend smoke tests deterministic, the backend is booted with its host pointing at a dead address and certain live-data features are disabled, ensuring the UI relies solely on an injected fake snapshot.

What is the best way to surface console errors in frontend iterations before broader testing?▼

The best way to surface console errors in frontend iterations is running an automated in-browser smoke check that boots a controlled backend, injects test snapshots, and validates rendering paths against desktop and mobile viewports.

Related Skills

Explore More Software Engineering Skills→
martiendejongmartiendejong
1

integration-testing

Configure Playwright tests and capture findings in ClickUp across phased workflows.

Community
Advanced
kennyolofsson23-netizenkennyolofsson23-netizen

deploy-flow

Deploy code to production via feature-branch, test, staging, PR, and merge workflow.

Community
Advanced
xg-gh-25xg-gh-25
36

health-check

Execute deterministic health checks on SwarmAI subsystems and summarize pass/fail results for CI workflows.

Community
Advanced
Typeless-GitTypeless-Git
1

webapp-testing

Automate end-to-end testing of local web applications with Playwright.

Official
Intermediate