mockup-extract

Transfer UI components into a sandboxed mockup by rewriting imports and stubbing dependencies.

Updated Feb 9, 2026
One-click install
npx skills add https://github.com/soq123/SE3354-Calo-fit --skill mockup-extract-soq123
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mockup-extract
Source: https://github.com/soq123/SE3354-Calo-fit/tree/main/.local/skills/mockup-extract
Command: npx skills add https://github.com/soq123/SE3354-Calo-fit --skill mockup-extract-soq123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pull an existing UI component from the main app into a sandboxed mockup to enable accurate visual iteration and redesigns.

Core Features & Use Cases

  • Pull existing UI components from the main app into the mockup sandbox for isolated preview on the canvas.
  • Enable redesigns, variants, and design iterations starting from the real source code.
  • Rewrites imports, stubs external dependencies, and embeds the result as an iframe for faithful visual fidelity.

Quick Start

Extract the target component into the mockup sandbox and load it in the preview pane to begin iteration.

Frequently Asked Questions about mockup-extract

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

FAQPage Schema
How do I extract an existing UI component into an isolated preview for design iteration?

To extract a UI component for design iteration, pull the component from the main app into a sandboxed mockup. This rewrites imports and stubs external dependencies to embed the result as an iframe preview.

What is the best way to preview code-based UI components without external dependency conflicts?

The best way to preview code-based UI components without dependency conflicts is using a sandbox mockup. It stubs external dependencies and embeds the component as an iframe to preserve visual fidelity during redesigns.

Can I create design variants starting directly from my real source code?

Yes, you can create design variants starting from real source code by transferring the existing UI component into a sandboxed mockup. This enables accurate visual iteration and comparison directly from the original code base.

How does dependency mocking work when pulling a UI component into a mockup?

Dependency mocking works by stubbing external dependencies and rewriting imports when transferring a UI component into the mockup sandbox. This isolates the component for accurate visual preview without breaking the main application.

Does pulling an existing UI component into a sandbox affect the main application code?

No, pulling an existing UI component into a sandbox does not affect the main application. It rewrites imports and stubs dependencies within the isolated mockup environment, leaving the original source code intact for safe visual iteration.