Component Studio

One place to configure how every shared component behaves on each surface â turn a component on or off, choose which hats see it, and toggle its feature modules. Changes are per-surface and reversible; the components read this config at render, so a change here reshapes the live page without a redeploy.

Admin only â a tab inside Shattique's Pure Admin Center. Every change is logged and reversible; nothing is deleted.

PURE Home

/pure-home â unsaved

How it wires: the Studio reads/writes pure_surface_configs (surface Ã component â enabled, roles, modules) via mcp_component_config_get/_set. Each component checks PureConfig.get(surface, key) at mount and honors it. Until Code lands the RPCs it persists locally (fail-soft) so you can design the config now. This is the control the Design System roadmap calls Component Studio.