devlyn:browser-validate

Launch a dev server and validate UI features through real browser interactions.

4|Updated Feb 23, 2026

Search Tags:#automation #screenshots #validation #ui-testing #e2e-testing #browser #dev-server

Ready to run

npx skills add https://github.com/fysoul17/one-query-v1 --skill devlyn-browser-validate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: devlyn:browser-validate
Source: https://github.com/fysoul17/one-query-v1/tree/main/onequery/.claude/skills/devlyn%3Abrowser-validate
Command: npx skills add https://github.com/fysoul17/one-query-v1 --skill devlyn-browser-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Browser-based validation bridges the gap between code and real user interactions by validating features in a live browser, ensuring the UI flows are actually usable rather than just visually correct.

Core Features & Use Cases

End-to-end browser validation: start the dev server, navigate the app, interact with UI, and verify outcomes with evidence.
Proactive regression checks: verify UI changes proactively after updates to catch issues early.
Real-browser reports: produce screenshots and a clear pass/fail narrative for feature verification.

Quick Start

Use this skill by asking to run a browser test, e.g., "test in browser" or "validate the UI" to initiate an end-to-end validation run.

Frequently Asked Questions about devlyn:browser-validate

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

FAQPage Schema

How do I run end-to-end UI validation in a browser after making frontend changes?▼

End-to-end UI validation is performed by launching a dev server, navigating the app, performing real-user interactions, and verifying outcomes in a live browser to catch regressions early.

Do I need a runnable frontend project to validate browser-based features?▼

Yes, browser-based feature validation requires a runnable frontend project, supporting multiple frameworks via start scripts and orchestration to execute real-browser interactions.

What is the best way to proactively catch UI regressions across different frontend setups?▼

Proactive regression checks are done by running end-to-end browser validation after UI updates, verifying user flows work across different frontend setups to catch issues early.

Can I get screenshots and reports from end-to-end browser testing?▼

Yes, real-browser reports produce screenshots and a clear pass/fail narrative for feature verification, providing evidence that UI flows are actually usable.

How do I test new UI changes in a live browser environment?▼

You can test new UI changes by initiating an end-to-end validation run that starts the dev server, navigates the app, interacts with the UI, and verifies outcomes in a live browser.

When do I need browser-based end-to-end validation instead of visual UI checks?▼

Browser-based validation is needed when you must bridge the gap between code and real user interactions, ensuring UI flows are actually usable rather than just visually correct.