What is the Stop Describing UI skill?
Stop Describing UI is an MIT-licensed skill by artouc, built from one SKILL.md. It tells your coding agent to delete copy that explains a feature, lists side effects or describes backend behavior, and to use precise verbs, icons and spacing instead. It applies when writing or reviewing any interface text.
Stop Describing UI is a copy-editing skill, not a visual one. Its SKILL.md opens with a plain principle: an interface shows what the user can do and does not explain itself, so a sentence stays only when the user would otherwise make a real mistake.
It works in two modes. While writing UI, the agent applies the rules as it goes. While reviewing, it goes through every string, applies each rule and presents the result as before and after.
The nine rules in short
- Do not describe the feature; name the action.
- Use specific verbs with their object, so New becomes Connect repository.
- Keep only the most critical consequence of an action.
- Do not describe backend behavior such as logging or syncing.
- Do not explain undo when the same control undoes it.
- Do not repeat what the page title or navigation already says.
- Do not state what does not exist.
- Put the upgrade or enable button on screen instead of a sentence about it.
- Do not rely on text alone; use icon-led short lines and spacing.
Who it is for and who it is not for
Best for
- Product and front-end teams whose AI-built screens are full of helper text.
- Reviews of settings pages, empty states, permission notices and onboarding.
- Developers who want a before and after list for each string.
Not for
- Marketing copy or long-form content. The rules aim at interface strings. For metadata work, see fixing-metadata.
- Layout, color or type decisions. Pair it with typeset or layout.
- Legal or safety text that the user must read. The skill says irreversible and destructive effects always stay.
Use it with UiChemy
This skill tightens the words inside an interface your agent built. When that build must become an editable WordPress page, UiChemy AI to WordPress imports an existing AI build. Click Get Started on uichemy.com.
How to install Stop Describing UI Skill: Cut Explanatory Copy From Interfaces
git clone https://github.com/artouc/stop-describing-ui.gitThe README documents a one-line skills CLI install; the manual copy above takes only this skill.Clone the repository
Run the command above. The skill is the folder skills/stop-describing-ui, which holds one SKILL.md.
Copy the folder
Copy skills/stop-describing-ui into your agent's skills directory, for example .claude/skills/ inside a project for Claude Code.
Name it in a request
Ask for it by name, for example: Use stop-describing-ui to review the strings on this settings page and show before and after.
Check that it loaded
Paste a screen with a long helper sentence and ask for a review. The agent should answer with a before and after list and drop the sentence.
Key features
- Delete feature descriptionsA heading, control and label already say what a screen is for, so the sentence explaining it goes. The skill's empty-state example ends with one Connect repository action.
- Specific verbsGeneric verbs such as New, Create, Manage, Set up, Configure, Go and OK are replaced with the verb that names what actually happens.
- One consequenceWhen an action has several effects, only the most critical one stays. Effects that follow from it are implied.
- Destructive effects stayDeleting data, charging money and notifying customers are treated as the critical consequence and are always kept.
- No backend talkWhere data is stored, what is logged and what syncs in the background are removed from user-facing text.
- No undo hints for togglesA toggle that turns something off also turns it on, so explaining that is dropped unless undo needs a different control.
- Show, do not tell, how to enableIf a feature needs a plan, a connection or a setting, the button or toggle that does it replaces the instruction sentence.
- Restrictions kept brieflyA limit the user would otherwise try and fail at, such as a role that cannot act, stays as one short line with an icon.
- Icons and spacing over symbolsArrows, bullets, pipes and colons as separators are replaced by icons and grouping.
- Nine-step checklistEach string is checked in order against the rules; if nothing is left, nothing is shown.
Frequently asked questions
What is the Stop Describing UI skill?
It is an agent skill in the artouc/stop-describing-ui repository. One SKILL.md holds nine rules and a checklist for stripping explanatory copy from headings, empty states, toggles, dialogs, banners and onboarding, replacing description with specific verbs, controls, icons and spacing.
How do I install Stop Describing UI?
Clone the repository and copy skills/stop-describing-ui into the folder your agent loads skills from. The README also shows a one-line command through a skills CLI. Then ask the agent to use stop-describing-ui when writing or reviewing interface text.
Which AI coding agents does it work with?
The README does not name specific agents. It is a standard SKILL.md folder, so it should suit tools that load skills from a folder, but check your tool's skills documentation for the exact location and trigger behavior before relying on it.
Will it delete warnings I need?
Not by design. The skill says irreversible or destructive effects, such as deleting data, charging money or notifying customers, count as the critical consequence and always stay. It also keeps restrictions the user would otherwise try and fail at, as one short line with an icon.
What does Stop Describing UI do to a button label?
Rule two replaces generic verbs such as New, Create, Manage, Set up, Configure, Go or OK with a precise verb and its object. The skill's own example turns New into Connect repository once the explanatory sentence above it is removed.
Is it a design system or a copywriting guide?
Neither fully. It is a narrow editing rule set for interface text. It does not choose colors, type or layout, and it does not write marketing copy. Many teams pair it with a visual design skill such as frontend-design.
Does it review existing screens?
Yes. The SKILL.md says that when reviewing UI the agent goes through every string, applies each rule and presents the result as before and after. When writing UI, it applies the rules as it writes.
Is it free and open source?
The repository is MIT licensed. The skill is a single Markdown file plus an assets folder of before and after illustrations. There is no paid tier or API key mentioned in the README.


