remix
Take a section, effect, or interaction from one website and rebuild it in another site in Design, matched to the destination's design system, with swappable assets and live knobs
Install / Use
npx skills add BuilderIO/skills --skill remixInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
DesignSupported Platforms
Our assessment of remix
remix scores 87/100 on our quality scale, 139th of 260 Design skills we index.
Its SKILL.md is 6.7 KB long, well organised into 10 sections and no code examples: a thorough specification that gives an agent plenty to work with.
With 4,394 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so remix is actively maintained.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-11-16. Automated pattern scan on 2026-11-16. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
remix compared with similar skills
All 4 of these similar skills score higher than remix; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| remix (this skill)by BuilderIO | 87 | 4.4k | 54d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
Frequently asked questions
- How do I install remix?
- Run
npx skills add BuilderIO/skills --skill remix. The install tabs above show the steps for each supported agent. - Which AI agents does remix work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is remix safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is remix still maintained?
- The repository was last updated about 2 months ago, so remix is actively maintained.
Skill content
View source on GitHubname: remix description: >- Take a section, effect, or interaction from one website and rebuild it in another site in Design, matched to the destination's design system, with swappable assets and live knobs. Use when the user asks to remix, borrow, port, or recreate part of a site in theirs, or asks to "remix explain" how a site's effect works. metadata: visibility: exported
Remix
/remix takes one part of a source site (a hero, a shader background, a
scroll effect, a 3D card) and rebuilds it inside a destination site, in the
destination's own colors, fonts, and components. Design is the workbench: the
source and the destination sit side by side as screens, the user points at what
to take and where it goes, and every effect ships with knobs in Design's
Tweaks section.
The editor is hosted at https://design.agent-native.com. Open it, connect, and
place screens exactly as /visual-edit does (WebMCP open-visual-edit in a
page-capable browser, otherwise the hosted Design MCP at
https://design.agent-native.com/mcp). Read the visual-edit skill for the
bridge, auth, and handoff rules; this skill covers only what remix adds. Never
start a local Design server.
Ask Only What Is Missing
Two inputs decide the job. Ask for one only when the request leaves it out:
- Source: the site (and page) to remix from, e.g.
apple.com/airpods-pro. - Destination: the running local app or site to remix into, or "a new site". For a new site, scaffold a minimal page in the user's stack and run it on localhost first.
Do not ask about style, colors, or fonts; the destination answers those. Do not ask which section yet; the user picks it on the canvas.
Put Both Sites On The Canvas
- Start or reuse the destination dev server and verify the route responds,
then call
open-visual-editwith its URL and route. That screen is the destination. - Add the source as a second screen beside it, at the same viewport width.
Design's URL screens are localhost-backed, and most production sites refuse
framing, so capture the source with your browser tool (rendered DOM,
stylesheets, scripts, and assets, saved to a scratch folder outside the
repo), serve that folder on its own localhost port, and add it with
add-localhost-screens. When it cannot be served, add the captured DOM as a static screen withcreate-file. Title it after the source URL. - Tell the user, in one line, to select the part to take in the source and the spot it goes in the destination. Both can be selected at once (Shift-click across screens): "from this to that". Several source layers are one remix; several destination layers mean place it in each.
Read the picks with view-screen (designSelection) or the Selected objects
context block. Ask once if the selection names only one side.
Extract From Shipped Code
The running source is the reference for how it looks; its shipped code is the reference for how it works. Read the code before writing any.
- Drive the source in your own browser (or Design's Interact mode): scroll, hover, click, and resize until the effect runs, then read the network log and the elements behind the selection.
- Pull the minified JS, CSS, and HTML that drive the selected layer. Find the
entry point (canvas/WebGL context,
requestAnimationFrameloop, scroll or pointer listeners, GSAP/Three/Lottie/Spline imports, keyframes) and pretty- print just that slice. Record shaders, uniforms, easing curves, timings, breakpoints, and asset URLs as facts with their file and line. - Keep everything captured outside the destination repository.
- Rebuild the behavior in the destination's own code. Never paste the source's code, shaders, fonts, logos, icons, copy, or media into the destination; reimplement the technique and make or pick our own assets.
Adapt To The Destination
- Read the destination's tokens first (CSS variables, Tailwind theme, design system, fonts) and map every color, type style, radius, and spacing in the remix to them. The result should look like it was always part of the destination.
- Use the destination's components and conventions for markup; add a component in its usual place rather than a pasted blob.
- Respect
prefers-reduced-motion, keep the page usable without WebGL, and do not regress the destination's load time.
Swappable Assets
Make each creative asset (image, video, 3D model, texture, Lottie, font) one named prop or constant at the top of the component, with a placeholder we own. Say in the report where to swap each one.
Knobs Are Always On
Every shader, WebGL, canvas, 3D, or animation effect gets knobs. Expose its meaningful parameters (speed, intensity, colors, scale, camera, easing, density) through Design's tweak system, never a private UI:
- Bind each parameter to a CSS custom property on the effect's root and have
the effect read it every frame (
getComputedStyle(el).getPropertyValue), so Design's livetweak-valuesupdates show instantly. - Register the knobs with
update-design, setting data pathtweaksto the definitions:{ id, label, type: "slider" | "toggle" | "segment" | "color-swatch" | "color-swatches", min, max, step, defaultValue, cssVar, unit?, scope }. Setscopeto{ screenId, nodeId }(orselectoron a URL screen) of the effect's root. Keep existing tweaks; append. - Design shows them, already expanded, in the inspector's Tweaks section whenever the user selects that screen, the effect, or any parent or child of it, and never for a sibling.
- Read values with
get-design-snapshot(tweaks,appliedTweaks) and set them withapply-tweaks. When the user is happy, write the chosen values back into the destination source as the defaults.
Remix Explain
remix explain <part of a site> teaches instead of porting. Extract the part as
above, then lay out an explainer microsite on the canvas beside the source:
- One small inline HTML/CSS screen per idea, left to right: the effect in isolation, then each layer of how it works (geometry, shader, timing, scroll binding), each a live minimal demo with a short caption and the few lines of code that matter.
- Every demo has knobs registered as above, like a lil-gui or Tweakpane panel in a three.js example, scoped to that screen.
- For something too heavy for inline HTML, run a tiny dev server and add it as a localhost screen.
Motion
When the user wants to retime a remixed animation, the Motion panel (a Design Lab) can edit GSAP-style tracks and keyframes. It is optional; knobs come first.
Finish
Show the destination screen with the remix in place, list the knobs and the swappable assets, and name what you could not reproduce. Hand off source edits the visual-edit way: the user reviews the diff in the destination repo.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
