make-tweakable

Loaded when the user wants in-design controls for toggling variants, swapping colors, editing copy, or flipping feature flags directly inside a design artifact.

What to expose

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.

Where the panel lives

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.

Activation protocol

Order matters. Run these steps in this sequence: