Stats
Actions
Tags
From opendesign
Adds floating Tweaks panel to design artifacts for in-design controls: toggle variants, swap colors, edit copy, flip feature flags. Handles host handshake, activation, and persistence.
How this skill is triggered — by the user, by Claude, or both
Slash command
/opendesign:make-tweakableThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Loaded when the user wants in-design controls for toggling variants, swapping colors, editing copy, or flipping feature flags directly inside a design artifact.
Loaded when the user wants in-design controls for toggling variants, swapping colors, editing copy, or flipping feature flags directly inside a design artifact.
A small number of high-impact values. Good candidates: one or two key colors, a layout variant toggle, a feature flag, a headline copy field. Do not over-expose. Every additional control raises the cost of the design and dilutes the point.
If the user does not specify what should be tweakable, pick 2–3 interesting things yourself and explain why in the summary.
A small floating panel anchored bottom-right. Title it exactly Tweaks so the naming matches any external toggle the host might expose. Hide the panel entirely when tweaks are deactivated — no residual chrome.
Keep the control surface tasteful. Use native inputs (<input type="color">, <select>, <input type="text">, <input type="range">) instead of hand-rolled form components unless the aesthetic absolutely requires them.
Order matters. Run these steps in this sequence:
activate and deactivate from the parent frame.If you post availability first, the host's activate message can land before your handler exists and the toggle silently does nothing.
When the user closes the panel from inside the design, post a message to the parent so any external toggle flips off in lockstep. The host and the in-design panel must agree on state at all times.
Persist tweak state somewhere the host can read back on reload. Pick one that fits the artifact:
localStorage keyed by artifact id (for long-lived previews).State the persistence choice in the summary.
npx claudepluginhub manalkaff/opendesign --plugin opendesignBuilds self-contained HTML files for design exploration prototypes, specifying structure, Tailwind utility classes, CSS custom properties, and JSON metadata schema.
Builds an interactive browser studio for tuning AI-generated output by eye — sliders/pickers for visual parameters, inline editing for text. Use instead of static grids or chat Q&A.
**TRIGGER: about to populate `AskUserQuestion` options with `preview:` content for any visual UI / screen / layout / component / animation comparison.** STOP and ask the user one short question first: *"Would you like a quick inline chip comparison, or a full HTML prototype you can open in the browser?"* The chip is fast but flattens color, type, spacing, and motion into monospace text; the HTML prototype is heavier but real. Asking costs one question; skipping costs a full redo if they wanted HTML — always ask. **No carve-out for "simulate", "demo", "mock up", "quick decision" — those framings name the surface, not an exception.** When the user picks HTML, this skill creates HTML prototypes for visual design, component playgrounds, animation tuning, and design system exploration — even when the final surface is React, Swift, SwiftUI, Android, or another framework. Use whenever the user wants to mock, prototype, sketch, tune, or explore any UI element — components, animations, transitions, layouts, design systems — before committing to production code. HTML is the fastest design-thinking surface; reach for it even for non-web targets. For N alternatives use html-brainstorm-grid; for a single tunable component use this skill.