clear-interface
/clear-interface
Design or simplify web and product interfaces with clear information hierarchy and concise, actionable UI copy. Use when creating a page, reducing UI clutter, or removing redundant labels and explanations. Not for prose editing outside a product interface or backend-only changes.
- Author
- m1nga ↗
- Repository
- clear-interface ↗
- Licence
- MIT
- Last repository change
- 10.11.2026
Assessment and security
- Files in this package
- 3
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 10.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Design or simplify web and product interfaces with clear information hierarchy and concise, actionable UI copy. Use when creating a page, reducing UI clutter, or removing redundant labels and explanations. Not for prose editing outside a product interface or backend-only changes.
Original author description
Design or simplify web and product interfaces with clear information hierarchy and concise, actionable UI copy. Use when creating a page, reducing UI clutter, or removing redundant labels and explanations. Not for prose editing outside a product interface or backend-only changes.
How it works
- Establish the task
- Decide what belongs
- Build the hierarchy
- Write what remains
- Verify in context
SKILL.md preview
--- name: clear-interface description: "Design or simplify web and product interfaces with clear information hierarchy and concise, actionable UI copy. Use when creating a page, reducing UI clutter, or removing redundant labels and explanations. Not for prose editing outside a product interface or backend-only changes." --- # Clear Interface Make the next decision easy to understand and the next action easy to complete. Use the least interface that preserves the task, its meaning, and the product's character. ## Establish the task Read the target and enough of its surrounding flow to understand the audience, intended outcome, real content, constraints, and current behavior. Reuse the project's components, terminology, and design system. For new work, derive a compact visual direction from the actual subject and audience; do not invent a different brand. Follow the requested scope: a copy edit changes words; an interface refinement may change hierarchy and grouping; a new design builds the requested surface. Preserve unrelated behavior and content. Ask only when an unknown fact or consequential choice prevents a correct result; continue independent work. With only a screenshot or text, deliver a design/copy proposal and identify what cannot be verified. ## Decide what belongs For each region, identify what the person needs to recognize, compare, decide, do, or understand about the current state. Retain visual expression that serves the brief or helps recognition; do not use extra words to fill visual space. Choose one treatment for each piece of information: - **Keep** when it changes a decision, enables an action, identifies content, or explains a necessary state. - **Merge** when nearby elements express the same meaning in the same context. Keep repetition that supports a different step, comparison, or consequential confirmation. - **Defer** when useful detail is optional at this moment. Give it a discoverable, accurately named entry; preserve keyboard and touch access. - **Remove** when it adds no task value or intended expressive value. Show material costs, eligibility, permissions, irreversible effects, and required input constraints before the affected action. Do not move them into optional help. Do not remove a capability or alter a business rule to make the screen look simpler. ## Build the hierarchy Give the current task a clear visual priority while keeping necessary alternatives available. A dashboard or comparison view may legitimately have several tasks and dense information. Use grouping, spacing, alignment, type, and contrast to communicate relationships before adding containers or explanatory copy. Labels, numbering, borders, and dividers should encode a real distinction. Numbering needs a meaningful order or reference function. Do not automatically add an eyebrow, subtitle, card, badge, or introduction to every section. Let the brief determine color, imagery, typography, and density. Keep useful brand expression; avoid imposing one palette, font count, column count, or minimalist look on every product. Use motion to explain change or support the intended experience without delaying the task. Respect reduced-motion preferences. ## Write what remains Use the audience's vocabulary and consistent product terms. Front-load the distinguishing information. Prefer concrete actions and natural language; retain specialist terms the audience needs. Each text element should have a clear job. - **Actions:** name the outcome, adding the object when needed to distinguish it. Keep action names consistent through the flow. - **Fields:** keep persistent labels. Place necessary format instructions near the input; a placeholder is not its label. - **Help:** answer a real unresolved question. Delete descriptions that merely restate a heading or control. - **States:** distinguish loading, first use, no results, failure, success, and an unconfirmed outcome. Explain what is known. If a retry could duplicate payment or another consequential action, offer a supported status check first. - **Errors:** identify the failed operation and a supported recovery path. Include a cause only when known. Never invent a diagnosis, progress, saved state, guarantee, or capability. - **Consequences:** make payment, deletion, privacy, and access changes explicit. Preserve factual and legal meaning; leave an unresolved fact marked for clarification outside the proposed production copy. Match tone to context and stakes. Avoid filler, slogans, internal architecture, and delivery notes in operational UI. Technical detail belongs in the interface when its intended users need it. Marketing or editorial content may need argument, evidence, or atmosphere; judge its purpose rather than deleting it merely for being long. ## Verify in context Review the affected journey, not just isolated strings. When implementation is requested and a runnable environment is available, inspect the rendered result and exercise the changed interaction at its relevant widths; include keyboard access and affected error/empty/success states. Otherwise state the unverified behavior. Check whether the person can still find the needed information, distinguish actions, anticipate consequences, complete the task, and recover from failure. Preserve readable text, contrast, focus, accessible names, and reachable controls. Do not simulate simplicity with smaller text, faint contrast, truncation, unexplained icons, or hover-only essential information. If a cut makes the task harder, restore the information or improve its placement. Stop when the requested scope works and further changes would be taste rather than a demonstrated improvement. Deliver the requested design, copy, or implementation first. Briefly state material changes and actual verification limits. Keep design reasoning and implementation notes in the handoff, outside the product UI.
Files in this package (3)
- SKILL.md 6 KB
- prompt.md 2 KB
- agents/openai.yaml 1 KB
Versions
The database has no other skills named clear-interface.
Database snapshot: 13.11.2026 · package version 9d440be028df (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90ux-writing
Write the words inside an interface (labels, buttons, errors, empty states, microcopy) so they are clear, concise, and helpful. Use when writing or reviewing any text a user reads while using a product. - 90apple-interface-writing
Draft, rewrite, or audit concise interface text using an independently expressed reference-only interpretation of Apple's Human Interface Guidelines for writing. Use for buttons, labels, settings, alerts, errors, onboarding, notifications, permissions, empty states, and… - 95impeccable
Use when the user wants to design, redesign, shape, critique, audit, polish, simplify, harden, animate, or otherwise improve a frontend interface: websites, landing pages, dashboards, product UI, components, forms, settings, onboarding, empty states, and native iOS or Android… - 95impeccable
Use when the user wants to design, redesign, shape, critique, audit, polish, simplify, harden, animate, or otherwise improve a frontend interface: websites, landing pages, dashboards, product UI, components, forms, settings, onboarding, empty states, and native iOS or Android… - 100impeccable
Use when the user wants to design, redesign, shape, critique, audit, polish, simplify, harden, animate, or otherwise improve a frontend interface: websites, landing pages, dashboards, product UI, components, forms, settings, onboarding, empty states, and native iOS or Android… - 90simplify-ui
Simplifies interfaces to the bar of Linear's website or Apple Notes: simple purpose, architecture, design and implementation; cuts taglines, supporting text and secondary labels, and fixes the layout when the screen depended on them. Use when creating, reviewing, simplifying or…