Single, status-driven, non-interactive — paid/unpaid, success/warning/error, "Verificado", count indicator, category label inline with text. Often colored semantically, often with a dot. Sits next to a title or in a corner.

Not for clickable elements (use Chip if it needs interaction) or for a row of related selectable items (chips imply a group).

dark variant: promo only — site-wide offer strip, campaign announcement. accent variant: mostly promo + landing pages — softer marketing call-out, secondary promo strip.

Not for inline contextual info between content blocks (use InfoCallout). Don’t stack multiple Banners on one view — pick the most important.

Inline contextual info inside content — a tip or caveat near the thing it relates to. info tone for explainers ("We confirm by WhatsApp"), warning tone for cautions. The default for inline messages embedded between content blocks.

Not for help most users don’t need (use InfoPopover) or page-level system messages (use Banner).

On-demand "what’s this?" help triggered by a small ? or info icon next to a label. The answer is rare, optional, and shouldn’t take vertical space until asked.

Not for info every user needs to read (surface as InfoCallout) or as a label for a control (labels go inline).

Stack popovers next to every label — turns the page into a quiz.

In-place feedback for a single action or small region — button loading state, inline async operation, table cell refresh.

Not as a centered placeholder for a list/grid that has a known layout (that’s a Skeleton). Not for full-page route transitions (that’s LoadingPage).

Full-page route transitions before any content is renderable — initial app boot, gated route checks, hard data dependencies. The whole screen is empty until ready.

Not for in-page reloads (too heavy) or partial section loads (that’s a Skeleton).

Layout-known list/grid loads — cards, table rows, profile blocks. Mirrors the final layout so there’s no jump on load.

Not for unknown-shape content (use Spinner). Don’t render an empty Skeleton when data has loaded as empty — that’s an empty state.

Full-screen success after a multi-step flow — completed booking, sent quote, finished onboarding. Lives at the end of a FlowSheet flow with a single primary CTA out. The user has finished something — the screen marks it.

Not for routine actions (saved settings, copied link) or in-page confirmations that don’t deserve a full screen.

Stack a SuccessView after the user already saw a confirmation modal — pick one.