Writing For Interfaces

andrewgleave/skills/writing-for-interfaces

作者 andrewgleaved6c72b885a1902d4b74d4bd9beca80f2a1b96b51無授權條款34 個星標收錄於 2026年10月9日更新於 2026年10月9日儲存庫5 個月前更新

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.