Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    claude-kit: Frontend Draft Studio

    1

    Edit React, Next.js, Vite, or HTML previews visually. Save text and style changes, then have your coding agent implement them in source inside an isolated draft.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    claude-kit: Frontend Draft Studio

    Example session with this skill installed

    /frontend-draft ./my-react-app

    I will edit the heading and card styles in the browser, then click Save changes. When I say "apply my visual changes", implement the saved requests in the draft source and verify the result.

    • Read your context and instructions
    • Compiled the claude-kit

    Example from the validated React/Next demo

    The studio opened a disposable project copy with a visual editor. I selected the heading, changed its text and color, and saved the requests. In the Vite React preview, I selected the card container, changed its padding, and saved that request as well.

    ElementBeforeRequested result
    Hero headingBuild something beautifulDesign it directly. Ship it in React.
    Heading colorInherited dark text#3158c9
    Card padding30px44px

    After the instruction "apply my visual changes", the implementation in the draft was:

    <h1 className="hero-title">Design it directly. Ship it in React.</h1>
    
    .hero-title { color: #3158c9; }
    .card { padding: 44px; /* other existing card styles preserved */ }
    

    The completed request batches were acknowledged. Reloading confirmed the heading and card styling came from JSX/CSS with no temporary inline preview styles. The React counter still worked, and the original project fixture remained unchanged.

    Next step

    Review the running draft. Ask the agent to promote the approved source changes into your project when you are satisfied. Saving a browser request alone does not change JSX; the agent must implement and verify it.

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

    About this skill

    Edit a frontend visually, then let your coding agent implement the result in real component source.

    Frontend Draft Studio opens an isolated copy of your project with an in-browser editor. Click an element to change its text, color, spacing, size, or visibility. Save your requests, then tell the agent: "apply my visual changes."

    What is included

    • Visual text and style controls, parent selection, hide, and undo.
    • React/Next.js/Vite previews with the development server and hot reload available.
    • Durable change requests containing the route, element selector, original and desired values, and surrounding context.
    • An agent workflow for applying requests to JSX/TSX and CSS, verifying the result, and acknowledging the completed batch.
    • The existing static HTML Design mode and scratch-page workflow.
    • Python servers, browser editor, instructions, README, and regression tests.

    How to use it

    1. Install the frontend-draft skill in your coding agent's skills directory.
    2. Ask: /frontend-draft <project-path>.
    3. Open the studio URL, select elements, and edit the preview.
    4. Click Save changes and tell the agent to apply your visual changes.
    5. Review the implemented draft before promoting it to your original project.

    The browser saves visual intent; the agent performs the source edits. This is a turn-based workflow, not an automatic JSX converter or a background implementation agent.

    Validated workflow

    Exercised in Chrome with Next.js App Router and Vite React: visual edits, saved requests, source implementation, and reload verification. React interaction and Next.js hot reload were also checked.

    Requires Python 3, Git, a local browser, and a coding agent with shell and file access. Framework apps also need Node.js/npm versions compatible with the project. See the compatibility note and limitations below. No Agensi API or paid design service is required to run the local tool. You'll still need your own coding-agent access. This is an independent tool, not an official Anthropic, React, or Next.js product. Use it only with projects you trust: framework startup runs their npm scripts. Original source stays separate until you approve promotion. App data and backend services used by a copied project are not automatically isolated. Framework editing binds to loopback; the legacy static server may bind to all network interfaces. Keep static sessions on a trusted machine/network.

    Visual previews become structured requests; the agent must apply them to JSX/TSX/CSS after you ask. Rerenders may reset previews while saved requests persist. No arbitrary drag-and-drop JSX restructuring, canvas, cross-origin iframe, or closed-shadow-root editing. Text editing supports text-only elements. Strict CSP can block injection. Next.js App Router and Vite React were exercised; other dev servers and operating systems are not fully tested.

    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 18 days ago

    Requires

    Python 3.9+
    Git
    Web browser
    Terminal access

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Network Access
    Environment Variables
    Browser

    Reads the selected project and writes a separate draft, Git baseline, and saved change requests. Runs Python and, for framework apps, npm install/ci and the project dev script. Opens a local preview; the framework proxy binds to loopback. Network access is used for dependencies, optional repository downloads, and any app requests. Inherits the shell environment for child processes. The legacy static server can bind to all interfaces. Run trusted projects; copied apps may still use their original backend services.

    Listed18 days ago

    What's inside

    Frequently Asked Questions

    No. The editor saves structured visual requests. Tell your coding agent "apply my visual changes"; it reads the requests, updates JSX/TSX and CSS in the draft, and verifies the implementation.

    The visual framework workflow has been exercised with Next.js App Router and Vite React. Static HTML and scratch pages use the existing Design mode. Other dev servers may work but are not guaranteed.

    Yes. The tool copies the project into a separate draft. Framework preview requests are saved in JSON until your agent implements them in that draft. Promote source changes only after review. Running a copied app does not isolate its existing backend services or external data.

    Python 3.9+, Git, a local browser, and a coding agent with shell and file access. Framework projects also need Node.js/npm versions supported by the app. Remote repositories can use Git or GitHub CLI.

    Canvas, cross-origin iframes, closed shadow roots, and arbitrary drag-and-drop JSX restructuring are unsupported. Text editing requires a text-only element. Strict Content Security Policy can block the editor, and app rerenders can reset temporary previews while saved requests remain.

    New in Frontend & Web Apps