mockup-extract

Extract React UI components into an isolated mockup sandbox with rewritten imports.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/Celia-12/Proyecto-Mern --skill mockup-extract-celia-12
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mockup-extract
Source: https://github.com/Celia-12/Proyecto-Mern/tree/main/frontend/.local/skills/mockup-extract
Command: npx skills add https://github.com/Celia-12/Proyecto-Mern --skill mockup-extract-celia-12

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extracting UI components from a running codebase for isolated visual inspection and iterative design is tedious and error-prone when done by hand. This Skill removes guesswork by copying the real source, resolving imports, stubbing external behavior, and producing an isolated preview that matches the app's visual output exactly.

Core Features & Use Cases

  • Precise extraction: Trace the full import graph for a target component and copy or inline dependencies so the component renders identically in a sandbox.
  • Safe stubbing: Replace network calls, routing, and global state with deterministic mocks so previews are stable and side-effect free.
  • Scoped styling and fonts: Generate a group-level stylesheet that reproduces the app's CSS variables and fonts without leaking tokens into other mockups.
  • Use Case: Move an app's Navbar or Settings page into the mockup sandbox to create variants, run visual comparisons, or hand the exact rendering to designers.

Quick Start

Extract the Navbar component from the frontend codebase into the mockup sandbox and preview it on the canvas for redesign.

Frequently Asked Questions about mockup-extract

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

FAQPage Schema
How do I extract React components into an isolated mockup sandbox for visual redesign?

You can isolate React UI components for visual iteration by tracing their import dependency graph, copying real source files, rewriting import paths, and stubbing external behavior to render them identically in a mockup sandbox.

What is the best way to isolate a React UI component for visual comparison without side effects?

The best way to isolate a React UI component for visual comparison is to replace network calls, routing, and global state with deterministic mocks, generating a scoped stylesheet to ensure stable, side-effect free previews.

Does component extraction work with any React SPA project to create UI variants?

Yes, component extraction works with React SPA projects to create UI variants by resolving imports, copying assets, and generating a group-level stylesheet that reproduces CSS variables and fonts without leaking tokens into other mockups.

How do you preserve CSS variables and fonts when copying app components to a mockup canvas?

You preserve CSS variables and fonts when copying app components to a mockup canvas by generating a group-level stylesheet that reproduces the app's styling environment exactly without leaking tokens into other mockups.

Why do extracted React components fail to render correctly in a design sandbox?

Extracted React components fail to render correctly in a design sandbox when import paths are not rewritten to the mockup directory or when external behaviors like routing and global state are not properly stubbed with deterministic mocks.

Can I hand off isolated React component renders to designers for iterative design?

Yes, you can hand off isolated React component renders to designers for iterative design by moving the app's exact visual output into a mockup sandbox, allowing designers to safely create variants and run visual comparisons.