mockup-extract

Extract UI components into a mockup sandbox and rewrite imports.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill enables the quick extraction of existing UI components from a main app into a mockup sandbox, facilitating design iteration, variant creation, and visual reference without altering the original codebase.

Core Features & Use Cases

  • Component Extraction: Pulls existing components and their dependencies into a mockup sandbox.
  • Rewriting Imports: Re-writes imports to ensure the component works within the sandbox environment.
  • Embedding Components: Embeds the component as an iframe on the canvas for visualization and iteration.
  • Use Case: When a designer needs to iterate on an existing UI component within a mockup environment, such as a new app or prototype.

Quick Start

Extract the 'SettingsPage' component from the main app into the mockup sandbox using the 'mockup-extract' skill.

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 main app for design iteration in a sandbox?

Extracting UI components for design iteration involves pulling existing components and their dependencies into a mockup sandbox, rewriting import paths, and stubbing external dependencies to ensure compatibility for isolated visualization without altering the original codebase.

How does dependency stubbing work when extracting mockup UI components?

Dependency stubbing for mockup UI components analyzes the extracted component's external dependencies and rewrites import paths, ensuring the component operates independently within the sandbox environment without requiring the full main application context.

Can I use iframe embedding to visualize extracted UI components in a mockup sandbox?

Iframe embedding can be used to visualize extracted UI components by placing the rewritten component directly onto the canvas, allowing designers to iterate on variants and view the mockup design within an isolated sandbox frame.

What is the best way to iterate on UI component variants without modifying the original codebase?

The best way to iterate on UI variants without modifying the original codebase is to extract the target component into a mockup sandbox, rewrite import paths, stub external dependencies, and use iframe embedding for visual reference and design iteration.

Does extracting a UI component for a mockup sandbox rewrite all import paths automatically?

Extracting a UI component for a mockup sandbox requires component and dependency analysis to automatically rewrite import paths and stub external dependencies, ensuring the extracted design iteration functions correctly in its new environment.