ui-teardown

Captures product screenshots and produces evidence-cited UX teardowns with feature matrices.

1|Updated Jun 30, 2026
One-click install
npx skills add https://github.com/Lia-Creative/lia-plugins --skill ui-teardown-lia-creative
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ui-teardown
Source: https://github.com/Lia-Creative/lia-plugins/tree/main/lia-tools/skills/ui-teardown
Command: npx skills add https://github.com/Lia-Creative/lia-plugins --skill ui-teardown-lia-creative

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Product and competitor analysis often relies on memory, guesswork, or uncited opinions, making teardowns untrustworthy and impossible to compare across products. This Skill captures the screens itself (via the ui-capture engine) when they do not exist yet, then produces a UX and feature teardown where every claim is cited to a specific screenshot and the analysis confidence is derived from actual capture coverage. ## Core Features & Use Cases - Capture-then-analyse in one command: Say "teardown of X" and it routes automatically — an existing capture run goes straight to analysis, a single page triggers directed capture, and a whole product or competitor triggers explore-mode capture with a coverage verification pass. - Evidence-bound analysis: A ten-section rubric (onboarding, IA, key flows, visual design, AI angle, weaknesses, and more) plus a controlled-vocabulary feature matrix where no feature is marked present without a screenshot proving it. - Honest confidence scoring: Coverage under 50% yields a Low confidence read instead of a confident wrong one, and uncaptured surfaces are named as gaps rather than invented. - Use Case: Run "teardown of Pipedrive" before a design sprint to get a rubric-structured teardown, a feature matrix comparable with past runs, and 3-6 decision-shaped takeaways framed against your own product strategy. ## Quick Start Ask the agent to run a teardown of a product, page, or competitor by saying "teardown of Pipedrive" and it will capture the screens and write the cited analysis into the capture run folder.

Frequently Asked Questions about ui-teardown

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

FAQPage Schema
How do I run a UX teardown of a competitor product?▼

Say "teardown of X" where X is the product or competitor name. The skill runs ui-capture in explore mode to discover and capture feature surfaces, verifies coverage, then writes a rubric-structured teardown and feature matrix into the capture run folder.

How do I analyze existing screenshots of a product?▼

Point the teardown at an existing capture run folder containing a manifest.json and it skips capture and goes straight to analysis. It reads the manifest first, then walks the shots in order, citing every claim to a specific screenshot.

Can it capture pages that require a login?▼

Yes, ui-capture uses your live Chrome session for authenticated pages, so no credentials are handled by the skill. Shots flagged pii: true stay local and are analyzed on-device rather than sent to an external API.

What is the difference between ui-teardown and ui-capture?▼

ui-capture is the engine that takes screenshots and writes the manifest; ui-teardown is the front door that does capture-then-analyse in one step. If you only want raw screenshots with no analysis, call ui-capture directly.

When should I not use a screenshot-based teardown?▼

Do not use it when you only need raw screenshots without analysis, or when the target is a native desktop app rather than a website. For desktop apps, capture via computer-use first, then point the teardown at the resulting screenshots.