Writing For Interfaces

andrewgleave/skills/writing-for-interfaces

by andrewgleaved6c72b885a1902d4b74d4bd9beca80f2a1b96b51No license34 starsListed Oct 9, 2026Updated Oct 9, 2026Repository updated 5 months ago

Use when someone asks to write, rewrite, review, or improve text that appears inside a product or interface. Examples: "review the UX copy", "is there a better way to phrase this", "rewrite this error message", "write copy for this screen/flow/page", reviewing button labels, improving CLI output messages, writing onboarding copy, settings descriptions, or confirmation dialogs. Trigger whenever the request involves wording shown to end users inside software — apps, web, CLI, email notifications, modals, tooltips, empty states, or alerts. Also trigger for vague requests like "review the UX" where interface copy review is implied. Do NOT trigger for content marketing, blog posts, app store listings, API docs, brand guides, cover letters, or interview questions — this is a technical writing skill for interface language.

  1. d6c72b885a1902d4b74d4bd9beca80f2a1b96b51Currentcommit d6c72b8Published Oct 9, 2026

Source and attribution

Source:andrewgleave/skillsinwriting-for-interfacesat commitd6c72b8

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal