mockup-extract

Extract UI components into a mockup sandbox with rewritten dependencies and CSS.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/rezosnd/MINI-PROJECT- --skill mockup-extract-rezosnd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mockup-extract
Source: https://github.com/rezosnd/MINI-PROJECT-/tree/main/ML%20BACKEND%20DASHBOARD/.local/skills/mockup-extract
Command: npx skills add https://github.com/rezosnd/MINI-PROJECT- --skill mockup-extract-rezosnd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designers and developers often need an exact copy of an existing UI component for redesign, variant creation, or visual comparison, but hand‑coding approximations leads to mismatched dimensions, colors, and interactions.

Core Features & Use Cases

  • Precise extraction: Copies the component and its dependency graph into the mockup/ sandbox, preserving original styles and assets.
  • Dependency handling: Classifies imports as inline, copy, or stub, rewrites paths, and generates a group‑level CSS file for tokens and fonts.
  • Ready‑to‑preview: Embeds the extracted component via the sandbox’s /preview/ URL, enabling instant visual iteration.
  • Typical use case: A product team wants to redesign the navigation bar; they invoke the skill to pull the current navbar into the sandbox, adjust styles, and compare variants side‑by‑side.

Quick Start

Extract the navigation bar component into the mockup sandbox for immediate redesign.

Frequently Asked Questions about mockup-extract

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

FAQPage Schema
How do I extract a React UI component into an isolated sandbox for redesign?

To extract a React UI component into an isolated sandbox, the skill copies the component and its dependency graph into a `mockup/` directory, preserving original styles and assets for immediate visual iteration.

How are component dependencies handled when copying a UI component to a mockup sandbox?

When copying a UI component to a mockup sandbox, dependencies are classified as inline, copy, or stub. Import paths are rewritten and a group-level CSS file is generated to preserve visual fidelity.

Does extracting a UI component for visual comparison modify the main application code?

Extracting a UI component for visual comparison does not modify the main application. The process isolates the exact visual replica in a sandbox environment, leaving the original codebase untouched.

What is the best way to create variants of an existing UI component without losing visual fidelity?

The best way to create variants without losing visual fidelity is to extract the exact UI component into a mockup sandbox, where styles and assets are preserved and dependencies are safely stubbed or inlined.

How do I preview an extracted component after copying it into the mockup sandbox?

To preview an extracted component after copying it into the mockup sandbox, access the sandbox's `/preview/` URL, which embeds the isolated UI component for instant side-by-side comparison and styling adjustments.