Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    UI Reference Replication — Premium

    1

    Replicate or redesign web interfaces from screenshots, Figma, and URLs with evidence-based visual QA.

    $18.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    UI Reference Replication — Premium

    UI Reference Replication — Premium

    Example session with this skill installed

    Build a new hero section for our landing page. Use the attached screenshot as a Reference-Faithful guide. Use our existing Tailwind config and the Button component from /components/ui.

    • Read your context and instructions
    • Compiled the ui reference replication

    I have analyzed the provided screenshot and your project's Tailwind configuration. The implementation follows the Reference-Faithful fidelity mode to match the layout geometry and typography hierarchy precisely.

    Hero Section Implementation

    import { Button } from "@/components/ui/button";
    
    export const HeroSection = () => {
      return (
        <section className="relative flex flex-col items-center px-6 py-24 lg:py-32 overflow-hidden bg-slate-950">
          {/* Visual Anchor: Gradient Glow */}
          <div className="absolute top-0 -z-10 h-full w-full bg-[radial-gradient(circle_at_50%_-20%,rgba(120,119,198,0.3),rgba(255,255,255,0))]" />
          
          <div className="max-w-4xl text-center">
            <h1 className="text-4xl font-bold tracking-tight text-white sm:text-6xl">
              Build faster with <span className="text-indigo-400">visual precision</span>
            </h1>
            <p className="mt-6 text-lg leading-8 text-slate-300 max-w-2xl mx-auto">
              Our new engine replicates your designs with pixel-level accuracy while maintaining 
              clean, accessible code that follows your existing project standards.
            </p>
            <div className="mt-10 flex items-center justify-center gap-x-6">
              <Button size="lg" className="bg-indigo-500 hover:bg-indigo-400">
                Get Started
              </Button>
              <a href="#" className="text-sm font-semibold leading-6 text-white">
                View Documentation <span aria-hidden="true">→</span>
              </a>
            </div>
          </div>
          
          {/* Reference Observation: Responsive Image Shadow */}
          <div className="mt-16 flow-root sm:mt-24">
            <div className="rounded-xl bg-white/5 p-2 ring-1 ring-inset ring-white/10 lg:-m-4 lg:rounded-2xl lg:p-4">
              <img
                src="/dashboard-preview.png"
                alt="App screenshot"
                width={2432}
                height={1442}
                className="rounded-md shadow-2xl ring-1 ring-gray-900/10"
              />
            </div>
          </div>
        </section>
      );
    };
    

    Next steps

    1. Run node ui-reference-replication/scripts/capture-screenshots.mjs to verify the rendering.
    2. Compare the output against the reference using the visual-review template.
    3. Verify the mobile breakpoint behavior matches the requested responsive spec.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Building a UI that actually matches a design is difficult when agents can only "see" code. This skill enables agents with visual capabilities to bridge the gap between Figma files, screenshots, or live URLs and your production codebase. It handles the heavy lifting of visual analysis and implementation while ensuring your existing application logic remains untouched.

    What it does

    • Visual implementation builds new UI components or entire screens based on screenshots, Figma frames, or website URLs.
    • UI redesign restyles existing applications while strictly preserving current routes, data permissions, and business logic.
    • Fidelity control allows switching between literal "Reference-Faithful" replication and "Reference-Inspired" creative interpretations.
    • Visual QA captures implementation screenshots to perform side-by-side perceptual comparisons against the source material.
    • Accessibility enforcement implements WCAG 2.2 AA standards by default, fixing design flaws during the coding phase.

    How it works

    1. Visual Preflight checks if the agent can perceive both the source reference and the rendered output before starting.
    2. Reference Specification maps observed layout geometry, typography roles, color tokens, and component hierarchy.
    3. Implementation generates framework-specific code using your existing design tokens and project conventions.
    4. Automated Audit runs bundled scripts for responsive behavior, performance budgets, and functional regression.

    Frameworks & tools

    Works with any modern frontend stack. Includes built-in support for Node.js and Python helper scripts, Playwright for browser-based testing, and axe-core for accessibility auditing.

    Why this beats prompting it yourself

    Standard prompts often result in generic "AI-style" layouts that ignore your existing design tokens. This skill uses a structured specification and a mandatory visual perception gate to ensure the output matches the reference's specific geometry and hierarchy.

    Use cases

    • Converting a Figma mockup into a production-ready React or Vue component.
    • Modernizing a legacy dashboard UI while keeping all backend API contracts intact.
    • Auditing a finished frontend implementation against a design spec to find visual regressions.
    • Rapidly prototyping a landing page inspired by a visual reference.

    Known limitations

    Requires an agent with vision capabilities to perceive images and rendered output. Browser-based QA scripts require Playwright and a local or containerized runtime environment.

    Requires vision-capable agent. Browser-based audits require Playwright. Scripts require Node.js or Python runtime. Does not bypass authenticated paywalls or private Figma permissions.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 10 days ago

    Requires

    Node.js
    Python
    Figma MCP
    playwright
    Git

    Permissions

    Terminal / Shell
    Browser
    Network Access
    Read Files
    Write Files
    Listed10 days ago

    What's inside

    Frequently Asked Questions

    This skill bridges the gap between visual design and code by using a 'Visual Preflight' gate, ensuring the agent actually sees and maps the reference geometry rather than just guessing the layout based on generic training data.

    Yes, the skill is designed to handle 'UI Redesign' tasks where it restyles the visual layer while strictly preserving your existing routes, API contracts, and business logic.

    The skill works with any modern frontend stack; it generates code based on your project's specific design tokens and conventions rather than forcing a specific framework.

    You will need an AI agent with vision capabilities (to 'see' the references) and a runtime environment that supports Playwright and Node.js for the automated Visual QA and accessibility auditing.

    By default, the skill implements WCAG 2.2 AA standards, automatically identifying and fixing accessibility flaws found in the original design reference during the coding phase.

    The purchase includes the core skill logic, a suite of helper scripts for Playwright and axe-core, and the structured specification templates used for mapping layout geometry.

    New in Frontend & Web Apps