Run a local web app in Chrome and capture screenshots for verification.
npx skills add https://github.com/neon-law-foundation/navigator --skill web-preview
Please help me install this Agent Skill. Skill: web-preview Source: https://github.com/neon-law-foundation/navigator/tree/main/.claude/skills/web-preview Command: npx skills add https://github.com/neon-law-foundation/navigator --skill web-preview
This Skill removes the guesswork from front-end changes by letting you run the web app against the real local dependency stack, open it in a browser, and confirm that the UI and client-side behavior actually render as expected.
Ask me to start the local dependency stack, launch the web app under Doppler, open it in Chrome, and capture a screenshot in /tmp to verify the page visually.
High-intent search queries and answers about installing and using this skill.
To preview a local web app in Chrome and capture a screenshot, you need to run the application with its full dependency stack and use headless Chrome to save visual evidence. This process confirms that layout, styling, and dynamic content render correctly.
Browser-based UI verification uses WebDriver to drive browser interactions and confirm that client-side scripts and visual states behave correctly. It validates dynamic page elements by running automated tests against the actual rendered output in Chrome.
Yes, you need Doppler to inject seeded secrets and KIND to manage the local dependency stack. These tools ensure the web app starts correctly with its required services so you can accurately verify the UI in Chrome.
The best way to verify front-end changes locally is to run the app against its real dependency stack and capture headless Chrome screenshots. This removes the guesswork by providing visual proof that layout and styling work as expected.
A local web preview fails to load the dependency stack if layered environment loading is incomplete or missing required services. You must ensure all dependencies, including Doppler-seeded secrets and KIND, are running before launching the app.
Yes, you can use headless Chrome to validate dynamic content and client-side behavior by capturing screenshots or running WebDriver tests. This confirms that interactions, scripts, and visual states render correctly within the browser.
GainInsightDevOrchestrate multi-account AWS infrastructure with Doppler secrets and Amplify CI/CD.
krzemienskiAutomates browser-based validation of web applications for runtime issues, visual regressions, and more.
GGEduAutomate browser-based visual testing and UI interaction verification across breakpoints.
kriscendobotValidate Mermaid diagram syntax in markdown files using a headless Node.js environment.
