Writing for Interfaces focuses on making interface writing an integral part of the design process. It's aimed at designers and writers looking to create seamless product experiences by aligning text with layout and interactions.
$ npx skills add https://github.com/andrewgleave/skills --skill writing-for-interfacesWriting for Interfaces helps product teams establish and maintain consistent voice across UI copy. The skill uses a structured workflow: establish your product's voice by documenting what it does, who it's for, and its personality traits; evaluate whether the task involves new copy, reviews, or rewrites; apply voice and core principles grounded in accessibility and clarity; and flag terminology drift to keep phrasing consistent. This approach ensures UI text supports both usability and brand identity, reducing confusion and creating seamless product experiences. Teams benefit from systematic copy evaluation, clearer communication with users, and tools to maintain voice consistency across interfaces.
Add the skill using the command below
Improve user interactions with thoughtful text placement
Enhance product clarity through cohesive design and writing
Facilitate smoother user experiences by considering text and design simultaneously
$ npx skills add https://github.com/andrewgleave/skills --skill writing-for-interfacesgit clone https://github.com/andrewgleave/skillsCopy the install command above and run it in your terminal.
Launch Claude Code, Cursor, or your preferred AI coding agent.
Use the prompt template or examples below to test the skill.
Adapt the skill to your specific use case and workflow.
Act as a UX writing consultant for [COMPANY], a [INDUSTRY] business. Review the following interface copy for [PRODUCT/APP NAME] and suggest improvements to enhance clarity, consistency, and user engagement. Focus on microcopy, error messages, and CTAs. Here’s the copy: [PASTE COPY HERE]
### **UX Writing Review for [PRODUCT/APP NAME]** #### **Current Copy Analysis** **1. Login Button** *Current:* "Click here to log in" *Feedback:* Too generic. Lacks urgency and clarity. *Suggested:* "Log in to access your dashboard" *Why:* Directs users to the next step while reinforcing value. **2. Error Message** *Current:* "Invalid input. Try again." *Feedback:* Passive and unhelpful. Doesn’t explain the issue. *Suggested:* "Email must include an @ symbol. Example: [email protected]" *Why:* Provides clear guidance to correct the mistake. **3. Empty State** *Current:* "No items found" *Feedback:* Bleak and unmotivating. Doesn’t guide users forward. *Suggested:* "Your cart is empty. Start shopping to add items!" *Why:* Encourages action while maintaining a friendly tone. #### **Key Improvements** - **Consistency:** Standardize terminology (e.g., "Log in" vs. "Sign in"). - **Tone:** Align with [COMPANY]’s brand voice (e.g., professional, friendly). - **Clarity:** Prioritize user goals over technical jargon. #### **Next Steps** 1. Audit all CTAs for action-oriented language. 2. Test error messages with real users for comprehension. 3. Update the style guide to reflect these changes.
Take a free 3-minute scan and get personalized AI skill recommendations.
Take free scan