mockup-extract

Extract UI components into standalone mockup sandboxes with rewritten imports and stubbed calls.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/lostitonce420-beep/novaura.life-official --skill mockup-extract-lostitonce420-beep
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mockup-extract
Source: https://github.com/lostitonce420-beep/novaura.life-official/tree/main/The-Gilded-Cage/.local/skills/mockup-extract
Command: npx skills add https://github.com/lostitonce420-beep/novaura.life-official --skill mockup-extract-lostitonce420-beep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pulling an existing UI component from the main app into a standalone mockup sandbox to preview, redesign, or create variants without rebuilding from scratch.

Core Features & Use Cases

  • Extracts a real component with its dependencies into mockup sandbox, rewriting imports and stubbing external calls to preserve visual fidelity.
  • Enables rapid design iteration by embedding the result in an iframe preview and supporting variant creation.
  • Use case: redesign a navbar from the main app to generate visual variants on the canvas for comparison.

Quick Start

Extract the target component into the mockup sandbox and open its preview for design 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 a UI component from my main app into a mockup sandbox?

To extract a UI component into a mockup sandbox, the skill analyzes the component's dependencies, rewrites its imports, and stubs external calls to preserve visual fidelity for isolated design iteration.

Can I preview an extracted UI component in isolation without rebuilding it?

Yes, you can preview an extracted UI component in isolation by embedding the result in an iframe preview within the mockup sandbox, allowing you to iterate on the design without rebuilding from scratch.

What is the best way to create design variants from an existing navbar?

Creating design variants from an existing navbar involves pulling the component into a standalone mockup sandbox, using the extraction workflow to stub external calls, and generating visual variants on the canvas for comparison.

Why does my extracted component lose visual fidelity when pulled into a design sandbox?

Visual fidelity is lost when dependencies are not properly resolved, but this skill preserves the original appearance by analyzing dependencies, rewriting imports, and stubbing external calls during the component extraction process.

Does this mockup extraction workflow support frontend redesign without affecting the main app?

Yes, this frontend redesign workflow supports isolated iteration by pulling the target component into a standalone mockup sandbox, ensuring that external calls are stubbed so the main app remains unaffected during design exploration.

When do I need to stub external calls for component extraction?

You need to stub external calls during component extraction when moving a UI component into a mockup sandbox, ensuring that the isolated design environment preserves visual fidelity without requiring the main app's full runtime.