43 tags with authored form, scope, and relationships. Stable tags can be written into layer names; rich data, motion, and scenarios belong in the structured contract.
Showing 43 of 43
[page=value]Stable
Page identity
A DFC Bridge page root always uses native Auto Layout and must never carry [asset]. It may sit directly on the Figma page or below native Figma SECTION canvas organizers; those organizers are transparent and contribute no DFC Bridge context.
Source of truth
DFC Bridge tag
Scope
page root
Form
property
Value
kebab-case
Relationships
requires[bp][view]
[route=/catalog]Stable
Production route
Source of truth
DFC Bridge tag
Scope
page root
Form
property
Value
route
Relationships
requires[page]
conflicts with[route-pattern]
[route-pattern=value]Experimental
Dynamic route pattern
Source of truth
DFC Bridge tag
Scope
page root
Form
property
Value
route-pattern
Relationships
requires[page]
conflicts with[route]
[bp=1440]Stable
Control width
Source of truth
DFC Bridge tag
Scope
page root
Form
property
Value
positive-integer
Relationships
requires[page]
[view=value]Stable
Page view
Source of truth
DFC Bridge tag
Scope
page root
Form
property
Value
kebab-case
Relationships
requires[page]
[anchor=value]Stable
Anchor target
Source of truth
DFC Bridge tag
Scope
layer
Form
property
Value
kebab-case
[section=value]Stable
Page section identity
A stable [section] value is the required boundary for Check selected section; never add page/bp/view/route tags to a section. A frame-built section or editable Page Sections source root uses native Auto Layout unless that exact selected root also carries [asset] and is a genuine opaque whole visual. A section nested below a different non-page-root opaque [asset] ancestor is an invalid blocked selection because the audit cannot pierce the inherited boundary. An invalid [asset] on a page root never creates opacity. Placed INSTANCE nodes are atomic and their source is audited separately.
Prefer the boolean form with a stable layer name. Outside an asset, [decor] belongs only on the exact intended absolute visual node and never exempts a container or GROUP from structural rules.
Source of truth
DFC Bridge tag
Scope
layer
Form
boolean or property
Value
kebab-case
[asset] · [asset=value]Stable
Whole-export policy
Prefer the boolean form with a stable layer name. An asset is one opaque visual subtree whose root remains in the parent flow; [decor] and [asset] may be combined. Page roots cannot be assets.
Source of truth
DFC Bridge tag
Scope
layer
Form
boolean or property
Value
kebab-case
[height=hug]Stable
Dynamic height policy
Source of truth
DFC Bridge tag
Scope
layer
Form
property
Value
enum
[overflow=visible]Stable
Overflow policy
Source of truth
DFC Bridge tag
Scope
layer
Form
property
Value
enum
[lines=1440]Stable
Maximum visible lines
Source of truth
DFC Bridge tag
Scope
layer
Form
property
Value
positive-integer
[bridge-exception=value]Stable
Documented transfer exception
Overlay may satisfy exact-node absolute positioning intent. Manual-layout documents a proposed structural deviation but does not suppress page, section, container, or GROUP errors.
Source of truth
DFC Bridge tag
Scope
layer · page root
Form
property
Value
kebab-case
Relationships
requires[reason]
[reason=value]Stable
Machine-readable reason
Source of truth
DFC Bridge tag
Scope
layer · page root
Form
property
Value
kebab-case
Relationships
requires one of[bridge-exception][height]
[locale=ru-RU]Stable
Locale variation axis
Source of truth
DFC Bridge tag
Scope
page root · variant root
Form
property
Value
locale
[theme=value]Stable
Theme variation axis
Source of truth
DFC Bridge tag
Scope
page root · variant root
Form
property
Value
kebab-case
[experiment=value]Experimental
Experiment variation axis
Source of truth
DFC Bridge tag
Scope
page root · variant root
Form
property
Value
kebab-case
[role-view=value]Experimental
Permission-role variation axis
Source of truth
DFC Bridge tag
Scope
page root · variant root
Form
property
Value
kebab-case
[data=value]Experimental
Data stress scenario
Source of truth
DFC Bridge tag
Scope
page root · variant root · layer
Form
property
Value
kebab-case
[text=value]Deprecated
Figma text node type
Use the native TEXT node type and a stable layer name.
Source of truth
Figma metadata
Scope
layer
Form
property
Value
kebab-case
[image=value]Deprecated
Figma image node type
Use native fills/export metadata and a stable layer name.
Source of truth
Figma metadata
Scope
layer
Form
property
Value
kebab-case
[icon=value]Deprecated
Figma icon node type
Use component/vector metadata and a stable layer name.
Source of truth
Figma metadata
Scope
layer
Form
property
Value
kebab-case
[container=value]Deprecated
Figma hierarchy
Use frames or components with native Auto Layout. GROUP is valid only inside an opaque [asset] subtree.
Source of truth
Figma metadata
Scope
layer
Form
property
Value
kebab-case
[layout=value]Deprecated
Figma layout mode
Use Auto Layout and constraints.
Source of truth
Figma metadata
Scope
layer
Form
property
Value
kebab-case
[abs]Deprecated
Figma positioning
Use native Figma positioning.
Source of truth
Figma metadata
Scope
layer
Form
boolean
Value
no value
[component=value]Deprecated
Figma component source
Resolve the source component from Figma metadata.
Source of truth
Figma metadata
Scope
layer
Form
property
Value
kebab-case
[to=value]Deprecated
Second navigation destination
Use [href=...] as the single navigation destination.
Source of truth
DFC Bridge tag
Scope
control
Form
property
Value
string
[wrapper-role=value]Deprecated
Wrapper intent tag
Express wrapper purpose with Figma structure and stable naming.
Source of truth
Figma metadata
Scope
layer
Form
property
Value
kebab-case
[card=value]Deprecated
Ad-hoc card identity
Use the stable layer/component name; use [item=...] only for an explicit repeated-item contract.