
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.
- skills.sh installs
- 1.1K
- GitHub stars
- 34
- last updated
- Aug 21, 2026
Install
$ npx -y skills add andrewgleave/skills --skill writing-for-interfaces --agent claude-codeInstalls into .claude/skills of the current project.
Files
Writing for Interfaces
Good interface writing is invisible. When words work seamlessly with design, people don't notice them.
Writing should be part of the design process from the start, not something filled in at the end. When words are considered alongside layout, interaction, and visual design, the result feels seamless. When they're an afterthought, product experiences feel stitched together.
Every piece of text in an interface is a small act of communication: it should respect the person's time, meet them where they are, and help them move forward.
When triggered
Step 1: Establish voice and personality
Voice is the foundation. All copy decisions — what to say, how to say it, what to leave out — flow from a clear understanding of who this product is, who it's for, and how it should sound. Without a defined voice, copy becomes inconsistent and the product loses coherency.
Search for an existing voice definition. Check for:
- A
CLAUDE.md,AGENTS.md, or similar project config that defines voice and/or tone - A style guide, design system documentation, or brand guidelines
- A word list or terminology reference
Sponsors
Details
- Repository
- github.com/andrewgleave/skills
- Categories
- Backend & APIs, Git & Pull Requests, Documentation, Code Review & Quality, Debugging, Marketing & SEO, CLI & Terminal
- First seen
- Jun 3, 2026