Core idea
A narrow interface over a powerful canvas.
Block keeps the raw component intact, then adds a small layer of named inputs for the things that are meant to change.
Figma component
Block layer
Usable controls
Principles
Block gives components a controlled surface
A design component already contains structure, intent, and rules. Block makes those rules visible as typed controls people can safely use today, while creating a clearer foundation for future AI workflows.
Readable controls
Inputs are the contract.
LabeltextSubmit
VariantselectPrimary
Disabledbooleanfalse
AI foundation
Future automation needs an intentional path.
01 Component02 Block schema03 Controls04 Canvas write
01
Expose intent, not internals
The editable parts of a component should be named controls, not layer archaeology.
02
Write through one owned path
Each input owns the canvas change it makes, so behavior stays readable and predictable.
03
Prepare a surface automation can understand
Block does not make the plugin agent-operated today. It gives future automation a clearer contract than raw Figma structure.
04
Keep the canvas protected
Rules, schemas, and conflicts are handled before changes land on the component.