Skip to main content

Overview

Studio’s style vocabulary is spread across a lot of small panels. A colour token name only appears inside a picker, a breakpoint band only shows when you expand one accordion. That is fine while you are building and unhelpful when you are trying to remember a name. This page collects them. Where the real thing lives:

The two property planes

A component exposes two different property sets depending on where you are editing it. Both sets are enumerated in full in the generated component catalogs.

What the Style panel actually calls things

Read top to bottom off a Heading’s Style tab. This is the on screen vocabulary, which does not always match the underlying key names.
Radius has two vocabularies. The panel labels its presets None, SM, MD, LG and Full. The generated component reference records the same control as the numeric presets 0, 4, 8, 16, 999, plus a custom px value. Same control: the panel names them, the schema stores numbers.

Colour tokens

16 tokens in 4 groups. Every token holds a separate value per theme mode. Light and Dark ship by default, and more named modes can be added.
Only $Token values follow a Colors edit. A literal hex does not. If a theme colour change did not affect a component, check whether that property holds a token or a literal.

Typography

18 named styles. Sizes and weights are per project. These are the names, which is what a reference is for. Each row carries these fields:

Token syntax

Any colour type property or style value can hold a raw value or a $token reference resolved against the active theme mode. The namespace is inferred from the token string. In the Style panel’s colour picker these appear as a Theme Tokens section. Picking $Primary there is what makes a later Colors edit ripple through.

Spacing, opacity and elevation

Breakpoints

Studio has two separate breakpoint systems, with different numbers and different labels. This is the most confusing piece of style vocabulary in the product, so both are named here. Do not reason from one system’s band name to the other’s.
How they line up against measured preview widths: Against Responsive Visibility the three preview sizes hit the three bands cleanly, one size per band. Against App Config’s breakpoints the labels do not match: the preview’s portrait Tablet falls inside App Config’s band called Tablet (landscape), and the preview’s Tablet landscape falls in App Config’s Desktop. The numbers are internally consistent, the two systems simply do not share a vocabulary.

Scale multipliers

App Config → Shared → Themed Component Scale holds the multipliers that drive the derived tiers. Each is locked to Mobile = 1 (Base) with adjustable Tablet and Desktop multipliers. Studio’s own note: Colors and behaviour never scale.

Component catalogs

The 72 universal style keys and the per component property tables.

Visibility rules

The four rule mechanisms in the Style tab.