Ios Button Style Hierarchy
iOS defines four button style roles with distinct visual weights: .borderedProminent for primary CTA, .bordered for secondary actions, .borderless for tertiary inline actions, and role: .…
$ prime install @community/fact-ios-button-style-hierarchy Projection
Always in _index.xml · the agent never has to ask for this.
IosButtonStyleHierarchy [fact] v1.0.0
iOS defines four button style roles with distinct visual weights: .borderedProminent for primary CTA, .bordered for secondary actions, .borderless for tertiary inline actions, and role: .destructive (red tint) for delete/remove actions.
Loaded when retrieval picks the atom as adjacent / supporting.
IosButtonStyleHierarchy [fact] v1.0.0
iOS defines four button style roles with distinct visual weights: .borderedProminent for primary CTA, .bordered for secondary actions, .borderless for tertiary inline actions, and role: .destructive (red tint) for delete/remove actions.
Evidence
- .borderedProminent: filled background, highest visual weight — one per screen, primary call-to-action.
- .bordered: outlined or lightly filled — secondary and supporting actions.
- .borderless: no frame, lowest weight — tertiary, inline, or supplementary actions.
- role: .destructive: red tint applied to any style — delete, remove, or irreversible actions.
- Using multiple .borderedProminent buttons on one screen creates ambiguity about the primary action.
Loaded when retrieval picks the atom as a focal / direct hit.
IosButtonStyleHierarchy [fact] v1.0.0
iOS defines four button style roles with distinct visual weights: .borderedProminent for primary CTA, .bordered for secondary actions, .borderless for tertiary inline actions, and role: .destructive (red tint) for delete/remove actions.
Evidence
- .borderedProminent: filled background, highest visual weight — one per screen, primary call-to-action.
- .bordered: outlined or lightly filled — secondary and supporting actions.
- .borderless: no frame, lowest weight — tertiary, inline, or supplementary actions.
- role: .destructive: red tint applied to any style — delete, remove, or irreversible actions.
- Using multiple .borderedProminent buttons on one screen creates ambiguity about the primary action.
Evidence
- .borderedProminent: filled background, highest visual weight — one per screen, primary call-to-action.
- .bordered: outlined or lightly filled — secondary and supporting actions.
- .borderless: no frame, lowest weight — tertiary, inline, or supplementary actions.
- role: .destructive: red tint applied to any style — delete, remove, or irreversible actions.
- Using multiple .borderedProminent buttons on one screen creates ambiguity about the primary action.
Source
prime-system/examples/frontend-design/primes/compiled/@community/fact-ios-button-style-hierarchy/atom.yaml