live-preview

Detect modified view-layer files, capture route screenshots, and verify component renders.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Buckeyes22/weather-app --skill live-preview-buckeyes22
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: live-preview
Source: https://github.com/Buckeyes22/weather-app/tree/main/docs/corpora/citadel-protocols/skills/live-preview
Command: npx skills add https://github.com/Buckeyes22/weather-app --skill live-preview-buckeyes22

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The live-preview workflow closes the gap between code completion and visual correctness by capturing mid-build UI states to detect invisible features and layout regressions before release.

Core Features & Use Cases

  • Detect modified view-layer files and map them to routes for verification.
  • Capture full-page screenshots of each route using an automated tool and verify component renders.
  • Store verification artifacts for review, enabling quick triage during UI redesigns or feature handoffs.

Quick Start

Start by invoking the live-preview workflow after you modify UI components to automatically capture and verify visuals.

Frequently Asked Questions about live-preview

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

FAQPage Schema
How do I catch UI layout regressions during development before release?▼

Catch UI layout regressions mid-build by detecting modified view-layer files, mapping them to render routes, and capturing full-page screenshots for visual verification. Artifacts are saved for review to detect invisible features and layout shifts early.

How do I automatically capture screenshots of modified UI components?▼

Automatically capture screenshots of modified UI components by mapping changed view-layer files to their render routes and using an automated screenshot tool to capture full-page visuals. This workflow verifies component renders and stores artifacts for review.

Do I need a running dev server to verify UI visuals with Playwright?▼

Yes, visual verification with Playwright requires a running dev server. The workflow maps modified view-layer files to render routes and uses the screenshot tool to capture full-page visuals, producing a verification summary saved to .planning/screenshots.

What is visual regression detection for mid-build UI states?▼

Visual regression detection for mid-build UI states captures full-page screenshots of render routes mapped from modified view-layer files. It closes the gap between code completion and visual correctness, detecting invisible features and layout regressions before release.

Where are screenshot artifacts stored during UI visual verification?▼

Screenshot artifacts during UI visual verification are stored in the .planning/screenshots directory. The workflow captures full-page screenshots of mapped render routes and saves these artifacts to enable quick triage during UI redesigns or feature handoffs.

Can I use this visual verification workflow for feature handoffs?▼

Yes, use this visual verification workflow for feature handoffs to capture mid-build UI states and store screenshot artifacts for review. It detects modified view-layer files, maps them to routes, and enables quick triage during UI redesigns.