mockup-extract

Extract UI components into a sandbox and embed them as iframes.

Updated Jun 19, 2018
One-click install
npx skills add https://github.com/ouzayr/Utilities --skill mockup-extract-ouzayr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mockup-extract
Source: https://github.com/ouzayr/Utilities/tree/main/DailyPlanner/.local/skills/mockup-extract
Command: npx skills add https://github.com/ouzayr/Utilities --skill mockup-extract-ouzayr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill allows you to pull existing UI components from your main application into a sandbox environment for redesign, variant creation, or visual reference, ensuring you work with the actual codebase rather than approximations.

Core Features & Use Cases

  • Component Extraction: Copies components and their dependencies into a mockup sandbox.
  • Dependency Management: Rewrites imports and stubs external dependencies for isolation.
  • Design Iteration: Enables redesigning, creating variants, or displaying existing UI elements on a canvas.
  • Use Case: When a user asks to "redesign my current navbar" or "show my user profile component on the board," this skill extracts the relevant code to enable isolated design work.

Quick Start

Use the mockup-extract skill to put the user's current settings page on the board.

Frequently Asked Questions about mockup-extract

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

FAQPage Schema
How do I extract UI components from my codebase for design iteration?

To extract UI components for design iteration, this Skill copies the target component and its dependencies into a dedicated sandbox, rewrites import paths, and stubs external dependencies to isolate the visual output on a canvas.

Can I redesign an existing navbar without affecting my main application?

Yes, you can redesign an existing navbar safely by pulling the actual source code into an isolated mockup sandbox, ensuring modifications and variant creation do not impact the main application.

What is the best way to isolate a frontend component for visual reference?

The best way to isolate a frontend component for visual reference is to extract the actual source code into a sandbox, which manages dependencies by copying or stubbing them and embeds the component as an iframe on a canvas.

Does mockup-extract work with existing source code or manual approximations?

mockup-extract prioritizes using actual source code from your codebase over manual approximations, copying components and managing their dependencies to ensure accurate visual fidelity during design iteration.

How do component dependencies get handled when extracting UI to a sandbox?

When extracting UI components to a sandbox, component dependencies are managed by copying them directly or stubbing external dependencies, and import paths are rewritten to maintain isolation within the sandbox environment.

What are the limitations of stubbing external dependencies in a mockup sandbox?

When stubbing external dependencies in a mockup sandbox, complex interactions relying on those external services may not function fully, as the isolation process prioritizes visual fidelity and structural extraction over complete runtime behavior.