Writing For Interfaces

For when you're writing button labels, error messages, empty states, or any text that lives inside a product interface. It walks you through establishing voice first (those 3-4 personality traits that define how your product sounds), then applying it through a clear precedence chain: clarity beats voice, voice beats craft rules. Includes a pattern reference guide and treats tone as dials you turn up or down depending on context. Won't trigger for marketing copy, docs, or blog posts. This is strictly for the words users see when they're actually using your software.