AI UX PlaygroundNewsletterJoin 2K+ AI designers and PMs on Substack. New teardowns, patterns, and prompts as they drop.

Onboarding

AI Tips & Tricks

Surface small, contextual hints for better prompts, features, or habits at the moment of need. Quiet nudges beat a tips dump nobody opens again.

Interactive demo

New chat · tips appear while the composer is empty

TIP · BE SPECIFIC

Name the audience, format, and length. Vague asks get vague drafts.

1 of 3

Overview

How might we surface small, contextual prompts for better AI usage without nagging people who already know the product?

When to use

  • ChatGPT, Copilot, Cursor, and Notion AI where empty composers or first actions benefit from brief guidance.
  • Surfaces where one concrete technique (be specific, show an example, one job per prompt) beats a help article.
  • Progressive onboarding: early sessions show more tips; frequency drops as people dismiss or demonstrate competence.
  • Products where tips attach to context (empty composer, first regenerate) instead of random pop-ups.

When to skip

  • Tips during errors when user needs fix steps only.
  • Repeating basics after proficiency signals.
  • Tips with no concrete example the user can try.

States

Design when tips appear and when they stop, not only the copy in the card.

  1. 01

    Contextual

    The product detects a teachable moment: empty composer, vague prompt, or first use of a feature.

  2. 02

    Shown

    A compact tip card appears near the relevant control. One idea, plain language, no modal takeover.

  3. 03

    Dismissed

    Close removes the current tip. The composer or workspace stays fully usable underneath.

  4. 04

    Next

    Optional rotation surfaces another tip. Pagination dots or Next tip avoid showing everything at once.

  5. 05

    Applied

    The person tries the suggested technique. Tips should not reappear immediately for the same behavior.

  6. 06

    Muted

    After repeated dismissals or mastery signals, tips suppress or move to an opt-in tips panel.

Key UX elements

The parts that must be present for contextual tips to feel helpful, not noisy.

Trigger

Show tips only on teachable moments.

Empty composer linger, first failure, or new feature use. Random tips on every page feel like ads.

Tip

One actionable idea per card.

Name the technique and why it helps. “Be specific” plus one line beats a paragraph of best practices.

Dismiss

Make close obvious and guilt-free.

An X or “Got it” should sit on the card. Dismissing must never block the primary task underneath.

Next

Rotate without overwhelming.

Dots or Next tip let curious users browse. Default to one tip per moment, not a carousel on every load.

Context

Anchor near the control being taught.

Tips belong beside the composer, suggestion row, or command palette they reference.

Progressive

Reduce frequency as people learn.

Track dismissals and successful patterns so tips back off for returning users instead of repeating forever.

Rules

  • Toast on every generation with generic advice.

  • Tips that open marketing blog tabs.

  • Same tip id shown ten times.

  • Blocking banner for non-critical optimization.

Evidence

ProductImplementation
ChatGPTInline suggestions on prompt quality and tools.
GitHub CopilotEditor tips on tests, docs, and chat usage.
Notion AIBlock-level hints after first AI use.
CursorComposer tips on @ symbols and agent modes.

FAQ

Are nudges and smart tooltips separate patterns?

No. Proactive nudges and progressive smart tooltips are presentation variants of AI Tips & Tricks. Tips teach technique; nudges push a specific next try; tooltips reveal guidance in place.

When show tips?

After success or stall moments, not mid-typing.

Personalize how?

Track accepted tips and increase depth over time.

Opt out?

Settings toggle for product education notifications.