ux-writinglisted

# UX writing Write interface copy that reads like someone thought about the specific screen, or rewrite copy that reads like a model generated it. ## Step 0 - load the pattern table Before writing or rewriting anything, read [references/banned-patterns.md](references/banned-patterns.md) if it is not already in context. It has the 13 AI-tell patterns this skill checks for, each with a bad and fixed example in interface copy. Do not skip this even if the patterns look familiar - the exact wording matters for a consistent check every run. ## Step 1 - pick a mode - **Write mode**: the request describes a component or flow with no existing copy to work from - a button, a form, an error state, an empty state, a delete flow. - **Strip mode**: the request includes an actual string of existing copy, or says the copy sounds generated, robotic, or "too AI". If the request gives neither a component to write for nor a string to rewrite, ask what needs copy instead of guessing. ## Step 2 - write mode ### 2a. Identify the element type If the user names the element (button, error, empty state), use it directly. If they only describe a flow ("write the copy for deleting a project"), break it into the elements that flow actually needs - usually a button, a confirmation, an error, and a success message - and write each one. ### 2b. Apply the rule for that element type | Element | Rule | Shape | |---|---|---| | Button / link | Start with a verb, name the outcome. Sentence case. Never