fieldtest

Validate rendered web apps in a real browser and produce evidence-backed QA findings.

2|Updated May 21, 2026
One-click install
npx skills add https://github.com/howells/skills --skill fieldtest
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fieldtest
Source: https://github.com/howells/skills/tree/main/fieldtest
Command: npx skills add https://github.com/howells/skills --skill fieldtest

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves the risk of shipping UI or UX bugs that only appear when an app is rendered in a real browser, including responsive layout issues, console errors, and broken or confusing flows.

Core Features & Use Cases

  • Evidence-backed browser QA: Produces findings grounded in what actually happened in-browser (routes visited, console and network signals, viewport behavior, and reproducible steps).
  • Responsive and persona-focused checking: Verifies mobile and desktop behavior and applies a chosen lens (e.g., first-time user, designer, operator) to evaluate usability and clarity.
  • Safe fix workflow (optional): When asked, it can move from reproduction to scoped code edits and re-test the affected route/flow in the browser.

Quick Start

Use the fieldtest skill to test your local or provided URL in the browser and produce a report with prioritized findings and reproduction steps.

Frequently Asked Questions about fieldtest

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

FAQPage Schema
How do I validate web app responsive layouts and catch console errors in a real browser?

Browser QA validation tests your rendered web app to catch responsive layout issues and console errors by inspecting routes, network signals, and viewport behavior. It produces evidence-backed findings with reproduction steps.

What is evidence-backed browser QA and how does it work for localhost testing?

Evidence-backed browser QA validates a local dev or localhost web app by exercising routes in a real browser. It inspects console and network signals, applies viewport coverage, and generates a structured report with reproducible steps.

How do I perform persona-based accessibility checks and responsive testing for web apps?

Persona-based accessibility checks apply a chosen lens like first-time user or operator to evaluate usability. Responsive testing verifies mobile and desktop viewport behavior, grounding findings in actual in-browser navigation and route exercises.

Can I use browser or Playwright navigation to test web regression and dogfood new features?

Yes, browser or Playwright-based navigation supports feature dogfooding and route regression checks. It inspects console and network signals across viewports, producing structured reports with prioritized findings and reproduction steps.

Does browser QA testing support scoped code fixes and re-testing affected routes?

Yes, an optional safe fix workflow moves from bug reproduction to scoped code edits, then re-tests the affected route or flow directly in the browser to verify the resolution.

What is the best way to document web app UX validation findings with reproduction steps?

Structured browser QA reports document UX validation findings by capturing actual routes visited, viewport behavior, and console signals. They include prioritized issues alongside clear reproduction steps for developer handoff.