ui-preview

Navigate to local dev servers and storybooks, capture screenshots, and analyze rendered UI components.

Updated Jan 16, 2026
One-click install
npx skills add https://github.com/jeninh/ampskills-dotfile --skill ui-preview
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui-preview
Source: https://github.com/jeninh/ampskills-dotfile/tree/main/.agents/skills/ui-preview
Command: npx skills add https://github.com/jeninh/ampskills-dotfile --skill ui-preview

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Preview local dev servers and storybooks to enable quick UI validation across components.

Core Features & Use Cases

  • Preview UI components across web and storybook environments.
  • Take screenshots for QA reviews and design feedback.
  • Inspect and compare components as they render on local servers.

Quick Start

Open the target URL using navigate_page and capture a screenshot with take_screenshot.

Frequently Asked Questions about ui-preview

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

FAQPage Schema
How do I take screenshots of local dev servers for UI validation?

To take screenshots of local dev servers for UI validation, you can use this Skill to navigate to your local URLs and capture visual outputs. It leverages the chrome-devtools MCP tool to wire navigation and screenshot capture across web environments.

Can I preview Storybook components automatically during development?

Yes, you can preview Storybook components automatically during development. The Skill supports navigating to Storybook environments, taking screenshots, and analyzing visuals to enable quick UI validation across your components.

What do I need to inspect web UI components on a local server?

To inspect web UI components on a local server, you need the chrome-devtools MCP tool installed via npm or npx. This dependency wires the necessary browser navigation, script evaluation, and screenshot capture functions.

What is the best way to automate UI preview and screenshot capture for QA?

The best way to automate UI preview and screenshot capture for QA is by navigating to the target URL and capturing the rendered state. This Skill automates that process by using chrome-devtools to evaluate scripts and take screenshots for design feedback.

Does this approach work with both standard web environments and Storybook?

Yes, this approach works with both standard web environments and Storybook. It is designed to preview local dev servers and Storybook setups, allowing you to inspect and compare components as they render across different local environments.

Why do I need the chrome-devtools MCP tool to preview my local UI?

You need the chrome-devtools MCP tool to preview your local UI because it provides the underlying browser automation required. It wires the page navigation, script evaluation, and screenshot capture mechanisms needed to validate your components.