Unicorn Studio
Meng ToCommunityCreated by Meng To
- Skill
- Tool integration
- Software development
- MIT
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides guidance on embedding and configuring Unicorn Studio WebGL scenes within web environments. It covers the implementation of the Unicorn Studio SDK, container setup, and the application of data attributes to control rendering behavior, performance, and interactivity. The skill assists in managing scene loading, responsive sizing, and layering within various site-building platforms.
What it does
- Provides patterns for embedding Unicorn Studio scenes using the SDK.
- Explains how to configure scene containers with specific dimensions.
- Details the use of data attributes to manage render scale, DPI, and frame rate.
- Offers guidance on optimizing scenes for different device capabilities.
- Outlines methods for handling interactivity through scene events.
- Addresses common integration issues like container sizing and WebGL context limits.
When to use it
- When embedding custom WebGL visuals into web projects without manual shader coding.
- When integrating interactive animations into platforms like Webflow, Framer, or custom sites.
- When adjusting the performance or resolution of an embedded scene.
- When troubleshooting display issues or WebGL context limitations on a page.
Advantages
- Enables the use of interactive WebGL scenes without writing custom three.js code.
- Provides granular control over rendering parameters via simple HTML attributes.
- Supports performance tuning through lazy loading and frame rate capping.
- Facilitates the layering of interactive animations with existing UI elements.
Usage examples
- “How do I embed a basic Unicorn Studio scene into my website?”
- The agent provides the necessary HTML container structure with the required data-us-project attribute and instructions for initializing the SDK.
- “My scene is not showing up on my page, what should I check?”
- The agent guides you to verify that the container element has defined width and height dimensions and checks for potential WebGL context limits.
- “How can I optimize a Unicorn Studio scene for mobile devices?”
- The agent suggests applying specific data attributes like data-us-scale, data-us-dpi, and data-us-fps to reduce resource usage.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/mengto/unicorn-studio/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip unicorn-studio.zip -d .agents/skills
Documentation by Meng To
Unicorn Studio — No-code WebGL Scenes (Embed/SDK) Skill
When to use
Designers want custom WebGL visuals without hand-coding shaders/three.js
You need “designed” effects layered with text/images/video, with built-in interactivity
Site builders: Framer, Webflow, Wix, Figma Sites, etc.
What it is
A scene editor (layers + effects + events) that exports:
Embed via Unicorn Studio SDK (small JS library)
Or JSON/code export for faster/self-hosted loading (plan-dependent)
Key embed patterns
Load SDK (can be in
<head>or footer depending on above-the-fold):UMD from jsDelivr (versioned)
Call
UnicornStudio.init()once DOM is ready
Add attributes to a container element:
data-us-project="PROJECT_ID"Optional performance/behavior params:
data-us-scale(render scale)data-us-dpi(resolution multiplier)data-us-fps(cap FPS)data-us-lazyload="true"data-us-production="true"
Optional JSON source:
data-us-project-src="https://.../scene.json.txt"
Events (authoring-side)
Appear (entrance), Scroll (progress/velocity), Hover, Mousemove
Use events for “feels interactive” without writing JS.
Common pitfalls
Container has no defined dimensions → scene won’t display
Ensure the element with
data-us-projecthas width/height.
Too many scenes on one page → WebGL context limits + memory
Prefer <10 scenes/page; WebGL context max ~16.
Performance on low-end devices
Use
data-us-scale/data-us-dpi/data-us-fps; reduce dynamic layers/effects.
Site builder preview limitations
Many builders won’t render in edit mode; must preview/publish to see it.
Quick recipes
1) Basic embed container
<div style="width: 100%; height: 420px" data-us-project="YOUR_PROJECT_ID"></div>2) Performance-first embed
<div
style="width: 100%; height: 420px"
data-us-project="YOUR_PROJECT_ID"
data-us-lazyload="true"
data-us-production="true"
data-us-scale="0.75"
data-us-dpi="1.25"
data-us-fps="45"
></div>What to ask the user
Target platform: Webflow / Framer / coded site?
Is the scene above-the-fold? (affects script placement and lazyload)
Mobile support requirement + acceptable quality/FPS
Number of scenes on the page and whether JSON export is available
Files
- ATTRIBUTION.mdAdded by AutoGineer850 B
- LICENSELicence file added by AutoGineer1.0 KiB
- REFERENCES.md321 B
- SKILL.md2.5 KiB
- demo/PROMPT.md1.8 KiB
- demo/index.html15.9 KiB
- demo/preview.jpg44.4 KiB
demo/PROMPT.md
Unicorn Studio Demo Prompts
Minimal prompt
Use $unicorn-studio to create a polished standalone HTML example that clearly demonstrates the skill.
Recreate the demo
Use $unicorn-studio to build a responsive reference demo for this capability:
Use when embedding and customizing Unicorn Studio interactive animations on the web (embed, responsive sizing, performance, layering with UI, fallbacks).
Direction
Use a full-bleed procedural canvas atmosphere behind precise interface framing.
Use an art-directed composition with one clear focal point, restrained supporting copy, and enough surrounding interface to show how the technique behaves in a real product or landing page.
Canonical example
Render eighteen slow procedural wave bands and one narrow moving signal beam.
Place the animated field behind compact live-system metadata.
Deliverable
Create demo/index.html as a standalone document.
Keep CSS and JavaScript inline.
Put any required images, fonts, models, textures, or vendor files in demo/assets/.
Do not add a framework, package manager, build step, or node_modules.
Add controls only when they help inspect or replay the technique.
Acceptance checks
Keep the demo responsive from 390px through 1440px.
Use semantic HTML, visible focus states, and reduced-motion handling.
Keep all HTML, CSS, and JavaScript inside demo/index.html.
Use only relative local asset paths.
Keep the canvas decorative and the content readable if rendering is unavailable.
Cap device pixel ratio and pause when the document is hidden.
Remix prompt
Use $unicorn-studio and keep the same implementation contract, but change the subject, copy, palette, and content hierarchy. Preserve the core technique, accessibility behavior, responsive rules, and performance constraints demonstrated by the reference.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- Meng To
- Publisher
- Meng To (Community)
- Source
- MengTo/Skills · agent-skills/web-design/unicorn-studio · commit 5ea1661
- Licence
- MIT License (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Meng To.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download unicorn-studio.zip