Border Radius Decision
frontend-design
$ aoe install @community/pattern-border-radius-decision Projection
Always in _index.xml · the agent never has to ask for this.
BorderRadiusDecision [pattern] v1.0.0
Loaded when retrieval picks the atom as adjacent / supporting.
BorderRadiusDecision [pattern] v1.0.0
Label
Border Radius Decision Checklist
Meta
- License: Apache-2.0
- License Provenance: package-authorship-claim
Problem
Developers ship border-radius values without answering the underlying design intent question. The result is radius decisions that conflict with product personality or create visual inconsistency across component types.
Solution
Before shipping, run a five-question checklist that forces articulation of product personality first, then validates radius consistency, interactive-element parity, nested-element adherence, and radius variation. If question 1 cannot be answered, stop and define personality before choosing any radius value.
Loaded when retrieval picks the atom as a focal / direct hit.
BorderRadiusDecision [pattern] v1.0.0
Label
Border Radius Decision Checklist
Meta
- License: Apache-2.0
- License Provenance: package-authorship-claim
Problem
Developers ship border-radius values without answering the underlying design intent question. The result is radius decisions that conflict with product personality or create visual inconsistency across component types.
Solution
Before shipping, run a five-question checklist that forces articulation of product personality first, then validates radius consistency, interactive-element parity, nested-element adherence, and radius variation. If question 1 cannot be answered, stop and define personality before choosing any radius value.
Relations
related: [@impeccable/persona-vercel-clean, @impeccable/persona-magazine-editorial, @community/anti-pattern-generic-saas-blue, @community/check-focus-visible]
Label
Border Radius Decision Checklist
Meta
- License: Apache-2.0
- License Provenance: package-authorship-claim
Problem
Developers ship border-radius values without answering the underlying design intent question. The result is radius decisions that conflict with product personality or create visual inconsistency across component types.
Solution
Before shipping, run a five-question checklist that forces articulation of product personality first, then validates radius consistency, interactive-element parity, nested-element adherence, and radius variation. If question 1 cannot be answered, stop and define personality before choosing any radius value.
Source
aoe-engine/examples/frontend-design/primes/compiled/@community/pattern-border-radius-decision/atom.yaml