---
name: no-eyebrows
description: Polish website and app UI as a final step before handoff by removing decorative eyebrow labels and unnecessary narrative or instructions. Use after building or revising an interface, especially landing pages, sections, cards, dialogs, and scrollable areas.
---

# No eyebrows

Make the interface speak for itself in the final polish pass. Apply these rules across the UI being worked on, including repeated components and responsive layouts.

## Remove

- Eyebrows, kickers, section numbers, and small category labels placed above headings. Keep the actual heading and close the gap left by the removed label.
- Copy that narrates the interface or announces an implementation detail: “Scroll to see more,” “This box is scrollable,” “Click a card to open it,” “Use the tabs above,” and similar text.
- Filler captions, repeated headings, and explanatory sentences that restate what a nearby control, title, or visual already makes clear.
- UI text added solely because a feature was requested. If someone asks for horizontal scrolling, implement the scrolling; do not add a sentence telling visitors it scrolls.

## Keep the information people need

Preserve meaningful product content, control and field labels, useful data, error recovery, required disclosures, and accessibility names. Keep a brief instruction only when the action would otherwise be unclear or error-prone; first try to make the control or layout self-explanatory. Explicit copy requested by the user takes priority.

## Review the result

Search the affected screens and shared components for eyebrow patterns and narrator copy, including mobile states. Remove their wrappers and leftover spacing. Use hierarchy, placement, visible controls, and appropriate scroll affordances to communicate interaction. Do not replace deleted text with a new badge, subtitle, tooltip, or note that repeats the same message.