mockup-extract

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

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/gopforever/Idle-Echoes --skill mockup-extract-gopforever
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mockup-extract
Source: https://github.com/gopforever/Idle-Echoes/tree/main/.local/skills/mockup-extract
Command: npx skills add https://github.com/gopforever/Idle-Echoes --skill mockup-extract-gopforever

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pulls an existing component from the main app into a sandbox so it can be previewed, iterated, and redesigned without hand-coding approximations.

Core Features & Use Cases

  • Extracts a target component and its dependencies into the mockup sandbox.
  • Rewrites imports, stubs external dependencies, and renders the result in an isolated iframe for safe iteration.
  • Generates design variants and compares against the original.

Quick Start

Ask the agent to extract the target component into artifacts/mockup-sandbox and preview it on the canvas.

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 for isolated preview and redesign?

Extracting a UI component for isolated preview involves pulling the target component from the main app into a mockup sandbox. The process rewrites imports and stubs external dependencies to render the result safely in an isolated iframe.

Can I generate design variants from a component that already exists in my codebase?

Yes, you can generate design variants from an existing codebase component by extracting it into the mockup sandbox. This allows you to iterate and compare new variants directly against the original design without hand-coding approximations.

How does component isolation work when sandboxing a UI prototype?

Component isolation works by rewriting imports to a sandbox directory and stubbing external dependencies. This ensures the extracted UI prototype renders independently in a preview environment without affecting the main application.

What is the best way to iterate on a UI mockup without hand-coding approximations?

The best way to iterate on a UI mockup without hand-coding approximations is to extract the actual component into a mockup sandbox. This provides a sandbox-ready preview for safe, isolated design iteration.

Do I need to manually stub external dependencies when extracting a component?

No, you do not need to manually stub external dependencies when extracting a component. The extraction process automatically stubs external dependencies and rewrites imports to ensure component isolation in the mockup sandbox.

Where does the sandbox-ready preview output get saved during UI component extraction?

The sandbox-ready preview output is saved at the mockup sandbox preview path. The extracted component and its dependencies are moved to the sandbox source directory for isolated rendering.