Voice and tone

Not defined yet.

Aura’s consistency principle says every team speaks to the user in the same way, visually and in writing. That sentence is the whole writing rule. There is no terminology list, no tone scale, no capitalization guide, and no content pattern for errors, empty states, or buttons.

What does exist, and belongs to other foundations:

• Product principles name the attitude of the system: accessible, consistent, reusable, shareable, user control, forgiveness, and a sense of stability. See Principles.
• Button and empty-state structure is specified. The words inside them are not. See Patterns.
• Type size, case, and tracking for labels are visual rules. See Typography.

A voice and tone page should be written from a real guide in the repo. Until that guide exists, this page stays empty on purpose.