<!-- ===== ui-patterns/CLAUDE.md ===== -->

# UI Patterns Namespace Instructions

This is a compiled namespace source under `pixi-vault/wikis/ui-patterns/`.

## Rules

- Follow the root `Wiki Compiler Maps/Namespace Wiki Compiler Map.md`.
- Preserve the UI Patterns source URL and copyright boundary on every imported page.
- Do not republish full source pattern bodies, screenshots, comments, or paid card-deck material.
- Use pattern pages as routing handles for design review and product critique.
- For exact wording/examples, retrieve the original source page and quote only bounded snippets when necessary.
- Update `wiki/index.md` and `wiki/log.md` whenever the import is refreshed.


<!-- ===== ui-patterns/README.md ===== -->

---
title: "UI Patterns"
created: "2026-07-02"
updated: "2026-07-02"
type: "namespace-overview"
status: "active"
category: "product-design"
namespace: "ui-patterns"
confidence: "medium"
source_url: "https://ui-patterns.com/patterns"
source_copyright_note: "UI Patterns site footer says All rights reserved; this namespace publishes a catalog/retrieval map, not full pattern text or screenshots."
---
# UI Patterns

> Product and persuasive interface pattern catalog for agents, compiled as a provenance-forward navigation layer over [ui-patterns.com](https://ui-patterns.com/patterns).

## Scope

### Covers

The `ui-patterns` namespace covers the public UI Patterns pattern catalog structure: pattern titles, source URLs, UI/persuasive taxonomy, section availability, example counts, provenance, copyright boundary, and agent-facing retrieval guidance for product/design review.

### Not Covered

This namespace does not republish full source pattern bodies, screenshots, comments, paid card-deck content, or commercial-clean training data. For exact wording and examples, retrieve the original source page and quote only bounded snippets when necessary.

### Current As

2026-07-02 — Initial import cataloged 170 pattern pages across 2 tracks and 11 groups from `https://ui-patterns.com/patterns`. Robots.txt allows `/patterns` crawling and disallows `/search`; the source footer says all rights reserved, so the public wiki remains a catalog and retrieval map.

## Canonical Source Roots

- Pattern index: `https://ui-patterns.com/patterns`
- Source site: `https://ui-patterns.com`
- Robots policy checked: `https://ui-patterns.com/robots.txt`
- Retrieved at: `2026-07-02T18:23:09+00:00`

## Agent Use Contract

- Start with [[summaries/for-agents-ui-patterns-retrieval|For Agents — UI Patterns Retrieval]].
- Search by pattern title, group, subgroup, or track.
- Open the source URL before relying on exact source wording, screenshot details, or nuanced usage limits.
- Treat this namespace as a design-review routing layer, not a license to bulk-copy the source site.
- Cite the source URL and this namespace page when turning a pattern into product recommendations.

## Public Output Contract

When published to `pixi-wiki`, this namespace should expose:

```text
/raw/ui-patterns/README.md
/raw/ui-patterns/wiki/index.md
/wiki/ui-patterns/README.md.html
/wiki/ui-patterns/wiki/index.md.html
/wiki/ui-patterns/llms.txt
```


<!-- ===== ui-patterns/wiki/concepts/patterns/accordion-menu.md ===== -->

---
title: "Accordion Menu"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/AccordionMenu"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/AccordionMenu"
source_slug: "AccordionMenu"
track: "User Interface Design Patterns"
group: "Navigation"
subgroup: "Menus"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 11
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Accordion Menu

> Catalog pointer for the UI Patterns source page: [Accordion Menu](https://ui-patterns.com/patterns/AccordionMenu).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Navigation
- Subgroup: Menus
- Source breadcrumb: Design Patterns > Navigation > Menus > Accordion Menu

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/AccordionMenu
- Page title: Accordion Menu design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 11
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 22 words on source page
- Example: 62 words on source page
- Usage: 61 words on source page
- Solution: 72 words on source page
- Rationale: 75 words on source page

## Source Navigation

- Previous source navigation: Horizontal Dropdown Menu
- Next source navigation: Forgiving Format


<!-- ===== ui-patterns/wiki/concepts/patterns/account-registration.md ===== -->

---
title: "Account Registration"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/AccountRegistration"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/AccountRegistration"
source_slug: "AccountRegistration"
track: "User Interface Design Patterns"
group: "Onboarding"
subgroup: "Registration"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
  - "Discussion"
  - "Is account registration necessary? And when?"
  - "Why should the user register?"
  - "Asking too many (unnecessary) questions"
example_count: 13
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Account Registration

> Catalog pointer for the UI Patterns source page: [Account Registration](https://ui-patterns.com/patterns/AccountRegistration).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Onboarding
- Subgroup: Registration
- Source breadcrumb: Design Patterns > Onboarding > Registration > Account Registration

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/AccountRegistration
- Page title: Account Registration design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale, Discussion, Is account registration necessary? And when?, Why should the user register?, Asking too many (unnecessary) questions
- Example screenshots detected at source: 13
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 21 words on source page
- Example: 96 words on source page
- Usage: 69 words on source page
- Solution: 355 words on source page
- Rationale: 120 words on source page
- Discussion: 454 words on source page
- Is account registration necessary? And when?: 178 words on source page
- Why should the user register?: 94 words on source page
- Asking too many (unnecessary) questions: 156 words on source page

## Source Navigation

- Previous source navigation: Vote To Promote
- Next source navigation: Input Feedback


<!-- ===== ui-patterns/wiki/concepts/patterns/achievements.md ===== -->

---
title: "Achievements"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Achievements"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Achievements"
source_slug: "Achievements"
track: "Persuasive Design Patterns"
group: "Game mechanics"
subgroup: "Gameplay rewards"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
  - "Why do achievements work?"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Achievements

> Catalog pointer for the UI Patterns source page: [Achievements](https://ui-patterns.com/patterns/Achievements).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Game mechanics
- Subgroup: Gameplay rewards
- Source breadcrumb: Design Patterns > Game mechanics > Gameplay rewards > Achievements

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Achievements
- Page title: Achievements design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale, Why do achievements work?
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 81 words on source page
- Usage: 69 words on source page
- Solution: 165 words on source page
- Rationale: 616 words on source page
- Why do achievements work?: 407 words on source page

## Source Navigation

- Previous source navigation: Value Attribution
- Next source navigation: Trigger


<!-- ===== ui-patterns/wiki/concepts/patterns/activity-stream.md ===== -->

---
title: "Activity Stream"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/ActivityStream"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/ActivityStream"
source_slug: "ActivityStream"
track: "User Interface Design Patterns"
group: "Social"
subgroup: "Social interactions"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "The details of an activity stream"
  - "Aggregated activities"
  - "Verbs"
  - "Rationale"
  - "Discussion"
  - "Avoiding negatives"
  - "Keeping it relevant"
  - "Activity streams attract momentary action"
  - "Make it easy to scan"
example_count: 13
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Activity Stream

> Catalog pointer for the UI Patterns source page: [Activity Stream](https://ui-patterns.com/patterns/ActivityStream).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Social
- Subgroup: Social interactions
- Source breadcrumb: Design Patterns > Social > Social interactions > Activity Stream

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/ActivityStream
- Page title: Activity Stream design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, The details of an activity stream, Aggregated activities, Verbs, Rationale, Discussion, Avoiding negatives, Keeping it relevant, Activity streams attract momentary action, Make it easy to scan
- Example screenshots detected at source: 13
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 21 words on source page
- Example: 85 words on source page
- Usage: 79 words on source page
- Solution: 334 words on source page
- The details of an activity stream: 35 words on source page
- Aggregated activities: 44 words on source page
- Verbs: 15 words on source page
- Rationale: 189 words on source page
- Discussion: 435 words on source page
- Avoiding negatives: 51 words on source page
- Keeping it relevant: 95 words on source page
- Activity streams attract momentary action: 133 words on source page
- Make it easy to scan: 87 words on source page

## Source Navigation

- Previous source navigation: Progressive Disclosure
- Next source navigation: Calendar Picker


<!-- ===== ui-patterns/wiki/concepts/patterns/adaptable-view.md ===== -->

---
title: "Adaptable View"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/AdaptableView"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/AdaptableView"
source_slug: "AdaptableView"
track: "User Interface Design Patterns"
group: "Navigation"
subgroup: "Content"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
  - "Discussion"
example_count: 4
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Adaptable View

> Catalog pointer for the UI Patterns source page: [Adaptable View](https://ui-patterns.com/patterns/AdaptableView).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Navigation
- Subgroup: Content
- Source breadcrumb: Design Patterns > Navigation > Content > Adaptable View

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/AdaptableView
- Page title: Adaptable View design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale, Discussion
- Example screenshots detected at source: 4
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 17 words on source page
- Example: 140 words on source page
- Usage: 132 words on source page
- Solution: 162 words on source page
- Rationale: 30 words on source page
- Discussion: 173 words on source page

## Source Navigation

- Previous source navigation: Image Zoom
- Next source navigation: Wizard


<!-- ===== ui-patterns/wiki/concepts/patterns/alternating-row-colors.md ===== -->

---
title: "Alternating Row Colors"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/AlternatingRowColors"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/AlternatingRowColors"
source_slug: "AlternatingRowColors"
track: "User Interface Design Patterns"
group: "Dealing with data"
subgroup: "Tables"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 7
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Alternating Row Colors

> Catalog pointer for the UI Patterns source page: [Alternating Row Colors](https://ui-patterns.com/patterns/AlternatingRowColors).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Dealing with data
- Subgroup: Tables
- Source breadcrumb: Design Patterns > Dealing with data > Tables > Alternating Row Colors

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/AlternatingRowColors
- Page title: Alternating Row Colors design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 7
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 22 words on source page
- Example: 39 words on source page
- Usage: 38 words on source page
- Solution: 74 words on source page
- Rationale: 96 words on source page

## Source Navigation

- Previous source navigation: Sort By Column
- Next source navigation: Copy Box


<!-- ===== ui-patterns/wiki/concepts/patterns/anchoring.md ===== -->

---
title: "Anchoring"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Anchoring"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Anchoring"
source_slug: "Anchoring"
track: "Persuasive Design Patterns"
group: "Perception and memory"
subgroup: "Comprehension"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
  - "Discussion"
  - "Contrast anchoring"
  - "Assimilation anchoring"
  - "What qualifies as an anchor"
example_count: 11
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Anchoring

> Catalog pointer for the UI Patterns source page: [Anchoring](https://ui-patterns.com/patterns/Anchoring).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Perception and memory
- Subgroup: Comprehension
- Source breadcrumb: Design Patterns > Perception and memory > Comprehension > Anchoring

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Anchoring
- Page title: Anchoring design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale, Discussion, Contrast anchoring, Assimilation anchoring, What qualifies as an anchor
- Example screenshots detected at source: 11
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 11 words on source page
- Example: 51 words on source page
- Usage: 35 words on source page
- Solution: 198 words on source page
- Rationale: 253 words on source page
- Discussion: 281 words on source page
- Contrast anchoring: 31 words on source page
- Assimilation anchoring: 44 words on source page
- What qualifies as an anchor: 27 words on source page

## Source Navigation

- Previous source navigation: Tunnelling
- Next source navigation: Serial Positioning Effect


<!-- ===== ui-patterns/wiki/concepts/patterns/appointment-dynamic.md ===== -->

---
title: "Appointment Dynamic"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/appointment-dynamic"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/appointment-dynamic"
source_slug: "appointment-dynamic"
track: "Persuasive Design Patterns"
group: "Game mechanics"
subgroup: "Gameplay rewards"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Appointment Dynamic

> Catalog pointer for the UI Patterns source page: [Appointment Dynamic](https://ui-patterns.com/patterns/appointment-dynamic).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Game mechanics
- Subgroup: Gameplay rewards
- Source breadcrumb: Design Patterns > Game mechanics > Gameplay rewards > Appointment Dynamic

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/appointment-dynamic
- Page title: Appointment Dynamic design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 57 words on source page
- Usage: 39 words on source page
- Solution: 123 words on source page
- Rationale: 149 words on source page

## Source Navigation

- Previous source navigation: Halo Effect
- Next source navigation: Autonomy


<!-- ===== ui-patterns/wiki/concepts/patterns/appropriate-challenge.md ===== -->

---
title: "Appropriate Challenge"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Appropriate-challenge"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Appropriate-challenge"
source_slug: "Appropriate-challenge"
track: "Persuasive Design Patterns"
group: "Game mechanics"
subgroup: "Gameplay design"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 4
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Appropriate Challenge

> Catalog pointer for the UI Patterns source page: [Appropriate Challenge](https://ui-patterns.com/patterns/Appropriate-challenge).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Game mechanics
- Subgroup: Gameplay design
- Source breadcrumb: Design Patterns > Game mechanics > Gameplay design > Appropriate Challenge

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Appropriate-challenge
- Page title: Appropriate Challenge design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 4
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 8 words on source page
- Example: 43 words on source page
- Usage: 42 words on source page
- Solution: 269 words on source page
- Rationale: 435 words on source page

## Source Navigation

- Previous source navigation: Cognitive Dissonance
- Next source navigation: Drag and drop


<!-- ===== ui-patterns/wiki/concepts/patterns/archive.md ===== -->

---
title: "Archive"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Archive"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Archive"
source_slug: "Archive"
track: "User Interface Design Patterns"
group: "Navigation"
subgroup: "Content"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 13
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Archive

> Catalog pointer for the UI Patterns source page: [Archive](https://ui-patterns.com/patterns/Archive).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Navigation
- Subgroup: Content
- Source breadcrumb: Design Patterns > Navigation > Content > Archive

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Archive
- Page title: Archive design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 13
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 14 words on source page
- Example: 87 words on source page
- Usage: 86 words on source page
- Solution: 94 words on source page
- Rationale: 53 words on source page

## Source Navigation

- Previous source navigation: Pagination
- Next source navigation: Search Filters


<!-- ===== ui-patterns/wiki/concepts/patterns/article-list.md ===== -->

---
title: "Article List"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/ArticleList"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/ArticleList"
source_slug: "ArticleList"
track: "User Interface Design Patterns"
group: "Navigation"
subgroup: "Content"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Design tips for designing great article lists"
  - "Common pitfalls of article list design"
  - "The elements of an article list item"
  - "Rationale"
  - "Discussion"
  - "Think from the user’s perspective – not your own"
example_count: 17
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Article List

> Catalog pointer for the UI Patterns source page: [Article List](https://ui-patterns.com/patterns/ArticleList).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Navigation
- Subgroup: Content
- Source breadcrumb: Design Patterns > Navigation > Content > Article List

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/ArticleList
- Page title: Article List design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Design tips for designing great article lists, Common pitfalls of article list design, The elements of an article list item, Rationale, Discussion, Think from the user’s perspective – not your own
- Example screenshots detected at source: 17
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 17 words on source page
- Example: 92 words on source page
- Usage: 68 words on source page
- Solution: 1396 words on source page
- Design tips for designing great article lists: 1031 words on source page
- Common pitfalls of article list design: 147 words on source page
- The elements of an article list item: 132 words on source page
- Rationale: 77 words on source page
- Discussion: 146 words on source page
- Think from the user’s perspective – not your own: 135 words on source page

## Source Navigation

- Previous source navigation: Autocomplete
- Next source navigation: Event Calendar


<!-- ===== ui-patterns/wiki/concepts/patterns/authority-bias.md ===== -->

---
title: "Authority Bias"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Authority"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Authority"
source_slug: "Authority"
track: "Persuasive Design Patterns"
group: "Social"
subgroup: "Social biases"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Communicate authority"
  - "Rationale"
  - "Identifying with Authority Figures"
  - "Discussion"
  - "The study"
  - "Powerful pairings"
  - "Ethical Recommendations"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Authority Bias

> Catalog pointer for the UI Patterns source page: [Authority Bias](https://ui-patterns.com/patterns/Authority).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Social
- Subgroup: Social biases
- Source breadcrumb: Design Patterns > Social > Social biases > Authority Bias

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Authority
- Page title: Authority Bias design pattern
- Section headings available at source: Problem summary, Usage, Solution, Communicate authority, Rationale, Identifying with Authority Figures, Discussion, The study, Powerful pairings, Ethical Recommendations
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 194 words on source page
- Usage: 183 words on source page
- Solution: 237 words on source page
- Communicate authority: 146 words on source page
- Rationale: 471 words on source page
- Identifying with Authority Figures: 235 words on source page
- Discussion: 1148 words on source page
- The study: 88 words on source page
- Powerful pairings: 249 words on source page
- Ethical Recommendations: 335 words on source page

## Source Navigation

- Previous source navigation: Goal-Gradient Effect
- Next source navigation: Tailoring


<!-- ===== ui-patterns/wiki/concepts/patterns/auto-sharing.md ===== -->

---
title: "Auto-sharing"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/auto-sharing"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/auto-sharing"
source_slug: "auto-sharing"
track: "User Interface Design Patterns"
group: "Social"
subgroup: "Social interactions"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 1
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Auto-sharing

> Catalog pointer for the UI Patterns source page: [Auto-sharing](https://ui-patterns.com/patterns/auto-sharing).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Social
- Subgroup: Social interactions
- Source breadcrumb: Design Patterns > Social > Social interactions > Auto-sharing

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/auto-sharing
- Page title: Auto-sharing design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 1
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 12 words on source page
- Example: 79 words on source page
- Usage: 60 words on source page
- Solution: 59 words on source page
- Rationale: 81 words on source page

## Source Navigation

- Previous source navigation: Testimonials
- Next source navigation: Invite friends


<!-- ===== ui-patterns/wiki/concepts/patterns/autocomplete.md ===== -->

---
title: "Autocomplete"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Autocomplete"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Autocomplete"
source_slug: "Autocomplete"
track: "User Interface Design Patterns"
group: "Dealing with data"
subgroup: "Search"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Implementation details"
  - "Rationale"
  - "Discussion"
example_count: 13
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Autocomplete

> Catalog pointer for the UI Patterns source page: [Autocomplete](https://ui-patterns.com/patterns/Autocomplete).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Dealing with data
- Subgroup: Search
- Source breadcrumb: Design Patterns > Dealing with data > Search > Autocomplete

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Autocomplete
- Page title: Autocomplete design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Implementation details, Rationale, Discussion
- Example screenshots detected at source: 13
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 18 words on source page
- Example: 139 words on source page
- Usage: 132 words on source page
- Solution: 369 words on source page
- Implementation details: 154 words on source page
- Rationale: 270 words on source page
- Discussion: 105 words on source page

## Source Navigation

- Previous source navigation: Calendar Picker
- Next source navigation: Article List


<!-- ===== ui-patterns/wiki/concepts/patterns/autonomy.md ===== -->

---
title: "Autonomy"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/autonomy"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/autonomy"
source_slug: "autonomy"
track: "Persuasive Design Patterns"
group: "Social"
subgroup: "Social biases"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Autonomy

> Catalog pointer for the UI Patterns source page: [Autonomy](https://ui-patterns.com/patterns/autonomy).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Social
- Subgroup: Social biases
- Source breadcrumb: Design Patterns > Social > Social biases > Autonomy

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/autonomy
- Page title: Autonomy design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 38 words on source page
- Usage: 31 words on source page
- Solution: 133 words on source page
- Rationale: 158 words on source page

## Source Navigation

- Previous source navigation: Appointment Dynamic
- Next source navigation: Fresh Start Effect


<!-- ===== ui-patterns/wiki/concepts/patterns/autosave.md ===== -->

---
title: "Autosave"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/autosave"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/autosave"
source_slug: "autosave"
track: "User Interface Design Patterns"
group: "Getting input"
subgroup: "Forms"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "The save button"
  - "Rationale"
  - "Discussion"
example_count: 1
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Autosave

> Catalog pointer for the UI Patterns source page: [Autosave](https://ui-patterns.com/patterns/autosave).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Getting input
- Subgroup: Forms
- Source breadcrumb: Design Patterns > Getting input > Forms > Autosave

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/autosave
- Page title: Autosave design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, The save button, Rationale, Discussion
- Example screenshots detected at source: 1
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 21 words on source page
- Example: 24 words on source page
- Usage: 23 words on source page
- Solution: 113 words on source page
- The save button: 41 words on source page
- Rationale: 45 words on source page
- Discussion: 67 words on source page

## Source Navigation

- Previous source navigation: Flagging & Reporting
- Next source navigation: Morphing Controls


<!-- ===== ui-patterns/wiki/concepts/patterns/blank-slate.md ===== -->

---
title: "Blank Slate"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/BlankSlate"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/BlankSlate"
source_slug: "BlankSlate"
track: "User Interface Design Patterns"
group: "Onboarding"
subgroup: "Guidance"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 13
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Blank Slate

> Catalog pointer for the UI Patterns source page: [Blank Slate](https://ui-patterns.com/patterns/BlankSlate).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Onboarding
- Subgroup: Guidance
- Source breadcrumb: Design Patterns > Onboarding > Guidance > Blank Slate

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/BlankSlate
- Page title: Blank Slate design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 13
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 35 words on source page
- Example: 102 words on source page
- Usage: 78 words on source page
- Solution: 157 words on source page
- Rationale: 139 words on source page

## Source Navigation

- Previous source navigation: Shopping Cart
- Next source navigation: Continuous Scrolling


<!-- ===== ui-patterns/wiki/concepts/patterns/breadcrumbs.md ===== -->

---
title: "Breadcrumbs"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Breadcrumbs"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Breadcrumbs"
source_slug: "Breadcrumbs"
track: "User Interface Design Patterns"
group: "Navigation"
subgroup: "Jumping in hierarchy"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 13
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Breadcrumbs

> Catalog pointer for the UI Patterns source page: [Breadcrumbs](https://ui-patterns.com/patterns/Breadcrumbs).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Navigation
- Subgroup: Jumping in hierarchy
- Source breadcrumb: Design Patterns > Navigation > Jumping in hierarchy > Breadcrumbs

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Breadcrumbs
- Page title: Breadcrumbs design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 13
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 26 words on source page
- Example: 155 words on source page
- Usage: 139 words on source page
- Solution: 95 words on source page
- Rationale: 152 words on source page

## Source Navigation

- Previous source navigation: Navigation Tabs
- Next source navigation: Shortcut Dropdown


<!-- ===== ui-patterns/wiki/concepts/patterns/calendar-picker.md ===== -->

---
title: "Calendar Picker"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/CalendarPicker"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/CalendarPicker"
source_slug: "CalendarPicker"
track: "User Interface Design Patterns"
group: "Getting input"
subgroup: "Forms"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Shortcuts"
  - "Locking-in the period of selection"
  - "Two ways of inputting data: speedy and easy"
  - "Good defaults"
  - "Check date range validity"
  - "Display complete weeks"
  - "Make link targets big"
  - "Rationale"
  - "Discussion"
  - "International considerations"
example_count: 8
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Calendar Picker

> Catalog pointer for the UI Patterns source page: [Calendar Picker](https://ui-patterns.com/patterns/CalendarPicker).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Getting input
- Subgroup: Forms
- Source breadcrumb: Design Patterns > Getting input > Forms > Calendar Picker

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/CalendarPicker
- Page title: Calendar Picker design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Shortcuts, Locking-in the period of selection, Two ways of inputting data: speedy and easy, Good defaults, Check date range validity, Display complete weeks, Make link targets big, Rationale, Discussion, International considerations
- Example screenshots detected at source: 8
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 15 words on source page
- Example: 95 words on source page
- Usage: 87 words on source page
- Solution: 487 words on source page
- Shortcuts: 41 words on source page
- Locking-in the period of selection: 39 words on source page
- Two ways of inputting data: speedy and easy: 109 words on source page
- Good defaults: 77 words on source page
- Check date range validity: 45 words on source page
- Display complete weeks: 32 words on source page
- Make link targets big: 13 words on source page
- Rationale: 33 words on source page
- Discussion: 94 words on source page
- International considerations: 82 words on source page

## Source Navigation

- Previous source navigation: Activity Stream
- Next source navigation: Autocomplete


<!-- ===== ui-patterns/wiki/concepts/patterns/captcha.md ===== -->

---
title: "Captcha"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Captcha"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Captcha"
source_slug: "Captcha"
track: "User Interface Design Patterns"
group: "Getting input"
subgroup: "Forms"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 13
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Captcha

> Catalog pointer for the UI Patterns source page: [Captcha](https://ui-patterns.com/patterns/Captcha).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Getting input
- Subgroup: Forms
- Source breadcrumb: Design Patterns > Getting input > Forms > Captcha

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Captcha
- Page title: Captcha design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 13
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 18 words on source page
- Example: 172 words on source page
- Usage: 171 words on source page
- Solution: 121 words on source page
- Rationale: 135 words on source page

## Source Navigation

- Previous source navigation: Good Defaults
- Next source navigation: Sort By Column


<!-- ===== ui-patterns/wiki/concepts/patterns/cards.md ===== -->

---
title: "Cards"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/cards"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/cards"
source_slug: "cards"
track: "User Interface Design Patterns"
group: "Navigation"
subgroup: "Content"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Cards can be manipulated"
  - "Rationale"
  - "Why use cards?"
  - "Discussion"
  - "When to use cards"
  - "When you shouldn’t use cards"
  - "The problem of visual overload"
  - "How to improve design and interaction with cards"
  - "Cards design and visual signifiers"
example_count: 11
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Cards

> Catalog pointer for the UI Patterns source page: [Cards](https://ui-patterns.com/patterns/cards).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Navigation
- Subgroup: Content
- Source breadcrumb: Design Patterns > Navigation > Content > Cards

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/cards
- Page title: Cards design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Cards can be manipulated, Rationale, Why use cards?, Discussion, When to use cards, When you shouldn’t use cards, The problem of visual overload, How to improve design and interaction with cards, Cards design and visual signifiers
- Example screenshots detected at source: 11
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 11 words on source page
- Example: 152 words on source page
- Usage: 128 words on source page
- Solution: 186 words on source page
- Cards can be manipulated: 81 words on source page
- Rationale: 410 words on source page
- Why use cards?: 263 words on source page
- Discussion: 1065 words on source page
- When to use cards: 250 words on source page
- When you shouldn’t use cards: 194 words on source page
- The problem of visual overload: 47 words on source page
- How to improve design and interaction with cards: 369 words on source page
- Cards design and visual signifiers: 73 words on source page

## Source Navigation

- Previous source navigation: Drag and drop
- Next source navigation: Retaliation


<!-- ===== ui-patterns/wiki/concepts/patterns/carousel.md ===== -->

---
title: "Carousel"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Carousel"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Carousel"
source_slug: "Carousel"
track: "User Interface Design Patterns"
group: "Navigation"
subgroup: "Content"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 13
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Carousel

> Catalog pointer for the UI Patterns source page: [Carousel](https://ui-patterns.com/patterns/Carousel).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Navigation
- Subgroup: Content
- Source breadcrumb: Design Patterns > Navigation > Content > Carousel

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Carousel
- Page title: Carousel design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 13
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 16 words on source page
- Example: 121 words on source page
- Usage: 120 words on source page
- Solution: 123 words on source page
- Rationale: 123 words on source page

## Source Navigation

- Previous source navigation: Table Filter
- Next source navigation: Coupon


<!-- ===== ui-patterns/wiki/concepts/patterns/cashless-effect.md ===== -->

---
title: "Cashless Effect"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/cashless-effect"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/cashless-effect"
source_slug: "cashless-effect"
track: "Persuasive Design Patterns"
group: "Cognition"
subgroup: "Other cognitive biases"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Cashless Effect

> Catalog pointer for the UI Patterns source page: [Cashless Effect](https://ui-patterns.com/patterns/cashless-effect).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Cognition
- Subgroup: Other cognitive biases
- Source breadcrumb: Design Patterns > Cognition > Other cognitive biases > Cashless Effect

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/cashless-effect
- Page title: Cashless Effect design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 20 words on source page
- Usage: 8 words on source page
- Solution: 109 words on source page
- Rationale: 216 words on source page

## Source Navigation

- Previous source navigation: Zeigarnik Effect
- Next source navigation: Picture Superiority Effect


<!-- ===== ui-patterns/wiki/concepts/patterns/categorization.md ===== -->

---
title: "Categorization"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/categorization"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/categorization"
source_slug: "categorization"
track: "User Interface Design Patterns"
group: "Navigation"
subgroup: "Content"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 2
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Categorization

> Catalog pointer for the UI Patterns source page: [Categorization](https://ui-patterns.com/patterns/categorization).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Navigation
- Subgroup: Content
- Source breadcrumb: Design Patterns > Navigation > Content > Categorization

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/categorization
- Page title: Categorization design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 2
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 15 words on source page
- Example: 42 words on source page
- Usage: 16 words on source page
- Solution: 30 words on source page
- Rationale: 105 words on source page

## Source Navigation

- Previous source navigation: Frequently Asked Questions (FAQ)
- Next source navigation: Pull to refresh


<!-- ===== ui-patterns/wiki/concepts/patterns/chat.md ===== -->

---
title: "Chat"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/direct-messaging"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/direct-messaging"
source_slug: "direct-messaging"
track: "User Interface Design Patterns"
group: "Social"
subgroup: "Social interactions"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 2
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Chat

> Catalog pointer for the UI Patterns source page: [Chat](https://ui-patterns.com/patterns/direct-messaging).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Social
- Subgroup: Social interactions
- Source breadcrumb: Design Patterns > Social > Social interactions > Chat

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/direct-messaging
- Page title: Chat design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 2
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 15 words on source page
- Example: 62 words on source page
- Usage: 51 words on source page
- Solution: 77 words on source page
- Rationale: 46 words on source page

## Source Navigation

- Previous source navigation: Testimonials
- Next source navigation: Invite friends


<!-- ===== ui-patterns/wiki/concepts/patterns/choice-closure.md ===== -->

---
title: "Choice Closure"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/choice-closure"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/choice-closure"
source_slug: "choice-closure"
track: "Persuasive Design Patterns"
group: "Cognition"
subgroup: "Other cognitive biases"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Choice Closure

> Catalog pointer for the UI Patterns source page: [Choice Closure](https://ui-patterns.com/patterns/choice-closure).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Cognition
- Subgroup: Other cognitive biases
- Source breadcrumb: Design Patterns > Cognition > Other cognitive biases > Choice Closure

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/choice-closure
- Page title: Choice Closure design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 41 words on source page
- Usage: 26 words on source page
- Solution: 158 words on source page
- Rationale: 160 words on source page

## Source Navigation

- Previous source navigation: Zeigarnik Effect
- Next source navigation: Picture Superiority Effect


<!-- ===== ui-patterns/wiki/concepts/patterns/chunking.md ===== -->

---
title: "Chunking"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Chunking"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Chunking"
source_slug: "Chunking"
track: "Persuasive Design Patterns"
group: "Perception and memory"
subgroup: "Comprehension"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "How far should I chunk – and what?"
  - "So always 4 to 5 menu items?"
  - "When to chunk…"
  - "Rationale"
example_count: 1
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Chunking

> Catalog pointer for the UI Patterns source page: [Chunking](https://ui-patterns.com/patterns/Chunking).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Perception and memory
- Subgroup: Comprehension
- Source breadcrumb: Design Patterns > Perception and memory > Comprehension > Chunking

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Chunking
- Page title: Chunking design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, How far should I chunk – and what?, So always 4 to 5 menu items?, When to chunk…, Rationale
- Example screenshots detected at source: 1
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 12 words on source page
- Example: 119 words on source page
- Usage: 70 words on source page
- Solution: 454 words on source page
- How far should I chunk – and what?: 62 words on source page
- So always 4 to 5 menu items?: 57 words on source page
- When to chunk…: 192 words on source page
- Rationale: 237 words on source page

## Source Navigation

- Previous source navigation: Tunnelling
- Next source navigation: Serial Positioning Effect


<!-- ===== ui-patterns/wiki/concepts/patterns/coachmarks.md ===== -->

---
title: "Coachmarks"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/coachmarks"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/coachmarks"
source_slug: "coachmarks"
track: "User Interface Design Patterns"
group: "Onboarding"
subgroup: "Guidance"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
  - "Discussion"
  - "Address underlying issues first"
example_count: 5
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Coachmarks

> Catalog pointer for the UI Patterns source page: [Coachmarks](https://ui-patterns.com/patterns/coachmarks).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Onboarding
- Subgroup: Guidance
- Source breadcrumb: Design Patterns > Onboarding > Guidance > Coachmarks

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/coachmarks
- Page title: Coachmarks design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale, Discussion, Address underlying issues first
- Example screenshots detected at source: 5
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 10 words on source page
- Example: 18 words on source page
- Solution: 46 words on source page
- Rationale: 33 words on source page
- Discussion: 273 words on source page
- Address underlying issues first: 106 words on source page

## Source Navigation

- Previous source navigation: Flagging & Reporting
- Next source navigation: Morphing Controls


<!-- ===== ui-patterns/wiki/concepts/patterns/cognitive-dissonance.md ===== -->

---
title: "Cognitive Dissonance"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/cognitive-dissonance"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/cognitive-dissonance"
source_slug: "cognitive-dissonance"
track: "Persuasive Design Patterns"
group: "Social"
subgroup: "Social biases"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Strategies"
  - "Rationale"
  - "Discussion"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Cognitive Dissonance

> Catalog pointer for the UI Patterns source page: [Cognitive Dissonance](https://ui-patterns.com/patterns/cognitive-dissonance).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Social
- Subgroup: Social biases
- Source breadcrumb: Design Patterns > Social > Social biases > Cognitive Dissonance

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/cognitive-dissonance
- Page title: Cognitive Dissonance design pattern
- Section headings available at source: Problem summary, Usage, Solution, Strategies, Rationale, Discussion
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 346 words on source page
- Usage: 329 words on source page
- Solution: 841 words on source page
- Strategies: 644 words on source page
- Rationale: 158 words on source page
- Discussion: 406 words on source page

## Source Navigation

- Previous source navigation: Modal
- Next source navigation: Appropriate Challenge


<!-- ===== ui-patterns/wiki/concepts/patterns/collectible-achievements.md ===== -->

---
title: "Collectible Achievements"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/CollectibleAchievements"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/CollectibleAchievements"
source_slug: "CollectibleAchievements"
track: "User Interface Design Patterns"
group: "Social"
subgroup: "Reputation"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Families of collectibles"
  - "It should be attractive to be rewarded"
  - "Combine easy successes with hard challenges"
  - "Types of achievements"
  - "What are you awarding?"
  - "Rationale"
  - "Discussion"
  - "Quality"
  - "Get people started"
  - "Is it mine forever?"
  - "Fraud"
example_count: 13
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Collectible Achievements

> Catalog pointer for the UI Patterns source page: [Collectible Achievements](https://ui-patterns.com/patterns/CollectibleAchievements).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Social
- Subgroup: Reputation
- Source breadcrumb: Design Patterns > Social > Reputation > Collectible Achievements

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/CollectibleAchievements
- Page title: Collectible Achievements design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Families of collectibles, It should be attractive to be rewarded, Combine easy successes with hard challenges, Types of achievements, What are you awarding?, Rationale, Discussion, Quality, Get people started, Is it mine forever?, Fraud
- Example screenshots detected at source: 13
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 25 words on source page
- Example: 161 words on source page
- Usage: 139 words on source page
- Solution: 887 words on source page
- Families of collectibles: 130 words on source page
- It should be attractive to be rewarded: 144 words on source page
- Combine easy successes with hard challenges: 70 words on source page
- Types of achievements: 370 words on source page
- What are you awarding?: 92 words on source page
- Rationale: 141 words on source page
- Discussion: 688 words on source page
- Quality: 357 words on source page
- Get people started: 40 words on source page
- Is it mine forever?: 92 words on source page
- Fraud: 85 words on source page

## Source Navigation

- Previous source navigation: Completeness meter
- Next source navigation: Progressive Disclosure


<!-- ===== ui-patterns/wiki/concepts/patterns/commitment-and-consistency.md ===== -->

---
title: "Commitment & Consistency"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Commitment-consistency"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Commitment-consistency"
source_slug: "Commitment-consistency"
track: "Persuasive Design Patterns"
group: "Social"
subgroup: "Social biases"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Getting commitments to work"
  - "Getting it Right"
  - "Rationale"
  - "Discussion"
example_count: 1
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Commitment & Consistency

> Catalog pointer for the UI Patterns source page: [Commitment & Consistency](https://ui-patterns.com/patterns/Commitment-consistency).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Social
- Subgroup: Social biases
- Source breadcrumb: Design Patterns > Social > Social biases > Commitment & Consistency

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Commitment-consistency
- Page title: Commitment & Consistency design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Getting commitments to work, Getting it Right, Rationale, Discussion
- Example screenshots detected at source: 1
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 19 words on source page
- Example: 73 words on source page
- Usage: 28 words on source page
- Solution: 562 words on source page
- Getting commitments to work: 93 words on source page
- Getting it Right: 244 words on source page
- Rationale: 221 words on source page
- Discussion: 352 words on source page

## Source Navigation

- Previous source navigation: Cognitive Dissonance
- Next source navigation: Drag and drop


<!-- ===== ui-patterns/wiki/concepts/patterns/competition.md ===== -->

---
title: "Competition"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Competition"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Competition"
source_slug: "Competition"
track: "Persuasive Design Patterns"
group: "Social"
subgroup: "Social biases"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
  - "Discussion"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Competition

> Catalog pointer for the UI Patterns source page: [Competition](https://ui-patterns.com/patterns/Competition).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Social
- Subgroup: Social biases
- Source breadcrumb: Design Patterns > Social > Social biases > Competition

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Competition
- Page title: Competition design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale, Discussion
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 25 words on source page
- Usage: 9 words on source page
- Solution: 117 words on source page
- Rationale: 64 words on source page
- Discussion: 83 words on source page

## Source Navigation

- Previous source navigation: Sequencing
- Next source navigation: Pricing table


<!-- ===== ui-patterns/wiki/concepts/patterns/completeness-meter.md ===== -->

---
title: "Completeness meter"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/CompletenessMeter"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/CompletenessMeter"
source_slug: "CompletenessMeter"
track: "User Interface Design Patterns"
group: "Getting input"
subgroup: "Explaining the process"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
  - "Discussion"
example_count: 13
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Completeness meter

> Catalog pointer for the UI Patterns source page: [Completeness meter](https://ui-patterns.com/patterns/CompletenessMeter).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Getting input
- Subgroup: Explaining the process
- Source breadcrumb: Design Patterns > Getting input > Explaining the process > Completeness meter

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/CompletenessMeter
- Page title: Completeness meter design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale, Discussion
- Example screenshots detected at source: 13
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 20 words on source page
- Example: 104 words on source page
- Usage: 89 words on source page
- Solution: 224 words on source page
- Rationale: 104 words on source page
- Discussion: 101 words on source page

## Source Navigation

- Previous source navigation: Wizard
- Next source navigation: Collectible Achievements


<!-- ===== ui-patterns/wiki/concepts/patterns/conceptual-metaphor.md ===== -->

---
title: "Conceptual Metaphor"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Conceptual-metaphor"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Conceptual-metaphor"
source_slug: "Conceptual-metaphor"
track: "Persuasive Design Patterns"
group: "Perception and memory"
subgroup: "Comprehension"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Conceptual Metaphor

> Catalog pointer for the UI Patterns source page: [Conceptual Metaphor](https://ui-patterns.com/patterns/Conceptual-metaphor).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Perception and memory
- Subgroup: Comprehension
- Source breadcrumb: Design Patterns > Perception and memory > Comprehension > Conceptual Metaphor

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Conceptual-metaphor
- Page title: Conceptual Metaphor design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 36 words on source page
- Usage: 23 words on source page
- Solution: 104 words on source page
- Rationale: 178 words on source page

## Source Navigation

- Previous source navigation: Tunnelling
- Next source navigation: Serial Positioning Effect


<!-- ===== ui-patterns/wiki/concepts/patterns/continuous-scrolling.md ===== -->

---
title: "Continuous Scrolling"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/ContinuousScrolling"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/ContinuousScrolling"
source_slug: "ContinuousScrolling"
track: "User Interface Design Patterns"
group: "Navigation"
subgroup: "Content"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 3
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Continuous Scrolling

> Catalog pointer for the UI Patterns source page: [Continuous Scrolling](https://ui-patterns.com/patterns/ContinuousScrolling).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Navigation
- Subgroup: Content
- Source breadcrumb: Design Patterns > Navigation > Content > Continuous Scrolling

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/ContinuousScrolling
- Page title: Continuous Scrolling design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 3
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 47 words on source page
- Example: 34 words on source page
- Usage: 33 words on source page
- Solution: 112 words on source page
- Rationale: 186 words on source page

## Source Navigation

- Previous source navigation: Blank Slate
- Next source navigation: Archive


<!-- ===== ui-patterns/wiki/concepts/patterns/copy-box.md ===== -->

---
title: "Copy Box"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/CopyBox"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/CopyBox"
source_slug: "CopyBox"
track: "User Interface Design Patterns"
group: "Dealing with data"
subgroup: "Formatting data"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 10
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Copy Box

> Catalog pointer for the UI Patterns source page: [Copy Box](https://ui-patterns.com/patterns/CopyBox).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Dealing with data
- Subgroup: Formatting data
- Source breadcrumb: Design Patterns > Dealing with data > Formatting data > Copy Box

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/CopyBox
- Page title: Copy Box design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 10
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 9 words on source page
- Example: 47 words on source page
- Usage: 46 words on source page
- Solution: 121 words on source page
- Rationale: 60 words on source page

## Source Navigation

- Previous source navigation: Table Filter
- Next source navigation: Coupon


<!-- ===== ui-patterns/wiki/concepts/patterns/coupon.md ===== -->

---
title: "Coupon"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Coupon"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Coupon"
source_slug: "Coupon"
track: "User Interface Design Patterns"
group: "Miscellaneous"
subgroup: "Shopping"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Types of coupon offers"
  - "Rationale"
example_count: 9
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Coupon

> Catalog pointer for the UI Patterns source page: [Coupon](https://ui-patterns.com/patterns/Coupon).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Miscellaneous
- Subgroup: Shopping
- Source breadcrumb: Design Patterns > Miscellaneous > Shopping > Coupon

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Coupon
- Page title: Coupon design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Types of coupon offers, Rationale
- Example screenshots detected at source: 9
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 11 words on source page
- Example: 114 words on source page
- Usage: 76 words on source page
- Solution: 197 words on source page
- Types of coupon offers: 129 words on source page
- Rationale: 140 words on source page

## Source Navigation

- Previous source navigation: Shopping Cart
- Next source navigation: Continuous Scrolling


<!-- ===== ui-patterns/wiki/concepts/patterns/curiosity.md ===== -->

---
title: "Curiosity"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/curiosity"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/curiosity"
source_slug: "curiosity"
track: "Persuasive Design Patterns"
group: "Cognition"
subgroup: "Other cognitive biases"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 2
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Curiosity

> Catalog pointer for the UI Patterns source page: [Curiosity](https://ui-patterns.com/patterns/curiosity).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Cognition
- Subgroup: Other cognitive biases
- Source breadcrumb: Design Patterns > Cognition > Other cognitive biases > Curiosity

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/curiosity
- Page title: Curiosity design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 2
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 12 words on source page
- Example: 31 words on source page
- Usage: 12 words on source page
- Solution: 93 words on source page
- Rationale: 176 words on source page

## Source Navigation

- Previous source navigation: Paywall
- Next source navigation: Auto-sharing


<!-- ===== ui-patterns/wiki/concepts/patterns/dashboard.md ===== -->

---
title: "Dashboard"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/dashboard"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/dashboard"
source_slug: "dashboard"
track: "User Interface Design Patterns"
group: "Dealing with data"
subgroup: "Formatting data"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Types of dashboards"
  - "Rationale"
example_count: 6
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Dashboard

> Catalog pointer for the UI Patterns source page: [Dashboard](https://ui-patterns.com/patterns/dashboard).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Dealing with data
- Subgroup: Formatting data
- Source breadcrumb: Design Patterns > Dealing with data > Formatting data > Dashboard

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/dashboard
- Page title: Dashboard design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Types of dashboards, Rationale
- Example screenshots detected at source: 6
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 12 words on source page
- Example: 46 words on source page
- Usage: 18 words on source page
- Solution: 223 words on source page
- Types of dashboards: 185 words on source page
- Rationale: 95 words on source page

## Source Navigation

- Previous source navigation: Paywall
- Next source navigation: Auto-sharing


<!-- ===== ui-patterns/wiki/concepts/patterns/decoy-effect.md ===== -->

---
title: "Decoy Effect"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/decoy-effect"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/decoy-effect"
source_slug: "decoy-effect"
track: "Persuasive Design Patterns"
group: "Cognition"
subgroup: "Loss Aversion"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
  - "Discussion"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Decoy Effect

> Catalog pointer for the UI Patterns source page: [Decoy Effect](https://ui-patterns.com/patterns/decoy-effect).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Cognition
- Subgroup: Loss Aversion
- Source breadcrumb: Design Patterns > Cognition > Loss Aversion > Decoy Effect

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/decoy-effect
- Page title: Decoy Effect design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale, Discussion
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 48 words on source page
- Usage: 38 words on source page
- Solution: 235 words on source page
- Rationale: 73 words on source page
- Discussion: 341 words on source page

## Source Navigation

- Previous source navigation: Present Bias


<!-- ===== ui-patterns/wiki/concepts/patterns/delay-discounting.md ===== -->

---
title: "Delay Discounting"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/delay-discounting"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/delay-discounting"
source_slug: "delay-discounting"
track: "Persuasive Design Patterns"
group: "Cognition"
subgroup: "Other cognitive biases"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Delay Discounting

> Catalog pointer for the UI Patterns source page: [Delay Discounting](https://ui-patterns.com/patterns/delay-discounting).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Cognition
- Subgroup: Other cognitive biases
- Source breadcrumb: Design Patterns > Cognition > Other cognitive biases > Delay Discounting

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/delay-discounting
- Page title: Delay Discounting design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 33 words on source page
- Usage: 21 words on source page
- Solution: 133 words on source page
- Rationale: 106 words on source page

## Source Navigation

- Previous source navigation: Fresh Start Effect
- Next source navigation: Inaction Inertia Effect


<!-- ===== ui-patterns/wiki/concepts/patterns/delighters.md ===== -->

---
title: "Delighters"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/delighters"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/delighters"
source_slug: "delighters"
track: "Persuasive Design Patterns"
group: "Game mechanics"
subgroup: "Gameplay rewards"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
  - "Discussion"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Delighters

> Catalog pointer for the UI Patterns source page: [Delighters](https://ui-patterns.com/patterns/delighters).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Game mechanics
- Subgroup: Gameplay rewards
- Source breadcrumb: Design Patterns > Game mechanics > Gameplay rewards > Delighters

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/delighters
- Page title: Delighters design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale, Discussion
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 28 words on source page
- Usage: 16 words on source page
- Solution: 123 words on source page
- Rationale: 55 words on source page
- Discussion: 251 words on source page

## Source Navigation

- Previous source navigation: Periodic Events
- Next source navigation: Flagging & Reporting


<!-- ===== ui-patterns/wiki/concepts/patterns/drag-and-drop.md ===== -->

---
title: "Drag and drop"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/drag-and-drop"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/drag-and-drop"
source_slug: "drag-and-drop"
track: "User Interface Design Patterns"
group: "Getting input"
subgroup: "Forms"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
  - "Discussion"
example_count: 1
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Drag and drop

> Catalog pointer for the UI Patterns source page: [Drag and drop](https://ui-patterns.com/patterns/drag-and-drop).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Getting input
- Subgroup: Forms
- Source breadcrumb: Design Patterns > Getting input > Forms > Drag and drop

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/drag-and-drop
- Page title: Drag and drop design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale, Discussion
- Example screenshots detected at source: 1
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 19 words on source page
- Example: 58 words on source page
- Usage: 47 words on source page
- Solution: 13 words on source page
- Rationale: 59 words on source page
- Discussion: 24 words on source page

## Source Navigation

- Previous source navigation: Playthrough
- Next source navigation: Cards


<!-- ===== ui-patterns/wiki/concepts/patterns/endowment-effect.md ===== -->

---
title: "Endowment Effect"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Endowment-effect"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Endowment-effect"
source_slug: "Endowment-effect"
track: "Persuasive Design Patterns"
group: "Cognition"
subgroup: "Loss Aversion"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
  - "Discussion"
example_count: 1
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Endowment Effect

> Catalog pointer for the UI Patterns source page: [Endowment Effect](https://ui-patterns.com/patterns/Endowment-effect).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Cognition
- Subgroup: Loss Aversion
- Source breadcrumb: Design Patterns > Cognition > Loss Aversion > Endowment Effect

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Endowment-effect
- Page title: Endowment Effect design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale, Discussion
- Example screenshots detected at source: 1
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 22 words on source page
- Example: 71 words on source page
- Usage: 27 words on source page
- Solution: 42 words on source page
- Rationale: 302 words on source page
- Discussion: 136 words on source page

## Source Navigation

- Previous source navigation: Storytelling
- Next source navigation: Peak-end rule


<!-- ===== ui-patterns/wiki/concepts/patterns/event-calendar.md ===== -->

---
title: "Event Calendar"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/EventCalendar"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/EventCalendar"
source_slug: "EventCalendar"
track: "User Interface Design Patterns"
group: "Navigation"
subgroup: "Content"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "The elements of an event list"
  - "Rationale"
  - "Discussion"
  - "Buckets of time"
  - "Common pitfalls of event calendar design"
  - "Thinking in outlook and the calendar box"
  - "Listing events without a start time"
  - "Missing other relevant data"
  - "Impossible to scan"
  - "Huge lists"
  - "No filtering options"
  - "Use the user’s abstractions – not your own"
example_count: 15
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Event Calendar

> Catalog pointer for the UI Patterns source page: [Event Calendar](https://ui-patterns.com/patterns/EventCalendar).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Navigation
- Subgroup: Content
- Source breadcrumb: Design Patterns > Navigation > Content > Event Calendar

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/EventCalendar
- Page title: Event Calendar design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, The elements of an event list, Rationale, Discussion, Buckets of time, Common pitfalls of event calendar design, Thinking in outlook and the calendar box, Listing events without a start time, Missing other relevant data, Impossible to scan, Huge lists, No filtering options, Use the user’s abstractions – not your own
- Example screenshots detected at source: 15
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 32 words on source page
- Example: 64 words on source page
- Usage: 45 words on source page
- Solution: 338 words on source page
- The elements of an event list: 93 words on source page
- Rationale: 23 words on source page
- Discussion: 892 words on source page
- Buckets of time: 138 words on source page
- Common pitfalls of event calendar design: 16 words on source page
- Thinking in outlook and the calendar box: 97 words on source page
- Listing events without a start time: 155 words on source page
- Missing other relevant data: 81 words on source page
- Impossible to scan: 144 words on source page
- Huge lists: 54 words on source page
- No filtering options: 61 words on source page
- Use the user’s abstractions – not your own: 94 words on source page

## Source Navigation

- Previous source navigation: Article List
- Next source navigation: Intentional Gaps


<!-- ===== ui-patterns/wiki/concepts/patterns/expandable-input.md ===== -->

---
title: "Expandable Input"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/expandable-input"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/expandable-input"
source_slug: "expandable-input"
track: "User Interface Design Patterns"
group: "Getting input"
subgroup: "Forms"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 1
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Expandable Input

> Catalog pointer for the UI Patterns source page: [Expandable Input](https://ui-patterns.com/patterns/expandable-input).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Getting input
- Subgroup: Forms
- Source breadcrumb: Design Patterns > Getting input > Forms > Expandable Input

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/expandable-input
- Page title: Expandable Input design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 1
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 20 words on source page
- Example: 68 words on source page
- Usage: 30 words on source page
- Solution: 56 words on source page
- Rationale: 40 words on source page

## Source Navigation

- Previous source navigation: Flagging & Reporting
- Next source navigation: Morphing Controls


<!-- ===== ui-patterns/wiki/concepts/patterns/fat-footer.md ===== -->

---
title: "Fat Footer"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/FatFooter"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/FatFooter"
source_slug: "FatFooter"
track: "User Interface Design Patterns"
group: "Navigation"
subgroup: "Jumping in hierarchy"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
  - "Discussion"
example_count: 13
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Fat Footer

> Catalog pointer for the UI Patterns source page: [Fat Footer](https://ui-patterns.com/patterns/FatFooter).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Navigation
- Subgroup: Jumping in hierarchy
- Source breadcrumb: Design Patterns > Navigation > Jumping in hierarchy > Fat Footer

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/FatFooter
- Page title: Fat Footer design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale, Discussion
- Example screenshots detected at source: 13
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 22 words on source page
- Example: 101 words on source page
- Usage: 78 words on source page
- Solution: 236 words on source page
- Rationale: 96 words on source page
- Discussion: 86 words on source page

## Source Navigation

- Previous source navigation: Home Link
- Next source navigation: Accordion Menu


<!-- ===== ui-patterns/wiki/concepts/patterns/favorites.md ===== -->

---
title: "Favorites"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/favorites"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/favorites"
source_slug: "favorites"
track: "User Interface Design Patterns"
group: "Navigation"
subgroup: "Content"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 3
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Favorites

> Catalog pointer for the UI Patterns source page: [Favorites](https://ui-patterns.com/patterns/favorites).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Navigation
- Subgroup: Content
- Source breadcrumb: Design Patterns > Navigation > Content > Favorites

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/favorites
- Page title: Favorites design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 3
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 10 words on source page
- Example: 39 words on source page
- Usage: 26 words on source page
- Solution: 171 words on source page
- Rationale: 50 words on source page

## Source Navigation

- Previous source navigation: Frequently Asked Questions (FAQ)
- Next source navigation: Pull to refresh


<!-- ===== ui-patterns/wiki/concepts/patterns/feedback-loops.md ===== -->

---
title: "Feedback Loops"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Feedback-loops"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Feedback-loops"
source_slug: "Feedback-loops"
track: "Persuasive Design Patterns"
group: "Feedback"
subgroup: "Timing"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
  - "Discussion"
  - "Positive feedback loops"
  - "Negative feedback loops"
  - "Things are connected"
  - "The four distinct stages of a feedback loop"
example_count: 1
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Feedback Loops

> Catalog pointer for the UI Patterns source page: [Feedback Loops](https://ui-patterns.com/patterns/Feedback-loops).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Feedback
- Subgroup: Timing
- Source breadcrumb: Design Patterns > Feedback > Timing > Feedback Loops

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Feedback-loops
- Page title: Feedback Loops design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale, Discussion, Positive feedback loops, Negative feedback loops, Things are connected, The four distinct stages of a feedback loop
- Example screenshots detected at source: 1
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 11 words on source page
- Example: 113 words on source page
- Usage: 15 words on source page
- Solution: 66 words on source page
- Rationale: 20 words on source page
- Discussion: 568 words on source page
- Positive feedback loops: 23 words on source page
- Negative feedback loops: 31 words on source page
- Things are connected: 85 words on source page
- The four distinct stages of a feedback loop: 229 words on source page

## Source Navigation

- Previous source navigation: Negativity bias
- Next source navigation: Reciprocation


<!-- ===== ui-patterns/wiki/concepts/patterns/fill-in-the-blanks.md ===== -->

---
title: "Fill in the Blanks"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/FillInTheBlanks"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/FillInTheBlanks"
source_slug: "FillInTheBlanks"
track: "User Interface Design Patterns"
group: "Getting input"
subgroup: "Forms"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 13
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Fill in the Blanks

> Catalog pointer for the UI Patterns source page: [Fill in the Blanks](https://ui-patterns.com/patterns/FillInTheBlanks).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Getting input
- Subgroup: Forms
- Source breadcrumb: Design Patterns > Getting input > Forms > Fill in the Blanks

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/FillInTheBlanks
- Page title: Fill in the Blanks design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 13
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 9 words on source page
- Example: 161 words on source page
- Usage: 160 words on source page
- Solution: 196 words on source page
- Rationale: 191 words on source page

## Source Navigation

- Previous source navigation: Structured Format
- Next source navigation: Input Prompt


<!-- ===== ui-patterns/wiki/concepts/patterns/fixed-rewards.md ===== -->

---
title: "Fixed rewards"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Fixed-rewards"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Fixed-rewards"
source_slug: "Fixed-rewards"
track: "Persuasive Design Patterns"
group: "Game mechanics"
subgroup: "Fundamentals of rewards"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Fixed rewards"
  - "The right reward at the right time and amount"
  - "Types of rewards"
  - "Rationale"
  - "Discussion"
  - "Positive and negative rewards (and punishments)"
  - "Primary and secondary rewards"
  - "Notes"
example_count: 5
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Fixed rewards

> Catalog pointer for the UI Patterns source page: [Fixed rewards](https://ui-patterns.com/patterns/Fixed-rewards).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Game mechanics
- Subgroup: Fundamentals of rewards
- Source breadcrumb: Design Patterns > Game mechanics > Fundamentals of rewards > Fixed rewards

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Fixed-rewards
- Page title: Fixed rewards design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Fixed rewards, The right reward at the right time and amount, Types of rewards, Rationale, Discussion, Positive and negative rewards (and punishments), Primary and secondary rewards, Notes
- Example screenshots detected at source: 5
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 10 words on source page
- Example: 86 words on source page
- Usage: 41 words on source page
- Solution: 393 words on source page
- Fixed rewards: 139 words on source page
- The right reward at the right time and amount: 190 words on source page
- Types of rewards: 31 words on source page
- Rationale: 13 words on source page
- Discussion: 210 words on source page
- Positive and negative rewards (and punishments): 69 words on source page
- Primary and secondary rewards: 44 words on source page
- Notes: 18 words on source page

## Source Navigation

- Previous source navigation: Event Calendar
- Next source navigation: Loss Aversion


<!-- ===== ui-patterns/wiki/concepts/patterns/flagging-and-reporting.md ===== -->

---
title: "Flagging & Reporting"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/flagging-and-reporting"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/flagging-and-reporting"
source_slug: "flagging-and-reporting"
track: "User Interface Design Patterns"
group: "Getting input"
subgroup: "Community driven"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 1
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Flagging & Reporting

> Catalog pointer for the UI Patterns source page: [Flagging & Reporting](https://ui-patterns.com/patterns/flagging-and-reporting).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Getting input
- Subgroup: Community driven
- Source breadcrumb: Design Patterns > Getting input > Community driven > Flagging & Reporting

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/flagging-and-reporting
- Page title: Flagging & Reporting design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 1
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 9 words on source page
- Example: 26 words on source page
- Usage: 25 words on source page
- Solution: 6 words on source page
- Rationale: 56 words on source page

## Source Navigation

- Previous source navigation: Delighters
- Next source navigation: Keyboard Shortcuts


<!-- ===== ui-patterns/wiki/concepts/patterns/follow.md ===== -->

---
title: "Follow"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/follow"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/follow"
source_slug: "follow"
track: "User Interface Design Patterns"
group: "Social"
subgroup: "Social interactions"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
  - "Discussion"
example_count: 1
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Follow

> Catalog pointer for the UI Patterns source page: [Follow](https://ui-patterns.com/patterns/follow).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Social
- Subgroup: Social interactions
- Source breadcrumb: Design Patterns > Social > Social interactions > Follow

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/follow
- Page title: Follow design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale, Discussion
- Example screenshots detected at source: 1
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 19 words on source page
- Example: 34 words on source page
- Usage: 19 words on source page
- Solution: 137 words on source page
- Rationale: 101 words on source page
- Discussion: 33 words on source page

## Source Navigation

- Previous source navigation: Testimonials
- Next source navigation: Invite friends


<!-- ===== ui-patterns/wiki/concepts/patterns/forgiving-format.md ===== -->

---
title: "Forgiving Format"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/ForgivingFormat"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/ForgivingFormat"
source_slug: "ForgivingFormat"
track: "User Interface Design Patterns"
group: "Getting input"
subgroup: "Forms"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 6
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Forgiving Format

> Catalog pointer for the UI Patterns source page: [Forgiving Format](https://ui-patterns.com/patterns/ForgivingFormat).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Getting input
- Subgroup: Forms
- Source breadcrumb: Design Patterns > Getting input > Forms > Forgiving Format

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/ForgivingFormat
- Page title: Forgiving Format design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 6
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 19 words on source page
- Example: 109 words on source page
- Usage: 108 words on source page
- Solution: 99 words on source page
- Rationale: 70 words on source page

## Source Navigation

- Previous source navigation: Accordion Menu
- Next source navigation: Structured Format


<!-- ===== ui-patterns/wiki/concepts/patterns/framing.md ===== -->

---
title: "Framing"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/framing"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/framing"
source_slug: "framing"
track: "Persuasive Design Patterns"
group: "Cognition"
subgroup: "Loss Aversion"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Framing

> Catalog pointer for the UI Patterns source page: [Framing](https://ui-patterns.com/patterns/framing).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Cognition
- Subgroup: Loss Aversion
- Source breadcrumb: Design Patterns > Cognition > Loss Aversion > Framing

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/framing
- Page title: Framing design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 20 words on source page
- Usage: 7 words on source page
- Solution: 119 words on source page
- Rationale: 188 words on source page

## Source Navigation

- Previous source navigation: Cards
- Next source navigation: Delighters


<!-- ===== ui-patterns/wiki/concepts/patterns/frequently-asked-questions-faq.md ===== -->

---
title: "Frequently Asked Questions (FAQ)"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/frequently-asked-questions-faq"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/frequently-asked-questions-faq"
source_slug: "frequently-asked-questions-faq"
track: "User Interface Design Patterns"
group: "Dealing with data"
subgroup: "Formatting data"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Focus on information"
  - "Designing longer FAQs"
  - "Card sorting"
  - "Let users ask new questions"
  - "Few people go to the FAQ front page directly"
example_count: 11
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Frequently Asked Questions (FAQ)

> Catalog pointer for the UI Patterns source page: [Frequently Asked Questions (FAQ)](https://ui-patterns.com/patterns/frequently-asked-questions-faq).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Dealing with data
- Subgroup: Formatting data
- Source breadcrumb: Design Patterns > Dealing with data > Formatting data > Frequently Asked Questions (FAQ)

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/frequently-asked-questions-faq
- Page title: Frequently Asked Questions (FAQ) design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Focus on information, Designing longer FAQs, Card sorting, Let users ask new questions, Few people go to the FAQ front page directly
- Example screenshots detected at source: 11
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 11 words on source page
- Example: 45 words on source page
- Usage: 30 words on source page
- Solution: 492 words on source page
- Focus on information: 53 words on source page
- Designing longer FAQs: 167 words on source page
- Card sorting: 43 words on source page
- Let users ask new questions: 46 words on source page
- Few people go to the FAQ front page directly: 78 words on source page

## Source Navigation

- Previous source navigation: Inline Hints
- Next source navigation: Categorization


<!-- ===== ui-patterns/wiki/concepts/patterns/fresh-start-effect.md ===== -->

---
title: "Fresh Start Effect"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/fresh-start-effect"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/fresh-start-effect"
source_slug: "fresh-start-effect"
track: "Persuasive Design Patterns"
group: "Feedback"
subgroup: "Timing"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Fresh Start Effect

> Catalog pointer for the UI Patterns source page: [Fresh Start Effect](https://ui-patterns.com/patterns/fresh-start-effect).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Feedback
- Subgroup: Timing
- Source breadcrumb: Design Patterns > Feedback > Timing > Fresh Start Effect

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/fresh-start-effect
- Page title: Fresh Start Effect design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 52 words on source page
- Usage: 35 words on source page
- Solution: 93 words on source page
- Rationale: 216 words on source page

## Source Navigation

- Previous source navigation: Priming Effect
- Next source navigation: Delay Discounting


<!-- ===== ui-patterns/wiki/concepts/patterns/friend-list.md ===== -->

---
title: "Friend list"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/friend-list"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/friend-list"
source_slug: "friend-list"
track: "User Interface Design Patterns"
group: "Social"
subgroup: "Social interactions"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 2
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Friend list

> Catalog pointer for the UI Patterns source page: [Friend list](https://ui-patterns.com/patterns/friend-list).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Social
- Subgroup: Social interactions
- Source breadcrumb: Design Patterns > Social > Social interactions > Friend list

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/friend-list
- Page title: Friend list design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 2
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 21 words on source page
- Example: 83 words on source page
- Usage: 77 words on source page
- Solution: 20 words on source page
- Rationale: 89 words on source page

## Source Navigation

- Previous source navigation: Testimonials
- Next source navigation: Invite friends


<!-- ===== ui-patterns/wiki/concepts/patterns/friend.md ===== -->

---
title: "Friend"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/friend"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/friend"
source_slug: "friend"
track: "User Interface Design Patterns"
group: "Social"
subgroup: "Social interactions"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
example_count: 1
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Friend

> Catalog pointer for the UI Patterns source page: [Friend](https://ui-patterns.com/patterns/friend).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Social
- Subgroup: Social interactions
- Source breadcrumb: Design Patterns > Social > Social interactions > Friend

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/friend
- Page title: Friend design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution
- Example screenshots detected at source: 1
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 12 words on source page
- Example: 33 words on source page
- Usage: 23 words on source page
- Solution: 57 words on source page

## Source Navigation

- Previous source navigation: Frequently Asked Questions (FAQ)
- Next source navigation: Pull to refresh


<!-- ===== ui-patterns/wiki/concepts/patterns/gallery.md ===== -->

---
title: "Gallery"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Gallery"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Gallery"
source_slug: "Gallery"
track: "User Interface Design Patterns"
group: "Dealing with data"
subgroup: "Images"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Navigation options often include"
  - "Tips for designing a gallery"
  - "Reload the entire page or change only the important parts"
  - "Rationale"
example_count: 13
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Gallery

> Catalog pointer for the UI Patterns source page: [Gallery](https://ui-patterns.com/patterns/Gallery).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Dealing with data
- Subgroup: Images
- Source breadcrumb: Design Patterns > Dealing with data > Images > Gallery

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Gallery
- Page title: Gallery design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Navigation options often include, Tips for designing a gallery, Reload the entire page or change only the important parts, Rationale
- Example screenshots detected at source: 13
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 11 words on source page
- Example: 111 words on source page
- Usage: 65 words on source page
- Solution: 465 words on source page
- Navigation options often include: 144 words on source page
- Tips for designing a gallery: 155 words on source page
- Reload the entire page or change only the important parts: 61 words on source page
- Rationale: 135 words on source page

## Source Navigation

- Previous source navigation: Walkthrough
- Next source navigation: Slideshow


<!-- ===== ui-patterns/wiki/concepts/patterns/goal-gradient-effect.md ===== -->

---
title: "Goal-Gradient Effect"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Completion"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Completion"
source_slug: "Completion"
track: "Persuasive Design Patterns"
group: "Game mechanics"
subgroup: "Gameplay rewards"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Set and communicate expectations and progress."
  - "Making the completion official"
  - "Provide artificial progress"
  - "Beware of the post-reward reset effect"
  - "Divide larger tasks into sub-tasks"
  - "Rationale"
example_count: 4
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Goal-Gradient Effect

> Catalog pointer for the UI Patterns source page: [Goal-Gradient Effect](https://ui-patterns.com/patterns/Completion).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Game mechanics
- Subgroup: Gameplay rewards
- Source breadcrumb: Design Patterns > Game mechanics > Gameplay rewards > Goal-Gradient Effect

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Completion
- Page title: Goal-Gradient Effect design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Set and communicate expectations and progress., Making the completion official, Provide artificial progress, Beware of the post-reward reset effect, Divide larger tasks into sub-tasks, Rationale
- Example screenshots detected at source: 4
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 10 words on source page
- Example: 72 words on source page
- Usage: 50 words on source page
- Solution: 362 words on source page
- Set and communicate expectations and progress.: 112 words on source page
- Making the completion official: 71 words on source page
- Provide artificial progress: 39 words on source page
- Beware of the post-reward reset effect: 32 words on source page
- Divide larger tasks into sub-tasks: 7 words on source page
- Rationale: 257 words on source page

## Source Navigation

- Previous source navigation: Value Attribution
- Next source navigation: Trigger


<!-- ===== ui-patterns/wiki/concepts/patterns/good-defaults.md ===== -->

---
title: "Good Defaults"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/GoodDefaults"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/GoodDefaults"
source_slug: "GoodDefaults"
track: "User Interface Design Patterns"
group: "Getting input"
subgroup: "Forms"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 8
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Good Defaults

> Catalog pointer for the UI Patterns source page: [Good Defaults](https://ui-patterns.com/patterns/GoodDefaults).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Getting input
- Subgroup: Forms
- Source breadcrumb: Design Patterns > Getting input > Forms > Good Defaults

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/GoodDefaults
- Page title: Good Defaults design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 8
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 20 words on source page
- Example: 153 words on source page
- Usage: 104 words on source page
- Solution: 108 words on source page
- Rationale: 92 words on source page

## Source Navigation

- Previous source navigation: Fill in the Blanks
- Next source navigation: Captcha


<!-- ===== ui-patterns/wiki/concepts/patterns/guided-tour.md ===== -->

---
title: "Guided Tour"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Guided-tour"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Guided-tour"
source_slug: "Guided-tour"
track: "User Interface Design Patterns"
group: "Onboarding"
subgroup: "Guidance"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Product-guided vs User-guided."
example_count: 13
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Guided Tour

> Catalog pointer for the UI Patterns source page: [Guided Tour](https://ui-patterns.com/patterns/Guided-tour).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Onboarding
- Subgroup: Guidance
- Source breadcrumb: Design Patterns > Onboarding > Guidance > Guided Tour

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Guided-tour
- Page title: Guided Tour design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Product-guided vs User-guided.
- Example screenshots detected at source: 13
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 11 words on source page
- Example: 58 words on source page
- Usage: 36 words on source page
- Solution: 184 words on source page
- Product-guided vs User-guided.: 57 words on source page

## Source Navigation

- Previous source navigation: Flagging & Reporting
- Next source navigation: Morphing Controls


<!-- ===== ui-patterns/wiki/concepts/patterns/halo-effect.md ===== -->

---
title: "Halo Effect"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/halo-effect"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/halo-effect"
source_slug: "halo-effect"
track: "Persuasive Design Patterns"
group: "Social"
subgroup: "Social biases"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
  - "Discussion"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Halo Effect

> Catalog pointer for the UI Patterns source page: [Halo Effect](https://ui-patterns.com/patterns/halo-effect).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Social
- Subgroup: Social biases
- Source breadcrumb: Design Patterns > Social > Social biases > Halo Effect

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/halo-effect
- Page title: Halo Effect design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale, Discussion
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 33 words on source page
- Usage: 20 words on source page
- Solution: 74 words on source page
- Rationale: 96 words on source page
- Discussion: 150 words on source page

## Source Navigation

- Previous source navigation: Rule Builder
- Next source navigation: Sunk Cost Effect


<!-- ===== ui-patterns/wiki/concepts/patterns/hedonic-adaptation.md ===== -->

---
title: "Hedonic Adaptation"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/hedonic-adaptation"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/hedonic-adaptation"
source_slug: "hedonic-adaptation"
track: "Persuasive Design Patterns"
group: "Game mechanics"
subgroup: "Gameplay design"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Hedonic Adaptation

> Catalog pointer for the UI Patterns source page: [Hedonic Adaptation](https://ui-patterns.com/patterns/hedonic-adaptation).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Game mechanics
- Subgroup: Gameplay design
- Source breadcrumb: Design Patterns > Game mechanics > Gameplay design > Hedonic Adaptation

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/hedonic-adaptation
- Page title: Hedonic Adaptation design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 40 words on source page
- Usage: 25 words on source page
- Solution: 153 words on source page
- Rationale: 185 words on source page

## Source Navigation

- Previous source navigation: Present Bias


<!-- ===== ui-patterns/wiki/concepts/patterns/home-link.md ===== -->

---
title: "Home Link"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/HomeLink"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/HomeLink"
source_slug: "HomeLink"
track: "User Interface Design Patterns"
group: "Navigation"
subgroup: "Jumping in hierarchy"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 1
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Home Link

> Catalog pointer for the UI Patterns source page: [Home Link](https://ui-patterns.com/patterns/HomeLink).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Navigation
- Subgroup: Jumping in hierarchy
- Source breadcrumb: Design Patterns > Navigation > Jumping in hierarchy > Home Link

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/HomeLink
- Page title: Home Link design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 1
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 14 words on source page
- Example: 35 words on source page
- Usage: 34 words on source page
- Solution: 89 words on source page
- Rationale: 65 words on source page

## Source Navigation

- Previous source navigation: Shortcut Dropdown
- Next source navigation: Fat Footer


<!-- ===== ui-patterns/wiki/concepts/patterns/horizontal-dropdown-menu.md ===== -->

---
title: "Horizontal Dropdown Menu"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/HorizontalDropdownMenu"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/HorizontalDropdownMenu"
source_slug: "HorizontalDropdownMenu"
track: "User Interface Design Patterns"
group: "Navigation"
subgroup: "Menus"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Other issues you want to take notice of"
  - "Rationale"
example_count: 3
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Horizontal Dropdown Menu

> Catalog pointer for the UI Patterns source page: [Horizontal Dropdown Menu](https://ui-patterns.com/patterns/HorizontalDropdownMenu).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Navigation
- Subgroup: Menus
- Source breadcrumb: Design Patterns > Navigation > Menus > Horizontal Dropdown Menu

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/HorizontalDropdownMenu
- Page title: Horizontal Dropdown Menu design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Other issues you want to take notice of, Rationale
- Example screenshots detected at source: 3
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 18 words on source page
- Example: 55 words on source page
- Usage: 54 words on source page
- Solution: 264 words on source page
- Other issues you want to take notice of: 66 words on source page
- Rationale: 66 words on source page

## Source Navigation

- Previous source navigation: Home Link
- Next source navigation: Accordion Menu


<!-- ===== ui-patterns/wiki/concepts/patterns/ikea-effect.md ===== -->

---
title: "IKEA effect"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/ikea-effect"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/ikea-effect"
source_slug: "ikea-effect"
track: "Persuasive Design Patterns"
group: "Cognition"
subgroup: "Loss Aversion"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# IKEA effect

> Catalog pointer for the UI Patterns source page: [IKEA effect](https://ui-patterns.com/patterns/ikea-effect).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Cognition
- Subgroup: Loss Aversion
- Source breadcrumb: Design Patterns > Cognition > Loss Aversion > IKEA effect

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/ikea-effect
- Page title: IKEA effect design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 57 words on source page
- Usage: 45 words on source page
- Solution: 156 words on source page
- Rationale: 252 words on source page

## Source Navigation

- Previous source navigation: Present Bias


<!-- ===== ui-patterns/wiki/concepts/patterns/illusion-of-control.md ===== -->

---
title: "Illusion of control"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Illusion-of-control"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Illusion-of-control"
source_slug: "Illusion-of-control"
track: "Persuasive Design Patterns"
group: "Cognition"
subgroup: "Other cognitive biases"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Illusion of control

> Catalog pointer for the UI Patterns source page: [Illusion of control](https://ui-patterns.com/patterns/Illusion-of-control).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Cognition
- Subgroup: Other cognitive biases
- Source breadcrumb: Design Patterns > Cognition > Other cognitive biases > Illusion of control

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Illusion-of-control
- Page title: Illusion of control design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 33 words on source page
- Usage: 13 words on source page
- Solution: 28 words on source page
- Rationale: 361 words on source page

## Source Navigation

- Previous source navigation: Peak-end rule
- Next source navigation: Kairos


<!-- ===== ui-patterns/wiki/concepts/patterns/image-zoom.md ===== -->

---
title: "Image Zoom"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/ImageZoom"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/ImageZoom"
source_slug: "ImageZoom"
track: "User Interface Design Patterns"
group: "Dealing with data"
subgroup: "Images"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 13
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Image Zoom

> Catalog pointer for the UI Patterns source page: [Image Zoom](https://ui-patterns.com/patterns/ImageZoom).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Dealing with data
- Subgroup: Images
- Source breadcrumb: Design Patterns > Dealing with data > Images > Image Zoom

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/ImageZoom
- Page title: Image Zoom design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 13
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 18 words on source page
- Example: 171 words on source page
- Usage: 139 words on source page
- Solution: 98 words on source page
- Rationale: 95 words on source page

## Source Navigation

- Previous source navigation: Rate Content
- Next source navigation: Adaptable View


<!-- ===== ui-patterns/wiki/concepts/patterns/inaction-inertia-effect.md ===== -->

---
title: "Inaction Inertia Effect"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/inaction-inertia-effect"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/inaction-inertia-effect"
source_slug: "inaction-inertia-effect"
track: "Persuasive Design Patterns"
group: "Cognition"
subgroup: "Other cognitive biases"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Inaction Inertia Effect

> Catalog pointer for the UI Patterns source page: [Inaction Inertia Effect](https://ui-patterns.com/patterns/inaction-inertia-effect).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Cognition
- Subgroup: Other cognitive biases
- Source breadcrumb: Design Patterns > Cognition > Other cognitive biases > Inaction Inertia Effect

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/inaction-inertia-effect
- Page title: Inaction Inertia Effect design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 54 words on source page
- Usage: 40 words on source page
- Solution: 160 words on source page
- Rationale: 173 words on source page

## Source Navigation

- Previous source navigation: Zeigarnik Effect
- Next source navigation: Picture Superiority Effect


<!-- ===== ui-patterns/wiki/concepts/patterns/inline-help-box.md ===== -->

---
title: "Inline Help Box"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/InlineHelpBox"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/InlineHelpBox"
source_slug: "InlineHelpBox"
track: "User Interface Design Patterns"
group: "Getting input"
subgroup: "Explaining the process"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 13
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Inline Help Box

> Catalog pointer for the UI Patterns source page: [Inline Help Box](https://ui-patterns.com/patterns/InlineHelpBox).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Getting input
- Subgroup: Explaining the process
- Source breadcrumb: Design Patterns > Getting input > Explaining the process > Inline Help Box

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/InlineHelpBox
- Page title: Inline Help Box design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 13
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 15 words on source page
- Example: 93 words on source page
- Usage: 92 words on source page
- Solution: 180 words on source page
- Rationale: 70 words on source page

## Source Navigation

- Previous source navigation: Tag Cloud
- Next source navigation: Password Strength Meter


<!-- ===== ui-patterns/wiki/concepts/patterns/inline-hints.md ===== -->

---
title: "Inline Hints"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/inline-hints"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/inline-hints"
source_slug: "inline-hints"
track: "User Interface Design Patterns"
group: "Onboarding"
subgroup: "Guidance"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 4
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Inline Hints

> Catalog pointer for the UI Patterns source page: [Inline Hints](https://ui-patterns.com/patterns/inline-hints).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Onboarding
- Subgroup: Guidance
- Source breadcrumb: Design Patterns > Onboarding > Guidance > Inline Hints

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/inline-hints
- Page title: Inline Hints design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 4
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 15 words on source page
- Example: 99 words on source page
- Usage: 83 words on source page
- Solution: 202 words on source page
- Rationale: 39 words on source page

## Source Navigation

- Previous source navigation: Flagging & Reporting
- Next source navigation: Morphing Controls


<!-- ===== ui-patterns/wiki/concepts/patterns/inplace-editor.md ===== -->

---
title: "Inplace Editor"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/InplaceEditor"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/InplaceEditor"
source_slug: "InplaceEditor"
track: "User Interface Design Patterns"
group: "Getting input"
subgroup: "Forms"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 2
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Inplace Editor

> Catalog pointer for the UI Patterns source page: [Inplace Editor](https://ui-patterns.com/patterns/InplaceEditor).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Getting input
- Subgroup: Forms
- Source breadcrumb: Design Patterns > Getting input > Forms > Inplace Editor

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/InplaceEditor
- Page title: Inplace Editor design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 2
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 13 words on source page
- Example: 67 words on source page
- Usage: 66 words on source page
- Solution: 309 words on source page
- Rationale: 60 words on source page

## Source Navigation

- Previous source navigation: Good Defaults
- Next source navigation: Sort By Column


<!-- ===== ui-patterns/wiki/concepts/patterns/input-feedback.md ===== -->

---
title: "Input Feedback"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/InputFeedback"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/InputFeedback"
source_slug: "InputFeedback"
track: "User Interface Design Patterns"
group: "Getting input"
subgroup: "Forms"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
  - "Discussion"
  - "Provide clear feedback after every action"
example_count: 13
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Input Feedback

> Catalog pointer for the UI Patterns source page: [Input Feedback](https://ui-patterns.com/patterns/InputFeedback).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Getting input
- Subgroup: Forms
- Source breadcrumb: Design Patterns > Getting input > Forms > Input Feedback

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/InputFeedback
- Page title: Input Feedback design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale, Discussion, Provide clear feedback after every action
- Example screenshots detected at source: 13
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 19 words on source page
- Example: 66 words on source page
- Usage: 48 words on source page
- Solution: 459 words on source page
- Rationale: 128 words on source page
- Discussion: 130 words on source page
- Provide clear feedback after every action: 50 words on source page

## Source Navigation

- Previous source navigation: Account Registration
- Next source navigation: Rate Content


<!-- ===== ui-patterns/wiki/concepts/patterns/input-prompt.md ===== -->

---
title: "Input Prompt"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/InputPrompt"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/InputPrompt"
source_slug: "InputPrompt"
track: "User Interface Design Patterns"
group: "Getting input"
subgroup: "Forms"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 3
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Input Prompt

> Catalog pointer for the UI Patterns source page: [Input Prompt](https://ui-patterns.com/patterns/InputPrompt).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Getting input
- Subgroup: Forms
- Source breadcrumb: Design Patterns > Getting input > Forms > Input Prompt

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/InputPrompt
- Page title: Input Prompt design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 3
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 9 words on source page
- Example: 82 words on source page
- Usage: 81 words on source page
- Solution: 146 words on source page
- Rationale: 152 words on source page

## Source Navigation

- Previous source navigation: Fill in the Blanks
- Next source navigation: Captcha


<!-- ===== ui-patterns/wiki/concepts/patterns/intentional-gaps.md ===== -->

---
title: "Intentional Gaps"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Intentional-gaps"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Intentional-gaps"
source_slug: "Intentional-gaps"
track: "Persuasive Design Patterns"
group: "Game mechanics"
subgroup: "Gameplay design"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 3
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Intentional Gaps

> Catalog pointer for the UI Patterns source page: [Intentional Gaps](https://ui-patterns.com/patterns/Intentional-gaps).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Game mechanics
- Subgroup: Gameplay design
- Source breadcrumb: Design Patterns > Game mechanics > Gameplay design > Intentional Gaps

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Intentional-gaps
- Page title: Intentional Gaps design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 3
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 12 words on source page
- Example: 58 words on source page
- Usage: 40 words on source page
- Solution: 152 words on source page
- Rationale: 149 words on source page

## Source Navigation

- Previous source navigation: Event Calendar
- Next source navigation: Loss Aversion


<!-- ===== ui-patterns/wiki/concepts/patterns/investment-loops.md ===== -->

---
title: "Investment Loops"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/investment-loops"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/investment-loops"
source_slug: "investment-loops"
track: "Persuasive Design Patterns"
group: "Game mechanics"
subgroup: "Gameplay design"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 1
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Investment Loops

> Catalog pointer for the UI Patterns source page: [Investment Loops](https://ui-patterns.com/patterns/investment-loops).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Game mechanics
- Subgroup: Gameplay design
- Source breadcrumb: Design Patterns > Game mechanics > Gameplay design > Investment Loops

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/investment-loops
- Page title: Investment Loops design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 1
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 13 words on source page
- Example: 24 words on source page
- Usage: 23 words on source page
- Solution: 209 words on source page
- Rationale: 125 words on source page

## Source Navigation

- Previous source navigation: Temptation Bundling
- Next source navigation: Hedonic Adaptation


<!-- ===== ui-patterns/wiki/concepts/patterns/invite-friends.md ===== -->

---
title: "Invite friends"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/invite-friends"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/invite-friends"
source_slug: "invite-friends"
track: "User Interface Design Patterns"
group: "Social"
subgroup: "Social interactions"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 10
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Invite friends

> Catalog pointer for the UI Patterns source page: [Invite friends](https://ui-patterns.com/patterns/invite-friends).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Social
- Subgroup: Social interactions
- Source breadcrumb: Design Patterns > Social > Social interactions > Invite friends

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/invite-friends
- Page title: Invite friends design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 10
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 10 words on source page
- Example: 63 words on source page
- Usage: 33 words on source page
- Solution: 99 words on source page
- Rationale: 39 words on source page

## Source Navigation

- Previous source navigation: Chat
- Next source navigation: Modal


<!-- ===== ui-patterns/wiki/concepts/patterns/isolation-effect.md ===== -->

---
title: "Isolation Effect"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/isolation-effect"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/isolation-effect"
source_slug: "isolation-effect"
track: "Persuasive Design Patterns"
group: "Perception and memory"
subgroup: "Attention"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
  - "Discussion"
example_count: 1
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Isolation Effect

> Catalog pointer for the UI Patterns source page: [Isolation Effect](https://ui-patterns.com/patterns/isolation-effect).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Perception and memory
- Subgroup: Attention
- Source breadcrumb: Design Patterns > Perception and memory > Attention > Isolation Effect

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/isolation-effect
- Page title: Isolation Effect design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale, Discussion
- Example screenshots detected at source: 1
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 10 words on source page
- Example: 28 words on source page
- Usage: 14 words on source page
- Solution: 191 words on source page
- Rationale: 76 words on source page
- Discussion: 215 words on source page

## Source Navigation

- Previous source navigation: Cards
- Next source navigation: Delighters


<!-- ===== ui-patterns/wiki/concepts/patterns/kairos.md ===== -->

---
title: "Kairos"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Kairos"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Kairos"
source_slug: "Kairos"
track: "Persuasive Design Patterns"
group: "Feedback"
subgroup: "Timing"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Kairos comes in patterns"
  - "Map it out"
  - "Rationale"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Kairos

> Catalog pointer for the UI Patterns source page: [Kairos](https://ui-patterns.com/patterns/Kairos).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Feedback
- Subgroup: Timing
- Source breadcrumb: Design Patterns > Feedback > Timing > Kairos

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Kairos
- Page title: Kairos design pattern
- Section headings available at source: Problem summary, Usage, Solution, Kairos comes in patterns, Map it out, Rationale
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 59 words on source page
- Usage: 46 words on source page
- Solution: 441 words on source page
- Kairos comes in patterns: 166 words on source page
- Map it out: 142 words on source page
- Rationale: 243 words on source page

## Source Navigation

- Previous source navigation: Negativity bias
- Next source navigation: Reciprocation


<!-- ===== ui-patterns/wiki/concepts/patterns/keyboard-shortcuts.md ===== -->

---
title: "Keyboard Shortcuts"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/keyboard-shortcuts"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/keyboard-shortcuts"
source_slug: "keyboard-shortcuts"
track: "User Interface Design Patterns"
group: "Getting input"
subgroup: "Forms"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
  - "Discussion"
  - "Keyboard shortcut strategies"
example_count: 4
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Keyboard Shortcuts

> Catalog pointer for the UI Patterns source page: [Keyboard Shortcuts](https://ui-patterns.com/patterns/keyboard-shortcuts).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Getting input
- Subgroup: Forms
- Source breadcrumb: Design Patterns > Getting input > Forms > Keyboard Shortcuts

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/keyboard-shortcuts
- Page title: Keyboard Shortcuts design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale, Discussion, Keyboard shortcut strategies
- Example screenshots detected at source: 4
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 8 words on source page
- Example: 32 words on source page
- Usage: 15 words on source page
- Solution: 82 words on source page
- Rationale: 86 words on source page
- Discussion: 110 words on source page
- Keyboard shortcut strategies: 96 words on source page

## Source Navigation

- Previous source navigation: Flagging & Reporting
- Next source navigation: Morphing Controls


<!-- ===== ui-patterns/wiki/concepts/patterns/lazy-registration.md ===== -->

---
title: "Lazy Registration"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/LazyRegistration"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/LazyRegistration"
source_slug: "LazyRegistration"
track: "User Interface Design Patterns"
group: "Onboarding"
subgroup: "Registration"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
  - "Discussion"
example_count: 13
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Lazy Registration

> Catalog pointer for the UI Patterns source page: [Lazy Registration](https://ui-patterns.com/patterns/LazyRegistration).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Onboarding
- Subgroup: Registration
- Source breadcrumb: Design Patterns > Onboarding > Registration > Lazy Registration

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/LazyRegistration
- Page title: Lazy Registration design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale, Discussion
- Example screenshots detected at source: 13
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 17 words on source page
- Example: 195 words on source page
- Usage: 166 words on source page
- Solution: 260 words on source page
- Rationale: 206 words on source page
- Discussion: 129 words on source page

## Source Navigation

- Previous source navigation: Password Strength Meter
- Next source navigation: Vote To Promote


<!-- ===== ui-patterns/wiki/concepts/patterns/leaderboard.md ===== -->

---
title: "Leaderboard"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/leaderboard"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/leaderboard"
source_slug: "leaderboard"
track: "User Interface Design Patterns"
group: "Social"
subgroup: "Reputation"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Multiple views"
  - "More design tips"
example_count: 13
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Leaderboard

> Catalog pointer for the UI Patterns source page: [Leaderboard](https://ui-patterns.com/patterns/leaderboard).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Social
- Subgroup: Reputation
- Source breadcrumb: Design Patterns > Social > Reputation > Leaderboard

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/leaderboard
- Page title: Leaderboard design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Multiple views, More design tips
- Example screenshots detected at source: 13
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 15 words on source page
- Example: 73 words on source page
- Usage: 64 words on source page
- Solution: 256 words on source page
- Multiple views: 47 words on source page
- More design tips: 118 words on source page

## Source Navigation

- Previous source navigation: Paywall
- Next source navigation: Auto-sharing


<!-- ===== ui-patterns/wiki/concepts/patterns/levels.md ===== -->

---
title: "Levels"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Levels"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Levels"
source_slug: "Levels"
track: "Persuasive Design Patterns"
group: "Game mechanics"
subgroup: "Gameplay design"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Levels

> Catalog pointer for the UI Patterns source page: [Levels](https://ui-patterns.com/patterns/Levels).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Game mechanics
- Subgroup: Gameplay design
- Source breadcrumb: Design Patterns > Game mechanics > Gameplay design > Levels

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Levels
- Page title: Levels design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 33 words on source page
- Usage: 22 words on source page
- Solution: 147 words on source page
- Rationale: 123 words on source page

## Source Navigation

- Previous source navigation: Event Calendar
- Next source navigation: Loss Aversion


<!-- ===== ui-patterns/wiki/concepts/patterns/liking.md ===== -->

---
title: "Liking"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Liking"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Liking"
source_slug: "Liking"
track: "Persuasive Design Patterns"
group: "Social"
subgroup: "Social biases"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Physical attractiveness"
  - "Similarity"
  - "Compliments"
  - "Contact"
  - "Cooperation rather than competition"
  - "Conditioning & association"
  - "Rationale"
  - "Discussion"
  - "Powerful Pairings"
  - "Ethical Recommendations"
example_count: 4
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Liking

> Catalog pointer for the UI Patterns source page: [Liking](https://ui-patterns.com/patterns/Liking).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Social
- Subgroup: Social biases
- Source breadcrumb: Design Patterns > Social > Social biases > Liking

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Liking
- Page title: Liking design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Physical attractiveness, Similarity, Compliments, Contact, Cooperation rather than competition, Conditioning & association, Rationale, Discussion, Powerful Pairings, Ethical Recommendations
- Example screenshots detected at source: 4
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 14 words on source page
- Example: 89 words on source page
- Usage: 42 words on source page
- Solution: 759 words on source page
- Physical attractiveness: 120 words on source page
- Similarity: 75 words on source page
- Compliments: 91 words on source page
- Contact: 90 words on source page
- Cooperation rather than competition: 235 words on source page
- Conditioning & association: 102 words on source page
- Rationale: 235 words on source page
- Discussion: 1234 words on source page
- Powerful Pairings: 335 words on source page
- Ethical Recommendations: 282 words on source page

## Source Navigation

- Previous source navigation: Product page
- Next source navigation: Walkthrough


<!-- ===== ui-patterns/wiki/concepts/patterns/limited-choice.md ===== -->

---
title: "Limited Choice"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Limited-choice"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Limited-choice"
source_slug: "Limited-choice"
track: "Persuasive Design Patterns"
group: "Cognition"
subgroup: "Scarcity"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Limited Choice

> Catalog pointer for the UI Patterns source page: [Limited Choice](https://ui-patterns.com/patterns/Limited-choice).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Cognition
- Subgroup: Scarcity
- Source breadcrumb: Design Patterns > Cognition > Scarcity > Limited Choice

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Limited-choice
- Page title: Limited Choice design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 49 words on source page
- Usage: 32 words on source page
- Solution: 138 words on source page
- Rationale: 190 words on source page

## Source Navigation

- Previous source navigation: Goal-Gradient Effect
- Next source navigation: Tailoring


<!-- ===== ui-patterns/wiki/concepts/patterns/limited-duration.md ===== -->

---
title: "Limited duration"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Limited-duration"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Limited-duration"
source_slug: "Limited-duration"
track: "Persuasive Design Patterns"
group: "Cognition"
subgroup: "Scarcity"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 4
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Limited duration

> Catalog pointer for the UI Patterns source page: [Limited duration](https://ui-patterns.com/patterns/Limited-duration).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Cognition
- Subgroup: Scarcity
- Source breadcrumb: Design Patterns > Cognition > Scarcity > Limited duration

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Limited-duration
- Page title: Limited duration design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 4
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 9 words on source page
- Example: 80 words on source page
- Usage: 45 words on source page
- Solution: 115 words on source page
- Rationale: 80 words on source page

## Source Navigation

- Previous source navigation: Variable Rewards
- Next source navigation: Self-Expression


<!-- ===== ui-patterns/wiki/concepts/patterns/loss-aversion.md ===== -->

---
title: "Loss Aversion"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Loss-aversion"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Loss-aversion"
source_slug: "Loss-aversion"
track: "Persuasive Design Patterns"
group: "Cognition"
subgroup: "Loss Aversion"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Thaler’s 4 principles"
  - "How to apply loss aversion to your product"
  - "Rationale"
  - "Example: Discounts and trial periods"
  - "Discussion"
  - "Example: Lazy registration"
  - "Background"
example_count: 2
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Loss Aversion

> Catalog pointer for the UI Patterns source page: [Loss Aversion](https://ui-patterns.com/patterns/Loss-aversion).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Cognition
- Subgroup: Loss Aversion
- Source breadcrumb: Design Patterns > Cognition > Loss Aversion > Loss Aversion

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Loss-aversion
- Page title: Loss Aversion design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Thaler’s 4 principles, How to apply loss aversion to your product, Rationale, Example: Discounts and trial periods, Discussion, Example: Lazy registration, Background
- Example screenshots detected at source: 2
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 16 words on source page
- Example: 72 words on source page
- Usage: 33 words on source page
- Solution: 586 words on source page
- Thaler’s 4 principles: 282 words on source page
- How to apply loss aversion to your product: 177 words on source page
- Rationale: 360 words on source page
- Example: Discounts and trial periods: 122 words on source page
- Discussion: 347 words on source page
- Example: Lazy registration: 117 words on source page
- Background: 68 words on source page

## Source Navigation

- Previous source navigation: Storytelling
- Next source navigation: Peak-end rule


<!-- ===== ui-patterns/wiki/concepts/patterns/modal.md ===== -->

---
title: "Modal"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/modal-windows"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/modal-windows"
source_slug: "modal-windows"
track: "User Interface Design Patterns"
group: "Navigation"
subgroup: "Jumping in hierarchy"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Matching titles"
  - "Allow escape"
  - "Rationale"
  - "Discussion"
example_count: 13
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Modal

> Catalog pointer for the UI Patterns source page: [Modal](https://ui-patterns.com/patterns/modal-windows).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Navigation
- Subgroup: Jumping in hierarchy
- Source breadcrumb: Design Patterns > Navigation > Jumping in hierarchy > Modal

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/modal-windows
- Page title: Modal design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Matching titles, Allow escape, Rationale, Discussion
- Example screenshots detected at source: 13
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 20 words on source page
- Example: 46 words on source page
- Usage: 32 words on source page
- Solution: 151 words on source page
- Matching titles: 48 words on source page
- Allow escape: 65 words on source page
- Rationale: 35 words on source page
- Discussion: 142 words on source page

## Source Navigation

- Previous source navigation: Undo
- Next source navigation: Cognitive Dissonance


<!-- ===== ui-patterns/wiki/concepts/patterns/module-tabs.md ===== -->

---
title: "Module Tabs"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/ModuleTabs"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/ModuleTabs"
source_slug: "ModuleTabs"
track: "User Interface Design Patterns"
group: "Navigation"
subgroup: "Tabs"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 9
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Module Tabs

> Catalog pointer for the UI Patterns source page: [Module Tabs](https://ui-patterns.com/patterns/ModuleTabs).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Navigation
- Subgroup: Tabs
- Source breadcrumb: Design Patterns > Navigation > Tabs > Module Tabs

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/ModuleTabs
- Page title: Module Tabs design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 9
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 27 words on source page
- Example: 113 words on source page
- Usage: 112 words on source page
- Solution: 138 words on source page
- Rationale: 88 words on source page

## Source Navigation

- Next source navigation: Navigation Tabs


<!-- ===== ui-patterns/wiki/concepts/patterns/morphing-controls.md ===== -->

---
title: "Morphing Controls"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/morphing-controls"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/morphing-controls"
source_slug: "morphing-controls"
track: "User Interface Design Patterns"
group: "Getting input"
subgroup: "Forms"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
example_count: 1
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Morphing Controls

> Catalog pointer for the UI Patterns source page: [Morphing Controls](https://ui-patterns.com/patterns/morphing-controls).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Getting input
- Subgroup: Forms
- Source breadcrumb: Design Patterns > Getting input > Forms > Morphing Controls

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/morphing-controls
- Page title: Morphing Controls design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution
- Example screenshots detected at source: 1
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 14 words on source page
- Example: 69 words on source page
- Usage: 39 words on source page
- Solution: 98 words on source page

## Source Navigation

- Previous source navigation: Inline Hints
- Next source navigation: Categorization


<!-- ===== ui-patterns/wiki/concepts/patterns/navigation-tabs.md ===== -->

---
title: "Navigation Tabs"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/NavigationTabs"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/NavigationTabs"
source_slug: "NavigationTabs"
track: "User Interface Design Patterns"
group: "Navigation"
subgroup: "Tabs"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 13
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Navigation Tabs

> Catalog pointer for the UI Patterns source page: [Navigation Tabs](https://ui-patterns.com/patterns/NavigationTabs).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Navigation
- Subgroup: Tabs
- Source breadcrumb: Design Patterns > Navigation > Tabs > Navigation Tabs

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/NavigationTabs
- Page title: Navigation Tabs design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 13
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 22 words on source page
- Example: 106 words on source page
- Usage: 105 words on source page
- Solution: 148 words on source page
- Rationale: 77 words on source page

## Source Navigation

- Previous source navigation: Module Tabs
- Next source navigation: Breadcrumbs


<!-- ===== ui-patterns/wiki/concepts/patterns/need-for-closure.md ===== -->

---
title: "Need for Closure"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Need-for-closure"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Need-for-closure"
source_slug: "Need-for-closure"
track: "Persuasive Design Patterns"
group: "Cognition"
subgroup: "Other cognitive biases"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
  - "Discussion"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Need for Closure

> Catalog pointer for the UI Patterns source page: [Need for Closure](https://ui-patterns.com/patterns/Need-for-closure).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Cognition
- Subgroup: Other cognitive biases
- Source breadcrumb: Design Patterns > Cognition > Other cognitive biases > Need for Closure

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Need-for-closure
- Page title: Need for Closure design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale, Discussion
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 57 words on source page
- Usage: 43 words on source page
- Solution: 137 words on source page
- Rationale: 142 words on source page
- Discussion: 258 words on source page

## Source Navigation

- Previous source navigation: Peak-end rule
- Next source navigation: Kairos


<!-- ===== ui-patterns/wiki/concepts/patterns/negativity-bias.md ===== -->

---
title: "Negativity bias"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Negativity-bias"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Negativity-bias"
source_slug: "Negativity-bias"
track: "Persuasive Design Patterns"
group: "Cognition"
subgroup: "Loss Aversion"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
  - "Discussion"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Negativity bias

> Catalog pointer for the UI Patterns source page: [Negativity bias](https://ui-patterns.com/patterns/Negativity-bias).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Cognition
- Subgroup: Loss Aversion
- Source breadcrumb: Design Patterns > Cognition > Loss Aversion > Negativity bias

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Negativity-bias
- Page title: Negativity bias design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale, Discussion
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 46 words on source page
- Usage: 23 words on source page
- Solution: 233 words on source page
- Rationale: 132 words on source page
- Discussion: 169 words on source page

## Source Navigation

- Previous source navigation: Peak-end rule
- Next source navigation: Kairos


<!-- ===== ui-patterns/wiki/concepts/patterns/noble-edge-effect.md ===== -->

---
title: "Noble Edge Effect"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/noble-edge-effect"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/noble-edge-effect"
source_slug: "noble-edge-effect"
track: "Persuasive Design Patterns"
group: "Social"
subgroup: "Social biases"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Noble Edge Effect

> Catalog pointer for the UI Patterns source page: [Noble Edge Effect](https://ui-patterns.com/patterns/noble-edge-effect).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Social
- Subgroup: Social biases
- Source breadcrumb: Design Patterns > Social > Social biases > Noble Edge Effect

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/noble-edge-effect
- Page title: Noble Edge Effect design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 39 words on source page
- Usage: 29 words on source page
- Solution: 110 words on source page
- Rationale: 172 words on source page

## Source Navigation

- Previous source navigation: Temptation Bundling
- Next source navigation: Hedonic Adaptation


<!-- ===== ui-patterns/wiki/concepts/patterns/nostalgia-effect.md ===== -->

---
title: "Nostalgia Effect"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/nostalgia-effect"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/nostalgia-effect"
source_slug: "nostalgia-effect"
track: "Persuasive Design Patterns"
group: "Social"
subgroup: "Social biases"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
  - "Discussion"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Nostalgia Effect

> Catalog pointer for the UI Patterns source page: [Nostalgia Effect](https://ui-patterns.com/patterns/nostalgia-effect).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Social
- Subgroup: Social biases
- Source breadcrumb: Design Patterns > Social > Social biases > Nostalgia Effect

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/nostalgia-effect
- Page title: Nostalgia Effect design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale, Discussion
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 30 words on source page
- Usage: 21 words on source page
- Solution: 116 words on source page
- Rationale: 59 words on source page
- Discussion: 148 words on source page

## Source Navigation

- Previous source navigation: Cards
- Next source navigation: Delighters


<!-- ===== ui-patterns/wiki/concepts/patterns/notifications.md ===== -->

---
title: "Notifications"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/notifications"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/notifications"
source_slug: "notifications"
track: "User Interface Design Patterns"
group: "Navigation"
subgroup: "Jumping in hierarchy"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Across devices"
  - "Minimize interruption"
  - "Allow escape"
  - "Provide summaries"
  - "Provide actions"
example_count: 4
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Notifications

> Catalog pointer for the UI Patterns source page: [Notifications](https://ui-patterns.com/patterns/notifications).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Navigation
- Subgroup: Jumping in hierarchy
- Source breadcrumb: Design Patterns > Navigation > Jumping in hierarchy > Notifications

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/notifications
- Page title: Notifications design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Across devices, Minimize interruption, Allow escape, Provide summaries, Provide actions
- Example screenshots detected at source: 4
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 11 words on source page
- Example: 79 words on source page
- Usage: 70 words on source page
- Solution: 324 words on source page
- Across devices: 50 words on source page
- Minimize interruption: 63 words on source page
- Allow escape: 17 words on source page
- Provide summaries: 35 words on source page
- Provide actions: 59 words on source page

## Source Navigation

- Previous source navigation: Paywall
- Next source navigation: Auto-sharing


<!-- ===== ui-patterns/wiki/concepts/patterns/optimism-bias.md ===== -->

---
title: "Optimism Bias"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/optimism-bias"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/optimism-bias"
source_slug: "optimism-bias"
track: "Persuasive Design Patterns"
group: "Cognition"
subgroup: "Loss Aversion"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Optimism Bias

> Catalog pointer for the UI Patterns source page: [Optimism Bias](https://ui-patterns.com/patterns/optimism-bias).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Cognition
- Subgroup: Loss Aversion
- Source breadcrumb: Design Patterns > Cognition > Loss Aversion > Optimism Bias

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/optimism-bias
- Page title: Optimism Bias design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 40 words on source page
- Usage: 30 words on source page
- Solution: 95 words on source page
- Rationale: 180 words on source page

## Source Navigation

- Previous source navigation: Cards
- Next source navigation: Delighters


<!-- ===== ui-patterns/wiki/concepts/patterns/pagination.md ===== -->

---
title: "Pagination"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Pagination"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Pagination"
source_slug: "Pagination"
track: "User Interface Design Patterns"
group: "Navigation"
subgroup: "Content"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 13
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Pagination

> Catalog pointer for the UI Patterns source page: [Pagination](https://ui-patterns.com/patterns/Pagination).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Navigation
- Subgroup: Content
- Source breadcrumb: Design Patterns > Navigation > Content > Pagination

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Pagination
- Page title: Pagination design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 13
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 14 words on source page
- Example: 49 words on source page
- Usage: 42 words on source page
- Solution: 86 words on source page
- Rationale: 159 words on source page

## Source Navigation

- Previous source navigation: Blank Slate
- Next source navigation: Archive


<!-- ===== ui-patterns/wiki/concepts/patterns/password-strength-meter.md ===== -->

---
title: "Password Strength Meter"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/PasswordStrengthMeter"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/PasswordStrengthMeter"
source_slug: "PasswordStrengthMeter"
track: "User Interface Design Patterns"
group: "Getting input"
subgroup: "Forms"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "How strong a password?"
  - "What is a strong password?"
  - "Dictionary attacks"
  - "Choosing an appropriate level of password strength"
  - "General guidelines on choosing a password"
  - "Rationale"
example_count: 6
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Password Strength Meter

> Catalog pointer for the UI Patterns source page: [Password Strength Meter](https://ui-patterns.com/patterns/PasswordStrengthMeter).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Getting input
- Subgroup: Forms
- Source breadcrumb: Design Patterns > Getting input > Forms > Password Strength Meter

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/PasswordStrengthMeter
- Page title: Password Strength Meter design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, How strong a password?, What is a strong password?, Dictionary attacks, Choosing an appropriate level of password strength, General guidelines on choosing a password, Rationale
- Example screenshots detected at source: 6
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 17 words on source page
- Example: 73 words on source page
- Usage: 72 words on source page
- Solution: 619 words on source page
- How strong a password?: 107 words on source page
- What is a strong password?: 114 words on source page
- Dictionary attacks: 101 words on source page
- Choosing an appropriate level of password strength: 48 words on source page
- General guidelines on choosing a password: 143 words on source page
- Rationale: 105 words on source page

## Source Navigation

- Previous source navigation: Inline Help Box
- Next source navigation: Lazy Registration


<!-- ===== ui-patterns/wiki/concepts/patterns/pattern-recognition.md ===== -->

---
title: "Pattern Recognition"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Pattern-recognition"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Pattern-recognition"
source_slug: "Pattern-recognition"
track: "Persuasive Design Patterns"
group: "Perception and memory"
subgroup: "Comprehension"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Pattern Recognition

> Catalog pointer for the UI Patterns source page: [Pattern Recognition](https://ui-patterns.com/patterns/Pattern-recognition).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Perception and memory
- Subgroup: Comprehension
- Source breadcrumb: Design Patterns > Perception and memory > Comprehension > Pattern Recognition

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Pattern-recognition
- Page title: Pattern Recognition design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 32 words on source page
- Usage: 16 words on source page
- Solution: 160 words on source page
- Rationale: 141 words on source page

## Source Navigation

- Previous source navigation: Tunnelling
- Next source navigation: Serial Positioning Effect


<!-- ===== ui-patterns/wiki/concepts/patterns/pay-to-promote.md ===== -->

---
title: "Pay To Promote"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/pay-to-promote"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/pay-to-promote"
source_slug: "pay-to-promote"
track: "User Interface Design Patterns"
group: "Getting input"
subgroup: "Community driven"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Discussion"
example_count: 2
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Pay To Promote

> Catalog pointer for the UI Patterns source page: [Pay To Promote](https://ui-patterns.com/patterns/pay-to-promote).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Getting input
- Subgroup: Community driven
- Source breadcrumb: Design Patterns > Getting input > Community driven > Pay To Promote

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/pay-to-promote
- Page title: Pay To Promote design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Discussion
- Example screenshots detected at source: 2
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 22 words on source page
- Example: 59 words on source page
- Usage: 42 words on source page
- Solution: 114 words on source page
- Discussion: 41 words on source page

## Source Navigation

- Previous source navigation: Testimonials
- Next source navigation: Invite friends


<!-- ===== ui-patterns/wiki/concepts/patterns/paywall.md ===== -->

---
title: "Paywall"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Paywall"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Paywall"
source_slug: "Paywall"
track: "User Interface Design Patterns"
group: "Onboarding"
subgroup: "Registration"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Strategies"
  - "Payment doesn’t have to be monetary"
  - "Rationale"
example_count: 13
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Paywall

> Catalog pointer for the UI Patterns source page: [Paywall](https://ui-patterns.com/patterns/Paywall).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Onboarding
- Subgroup: Registration
- Source breadcrumb: Design Patterns > Onboarding > Registration > Paywall

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Paywall
- Page title: Paywall design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Strategies, Payment doesn’t have to be monetary, Rationale
- Example screenshots detected at source: 13
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 15 words on source page
- Example: 103 words on source page
- Usage: 75 words on source page
- Solution: 416 words on source page
- Strategies: 119 words on source page
- Payment doesn’t have to be monetary: 225 words on source page
- Rationale: 55 words on source page

## Source Navigation

- Previous source navigation: Slideshow
- Next source navigation: Leaderboard


<!-- ===== ui-patterns/wiki/concepts/patterns/peak-end-rule.md ===== -->

---
title: "Peak-end rule"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Peakend-rule"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Peakend-rule"
source_slug: "Peakend-rule"
track: "Persuasive Design Patterns"
group: "Cognition"
subgroup: "Other cognitive biases"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
  - "Discussion"
  - "Why the peak is memorable"
  - "Why the end is memorable"
example_count: 1
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Peak-end rule

> Catalog pointer for the UI Patterns source page: [Peak-end rule](https://ui-patterns.com/patterns/Peakend-rule).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Cognition
- Subgroup: Other cognitive biases
- Source breadcrumb: Design Patterns > Cognition > Other cognitive biases > Peak-end rule

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Peakend-rule
- Page title: Peak-end rule design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale, Discussion, Why the peak is memorable, Why the end is memorable
- Example screenshots detected at source: 1
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 16 words on source page
- Example: 30 words on source page
- Usage: 29 words on source page
- Solution: 246 words on source page
- Rationale: 426 words on source page
- Discussion: 381 words on source page
- Why the peak is memorable: 43 words on source page
- Why the end is memorable: 57 words on source page

## Source Navigation

- Previous source navigation: Scarcity
- Next source navigation: Social Proof


<!-- ===== ui-patterns/wiki/concepts/patterns/periodic-events.md ===== -->

---
title: "Periodic Events"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/periodic-events"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/periodic-events"
source_slug: "periodic-events"
track: "Persuasive Design Patterns"
group: "Game mechanics"
subgroup: "Gameplay design"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Periodic Events

> Catalog pointer for the UI Patterns source page: [Periodic Events](https://ui-patterns.com/patterns/periodic-events).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Game mechanics
- Subgroup: Gameplay design
- Source breadcrumb: Design Patterns > Game mechanics > Gameplay design > Periodic Events

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/periodic-events
- Page title: Periodic Events design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 31 words on source page
- Usage: 14 words on source page
- Solution: 136 words on source page
- Rationale: 134 words on source page

## Source Navigation

- Previous source navigation: Cards
- Next source navigation: Delighters


<!-- ===== ui-patterns/wiki/concepts/patterns/picture-superiority-effect.md ===== -->

---
title: "Picture Superiority Effect"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/picture-superiority-effect"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/picture-superiority-effect"
source_slug: "picture-superiority-effect"
track: "Persuasive Design Patterns"
group: "Perception and memory"
subgroup: "Attention"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Picture Superiority Effect

> Catalog pointer for the UI Patterns source page: [Picture Superiority Effect](https://ui-patterns.com/patterns/picture-superiority-effect).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Perception and memory
- Subgroup: Attention
- Source breadcrumb: Design Patterns > Perception and memory > Attention > Picture Superiority Effect

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/picture-superiority-effect
- Page title: Picture Superiority Effect design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 33 words on source page
- Usage: 25 words on source page
- Solution: 104 words on source page
- Rationale: 197 words on source page

## Source Navigation

- Previous source navigation: Temptation Bundling
- Next source navigation: Hedonic Adaptation


<!-- ===== ui-patterns/wiki/concepts/patterns/playthrough.md ===== -->

---
title: "Playthrough"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/playthrough"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/playthrough"
source_slug: "playthrough"
track: "User Interface Design Patterns"
group: "Onboarding"
subgroup: "Guidance"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Let users learn through real tasks"
  - "Continue the experience seamlessly into the full product"
  - "Provide a skip option"
  - "Don’t drag it out"
  - "Rationale"
example_count: 3
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Playthrough

> Catalog pointer for the UI Patterns source page: [Playthrough](https://ui-patterns.com/patterns/playthrough).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Onboarding
- Subgroup: Guidance
- Source breadcrumb: Design Patterns > Onboarding > Guidance > Playthrough

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/playthrough
- Page title: Playthrough design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Let users learn through real tasks, Continue the experience seamlessly into the full product, Provide a skip option, Don’t drag it out, Rationale
- Example screenshots detected at source: 3
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 14 words on source page
- Example: 202 words on source page
- Usage: 165 words on source page
- Solution: 291 words on source page
- Let users learn through real tasks: 38 words on source page
- Continue the experience seamlessly into the full product: 30 words on source page
- Provide a skip option: 20 words on source page
- Don’t drag it out: 45 words on source page
- Rationale: 68 words on source page

## Source Navigation

- Previous source navigation: Cognitive Dissonance
- Next source navigation: Drag and drop


<!-- ===== ui-patterns/wiki/concepts/patterns/positive-mimicry.md ===== -->

---
title: "Positive Mimicry"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Positive-mimicry"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Positive-mimicry"
source_slug: "Positive-mimicry"
track: "Persuasive Design Patterns"
group: "Social"
subgroup: "Social biases"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Powerful Pairings"
  - "Rationale"
  - "Discussion"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Positive Mimicry

> Catalog pointer for the UI Patterns source page: [Positive Mimicry](https://ui-patterns.com/patterns/Positive-mimicry).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Social
- Subgroup: Social biases
- Source breadcrumb: Design Patterns > Social > Social biases > Positive Mimicry

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Positive-mimicry
- Page title: Positive Mimicry design pattern
- Section headings available at source: Problem summary, Usage, Solution, Powerful Pairings, Rationale, Discussion
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 35 words on source page
- Usage: 23 words on source page
- Solution: 696 words on source page
- Powerful Pairings: 204 words on source page
- Rationale: 176 words on source page
- Discussion: 508 words on source page

## Source Navigation

- Previous source navigation: Variable Rewards
- Next source navigation: Self-Expression


<!-- ===== ui-patterns/wiki/concepts/patterns/praise.md ===== -->

---
title: "Praise"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Praise"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Praise"
source_slug: "Praise"
track: "Persuasive Design Patterns"
group: "Game mechanics"
subgroup: "Gameplay rewards"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 2
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Praise

> Catalog pointer for the UI Patterns source page: [Praise](https://ui-patterns.com/patterns/Praise).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Game mechanics
- Subgroup: Gameplay rewards
- Source breadcrumb: Design Patterns > Game mechanics > Gameplay rewards > Praise

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Praise
- Page title: Praise design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 2
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 16 words on source page
- Example: 66 words on source page
- Usage: 45 words on source page
- Solution: 170 words on source page
- Rationale: 32 words on source page

## Source Navigation

- Previous source navigation: Value Attribution
- Next source navigation: Trigger


<!-- ===== ui-patterns/wiki/concepts/patterns/present-bias.md ===== -->

---
title: "Present Bias"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/present-bias"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/present-bias"
source_slug: "present-bias"
track: "Persuasive Design Patterns"
group: "Cognition"
subgroup: "Other cognitive biases"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Present Bias

> Catalog pointer for the UI Patterns source page: [Present Bias](https://ui-patterns.com/patterns/present-bias).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Cognition
- Subgroup: Other cognitive biases
- Source breadcrumb: Design Patterns > Cognition > Other cognitive biases > Present Bias

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/present-bias
- Page title: Present Bias design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 47 words on source page
- Usage: 33 words on source page
- Solution: 104 words on source page
- Rationale: 208 words on source page

## Source Navigation

- Previous source navigation: Temptation Bundling
- Next source navigation: Hedonic Adaptation


<!-- ===== ui-patterns/wiki/concepts/patterns/preview.md ===== -->

---
title: "Preview"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/LivePreview"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/LivePreview"
source_slug: "LivePreview"
track: "User Interface Design Patterns"
group: "Getting input"
subgroup: "Forms"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 3
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Preview

> Catalog pointer for the UI Patterns source page: [Preview](https://ui-patterns.com/patterns/LivePreview).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Getting input
- Subgroup: Forms
- Source breadcrumb: Design Patterns > Getting input > Forms > Preview

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/LivePreview
- Page title: Preview design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 3
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 18 words on source page
- Example: 62 words on source page
- Usage: 61 words on source page
- Solution: 58 words on source page
- Rationale: 81 words on source page

## Source Navigation

- Previous source navigation: Wiki
- Next source navigation: Tagging


<!-- ===== ui-patterns/wiki/concepts/patterns/pricing-table.md ===== -->

---
title: "Pricing table"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/PricingTable"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/PricingTable"
source_slug: "PricingTable"
track: "User Interface Design Patterns"
group: "Miscellaneous"
subgroup: "Shopping"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
  - "Discussion"
  - "Apply hooks"
  - "Highlight why users should pay for your product"
  - "First one free"
  - "Order plans by descending price"
  - "Add decoys"
  - "The Goldilocks effect: We are aversive toward extremes"
  - "Let people know what they’re missing"
  - "Showcase differences with extremes"
example_count: 13
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Pricing table

> Catalog pointer for the UI Patterns source page: [Pricing table](https://ui-patterns.com/patterns/PricingTable).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Miscellaneous
- Subgroup: Shopping
- Source breadcrumb: Design Patterns > Miscellaneous > Shopping > Pricing table

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/PricingTable
- Page title: Pricing table design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale, Discussion, Apply hooks, Highlight why users should pay for your product, First one free, Order plans by descending price, Add decoys, The Goldilocks effect: We are aversive toward extremes, Let people know what they’re missing, Showcase differences with extremes
- Example screenshots detected at source: 13
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 17 words on source page
- Example: 83 words on source page
- Usage: 82 words on source page
- Solution: 233 words on source page
- Rationale: 33 words on source page
- Discussion: 840 words on source page
- Apply hooks: 308 words on source page
- Highlight why users should pay for your product: 59 words on source page
- First one free: 61 words on source page
- Order plans by descending price: 95 words on source page
- Add decoys: 30 words on source page
- The Goldilocks effect: We are aversive toward extremes: 102 words on source page
- Let people know what they’re missing: 34 words on source page
- Showcase differences with extremes: 42 words on source page

## Source Navigation

- Previous source navigation: Competition
- Next source navigation: Product page


<!-- ===== ui-patterns/wiki/concepts/patterns/priming-effect.md ===== -->

---
title: "Priming Effect"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/priming-effect"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/priming-effect"
source_slug: "priming-effect"
track: "Persuasive Design Patterns"
group: "Cognition"
subgroup: "Other cognitive biases"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
  - "Discussion"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Priming Effect

> Catalog pointer for the UI Patterns source page: [Priming Effect](https://ui-patterns.com/patterns/priming-effect).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Cognition
- Subgroup: Other cognitive biases
- Source breadcrumb: Design Patterns > Cognition > Other cognitive biases > Priming Effect

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/priming-effect
- Page title: Priming Effect design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale, Discussion
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 38 words on source page
- Usage: 27 words on source page
- Solution: 61 words on source page
- Rationale: 59 words on source page
- Discussion: 259 words on source page

## Source Navigation

- Previous source navigation: Appointment Dynamic
- Next source navigation: Fresh Start Effect


<!-- ===== ui-patterns/wiki/concepts/patterns/privileges.md ===== -->

---
title: "Privileges"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Powers"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Powers"
source_slug: "Powers"
track: "Persuasive Design Patterns"
group: "Game mechanics"
subgroup: "Gameplay rewards"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Reward the contributor and curator roles"
  - "Grant roles"
  - "Instil a sense of self-determination"
  - "Common powers given to users"
  - "Rationale"
example_count: 2
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Privileges

> Catalog pointer for the UI Patterns source page: [Privileges](https://ui-patterns.com/patterns/Powers).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Game mechanics
- Subgroup: Gameplay rewards
- Source breadcrumb: Design Patterns > Game mechanics > Gameplay rewards > Privileges

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Powers
- Page title: Privileges design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Reward the contributor and curator roles, Grant roles, Instil a sense of self-determination, Common powers given to users, Rationale
- Example screenshots detected at source: 2
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 14 words on source page
- Example: 64 words on source page
- Usage: 35 words on source page
- Solution: 370 words on source page
- Reward the contributor and curator roles: 124 words on source page
- Grant roles: 36 words on source page
- Instil a sense of self-determination: 60 words on source page
- Common powers given to users: 74 words on source page
- Rationale: 161 words on source page

## Source Navigation

- Previous source navigation: Value Attribution
- Next source navigation: Trigger


<!-- ===== ui-patterns/wiki/concepts/patterns/product-page.md ===== -->

---
title: "Product page"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/ProductPage"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/ProductPage"
source_slug: "ProductPage"
track: "User Interface Design Patterns"
group: "Miscellaneous"
subgroup: "Shopping"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
  - "Discussion"
example_count: 13
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Product page

> Catalog pointer for the UI Patterns source page: [Product page](https://ui-patterns.com/patterns/ProductPage).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Miscellaneous
- Subgroup: Shopping
- Source breadcrumb: Design Patterns > Miscellaneous > Shopping > Product page

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/ProductPage
- Page title: Product page design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale, Discussion
- Example screenshots detected at source: 13
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 22 words on source page
- Example: 64 words on source page
- Usage: 35 words on source page
- Solution: 155 words on source page
- Rationale: 31 words on source page
- Discussion: 452 words on source page

## Source Navigation

- Previous source navigation: Pricing table
- Next source navigation: Liking


<!-- ===== ui-patterns/wiki/concepts/patterns/progressive-disclosure.md ===== -->

---
title: "Progressive Disclosure"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/ProgressiveDisclosure"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/ProgressiveDisclosure"
source_slug: "ProgressiveDisclosure"
track: "User Interface Design Patterns"
group: "Navigation"
subgroup: "Content"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 1
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Progressive Disclosure

> Catalog pointer for the UI Patterns source page: [Progressive Disclosure](https://ui-patterns.com/patterns/ProgressiveDisclosure).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Navigation
- Subgroup: Content
- Source breadcrumb: Design Patterns > Navigation > Content > Progressive Disclosure

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/ProgressiveDisclosure
- Page title: Progressive Disclosure design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 1
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 27 words on source page
- Example: 54 words on source page
- Usage: 10 words on source page
- Solution: 62 words on source page
- Rationale: 227 words on source page

## Source Navigation

- Previous source navigation: Collectible Achievements
- Next source navigation: Activity Stream


<!-- ===== ui-patterns/wiki/concepts/patterns/prolonged-play.md ===== -->

---
title: "Prolonged Play"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Prolonged-play"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Prolonged-play"
source_slug: "Prolonged-play"
track: "Persuasive Design Patterns"
group: "Game mechanics"
subgroup: "Gameplay rewards"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Examples"
  - "Rationale"
example_count: 4
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Prolonged Play

> Catalog pointer for the UI Patterns source page: [Prolonged Play](https://ui-patterns.com/patterns/Prolonged-play).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Game mechanics
- Subgroup: Gameplay rewards
- Source breadcrumb: Design Patterns > Game mechanics > Gameplay rewards > Prolonged Play

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Prolonged-play
- Page title: Prolonged Play design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Examples, Rationale
- Example screenshots detected at source: 4
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 16 words on source page
- Example: 36 words on source page
- Usage: 12 words on source page
- Solution: 443 words on source page
- Examples: 136 words on source page
- Rationale: 134 words on source page

## Source Navigation

- Previous source navigation: Value Attribution
- Next source navigation: Trigger


<!-- ===== ui-patterns/wiki/concepts/patterns/pull-to-refresh.md ===== -->

---
title: "Pull to refresh"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/pull-to-refresh"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/pull-to-refresh"
source_slug: "pull-to-refresh"
track: "User Interface Design Patterns"
group: "Navigation"
subgroup: "Gestures"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Immediate visual feedback after the action"
  - "Refresh indicator should only be triggered by user action"
  - "Meaningful state transitions"
  - "Rationale"
  - "Why should we use pull to refresh?"
  - "Discussion"
  - "Visible “refresh” button vs Hidden pull-to-refresh gesture"
  - "When you should use visible “Refresh” button or auto-update instead of Pull-to-refresh"
  - "Thumb-reach issue on iPad"
  - "Augmented Pull-to-refresh"
example_count: 11
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Pull to refresh

> Catalog pointer for the UI Patterns source page: [Pull to refresh](https://ui-patterns.com/patterns/pull-to-refresh).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Navigation
- Subgroup: Gestures
- Source breadcrumb: Design Patterns > Navigation > Gestures > Pull to refresh

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/pull-to-refresh
- Page title: Pull to refresh design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Immediate visual feedback after the action, Refresh indicator should only be triggered by user action, Meaningful state transitions, Rationale, Why should we use pull to refresh?, Discussion, Visible “refresh” button vs Hidden pull-to-refresh gesture, When you should use visible “Refresh” button or auto-update instead of Pull-to-refresh, Thumb-reach issue on iPad, Augmented Pull-to-refresh
- Example screenshots detected at source: 11
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 16 words on source page
- Example: 86 words on source page
- Usage: 63 words on source page
- Solution: 231 words on source page
- Immediate visual feedback after the action: 80 words on source page
- Refresh indicator should only be triggered by user action: 42 words on source page
- Meaningful state transitions: 47 words on source page
- Rationale: 263 words on source page
- Why should we use pull to refresh?: 256 words on source page
- Discussion: 561 words on source page
- Visible “refresh” button vs Hidden pull-to-refresh gesture: 75 words on source page
- When you should use visible “Refresh” button or auto-update instead of Pull-to-refresh: 199 words on source page
- Thumb-reach issue on iPad: 56 words on source page
- Augmented Pull-to-refresh: 121 words on source page

## Source Navigation

- Previous source navigation: Friend
- Next source navigation: Rule Builder


<!-- ===== ui-patterns/wiki/concepts/patterns/rate-content.md ===== -->

---
title: "Rate Content"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/RateContent"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/RateContent"
source_slug: "RateContent"
track: "User Interface Design Patterns"
group: "Getting input"
subgroup: "Community driven"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
  - "Discussion"
example_count: 13
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Rate Content

> Catalog pointer for the UI Patterns source page: [Rate Content](https://ui-patterns.com/patterns/RateContent).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Getting input
- Subgroup: Community driven
- Source breadcrumb: Design Patterns > Getting input > Community driven > Rate Content

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/RateContent
- Page title: Rate Content design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale, Discussion
- Example screenshots detected at source: 13
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 22 words on source page
- Example: 160 words on source page
- Usage: 126 words on source page
- Solution: 362 words on source page
- Rationale: 63 words on source page
- Discussion: 436 words on source page

## Source Navigation

- Previous source navigation: Input Feedback
- Next source navigation: Image Zoom


<!-- ===== ui-patterns/wiki/concepts/patterns/reaction.md ===== -->

---
title: "Reaction"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/reaction"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/reaction"
source_slug: "reaction"
track: "User Interface Design Patterns"
group: "Social"
subgroup: "Social interactions"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 1
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Reaction

> Catalog pointer for the UI Patterns source page: [Reaction](https://ui-patterns.com/patterns/reaction).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Social
- Subgroup: Social interactions
- Source breadcrumb: Design Patterns > Social > Social interactions > Reaction

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/reaction
- Page title: Reaction design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 1
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 11 words on source page
- Example: 64 words on source page
- Usage: 42 words on source page
- Solution: 44 words on source page
- Rationale: 23 words on source page

## Source Navigation

- Previous source navigation: Frequently Asked Questions (FAQ)
- Next source navigation: Pull to refresh


<!-- ===== ui-patterns/wiki/concepts/patterns/reciprocation.md ===== -->

---
title: "Reciprocation"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Reciprocation"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Reciprocation"
source_slug: "Reciprocation"
track: "Persuasive Design Patterns"
group: "Social"
subgroup: "Social biases"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
  - "Discussion"
  - "Reciprocity Decay"
  - "Powerful Pairings"
  - "Ethical Recommendations"
example_count: 3
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Reciprocation

> Catalog pointer for the UI Patterns source page: [Reciprocation](https://ui-patterns.com/patterns/Reciprocation).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Social
- Subgroup: Social biases
- Source breadcrumb: Design Patterns > Social > Social biases > Reciprocation

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Reciprocation
- Page title: Reciprocation design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale, Discussion, Reciprocity Decay, Powerful Pairings, Ethical Recommendations
- Example screenshots detected at source: 3
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 8 words on source page
- Example: 43 words on source page
- Usage: 19 words on source page
- Solution: 129 words on source page
- Rationale: 93 words on source page
- Discussion: 1166 words on source page
- Reciprocity Decay: 112 words on source page
- Powerful Pairings: 280 words on source page
- Ethical Recommendations: 246 words on source page

## Source Navigation

- Previous source navigation: Simulation
- Next source navigation: Variable Rewards


<!-- ===== ui-patterns/wiki/concepts/patterns/recognition-over-recall.md ===== -->

---
title: "Recognition over Recall"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Recognition-over-recall"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Recognition-over-recall"
source_slug: "Recognition-over-recall"
track: "Persuasive Design Patterns"
group: "Perception and memory"
subgroup: "Comprehension"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Minimize need to recall"
  - "Rationale"
  - "Recognition vs Recall"
  - "Recognition doesn’t involve origin, context, or relevance"
example_count: 12
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Recognition over Recall

> Catalog pointer for the UI Patterns source page: [Recognition over Recall](https://ui-patterns.com/patterns/Recognition-over-recall).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Perception and memory
- Subgroup: Comprehension
- Source breadcrumb: Design Patterns > Perception and memory > Comprehension > Recognition over Recall

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Recognition-over-recall
- Page title: Recognition over Recall design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Minimize need to recall, Rationale, Recognition vs Recall, Recognition doesn’t involve origin, context, or relevance
- Example screenshots detected at source: 12
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 16 words on source page
- Example: 98 words on source page
- Usage: 78 words on source page
- Solution: 195 words on source page
- Minimize need to recall: 26 words on source page
- Rationale: 324 words on source page
- Recognition vs Recall: 96 words on source page
- Recognition doesn’t involve origin, context, or relevance: 78 words on source page

## Source Navigation

- Previous source navigation: Tunnelling
- Next source navigation: Serial Positioning Effect


<!-- ===== ui-patterns/wiki/concepts/patterns/reduction.md ===== -->

---
title: "Reduction"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Reduction"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Reduction"
source_slug: "Reduction"
track: "Persuasive Design Patterns"
group: "Perception and memory"
subgroup: "Attention"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Reduction implied to navigation."
  - "Reduction based on what other users did"
  - "Rationale"
example_count: 1
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Reduction

> Catalog pointer for the UI Patterns source page: [Reduction](https://ui-patterns.com/patterns/Reduction).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Perception and memory
- Subgroup: Attention
- Source breadcrumb: Design Patterns > Perception and memory > Attention > Reduction

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Reduction
- Page title: Reduction design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Reduction implied to navigation., Reduction based on what other users did, Rationale
- Example screenshots detected at source: 1
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 18 words on source page
- Example: 88 words on source page
- Usage: 57 words on source page
- Solution: 355 words on source page
- Reduction implied to navigation.: 17 words on source page
- Reduction based on what other users did: 194 words on source page
- Rationale: 224 words on source page

## Source Navigation

- Previous source navigation: Limited Choice
- Next source navigation: Anchoring


<!-- ===== ui-patterns/wiki/concepts/patterns/reputation.md ===== -->

---
title: "Reputation"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/reputation"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/reputation"
source_slug: "reputation"
track: "Persuasive Design Patterns"
group: "Social"
subgroup: "Social biases"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Using Aristotle’s triad of appeals to communicate Reputation"
  - "Getting a design that showcases reputation right"
  - "Powerful pairings"
  - "Rationale"
  - "Discussion"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Reputation

> Catalog pointer for the UI Patterns source page: [Reputation](https://ui-patterns.com/patterns/reputation).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Social
- Subgroup: Social biases
- Source breadcrumb: Design Patterns > Social > Social biases > Reputation

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/reputation
- Page title: Reputation design pattern
- Section headings available at source: Problem summary, Usage, Solution, Using Aristotle’s triad of appeals to communicate Reputation, Getting a design that showcases reputation right, Powerful pairings, Rationale, Discussion
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 104 words on source page
- Usage: 87 words on source page
- Solution: 1106 words on source page
- Using Aristotle’s triad of appeals to communicate Reputation: 290 words on source page
- Getting a design that showcases reputation right: 425 words on source page
- Powerful pairings: 148 words on source page
- Rationale: 115 words on source page
- Discussion: 419 words on source page

## Source Navigation

- Previous source navigation: Cards
- Next source navigation: Delighters


<!-- ===== ui-patterns/wiki/concepts/patterns/retaliation.md ===== -->

---
title: "Retaliation"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/revenge"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/revenge"
source_slug: "revenge"
track: "Persuasive Design Patterns"
group: "Social"
subgroup: "Social biases"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
  - "Discussion"
  - "Powerful pairings"
  - "Ethical Recommendations"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Retaliation

> Catalog pointer for the UI Patterns source page: [Retaliation](https://ui-patterns.com/patterns/revenge).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Social
- Subgroup: Social biases
- Source breadcrumb: Design Patterns > Social > Social biases > Retaliation

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/revenge
- Page title: Retaliation design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale, Discussion, Powerful pairings, Ethical Recommendations
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 65 words on source page
- Usage: 60 words on source page
- Solution: 103 words on source page
- Rationale: 291 words on source page
- Discussion: 1030 words on source page
- Powerful pairings: 207 words on source page
- Ethical Recommendations: 273 words on source page

## Source Navigation

- Previous source navigation: Cards
- Next source navigation: Delighters


<!-- ===== ui-patterns/wiki/concepts/patterns/role-playing.md ===== -->

---
title: "Role Playing"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Roleplaying"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Roleplaying"
source_slug: "Roleplaying"
track: "Persuasive Design Patterns"
group: "Social"
subgroup: "Social biases"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Role Playing

> Catalog pointer for the UI Patterns source page: [Role Playing](https://ui-patterns.com/patterns/Roleplaying).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Social
- Subgroup: Social biases
- Source breadcrumb: Design Patterns > Social > Social biases > Role Playing

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Roleplaying
- Page title: Role Playing design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 48 words on source page
- Usage: 41 words on source page
- Solution: 125 words on source page
- Rationale: 173 words on source page

## Source Navigation

- Previous source navigation: Event Calendar
- Next source navigation: Loss Aversion


<!-- ===== ui-patterns/wiki/concepts/patterns/rule-builder.md ===== -->

---
title: "Rule Builder"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/rule-builder"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/rule-builder"
source_slug: "rule-builder"
track: "User Interface Design Patterns"
group: "Getting input"
subgroup: "Forms"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Any or all"
  - "Treat each rule type differently?"
  - "Adding and removing rules"
  - "Rationale"
  - "Discussion"
  - "Pattern authors"
example_count: 6
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Rule Builder

> Catalog pointer for the UI Patterns source page: [Rule Builder](https://ui-patterns.com/patterns/rule-builder).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Getting input
- Subgroup: Forms
- Source breadcrumb: Design Patterns > Getting input > Forms > Rule Builder

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/rule-builder
- Page title: Rule Builder design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Any or all, Treat each rule type differently?, Adding and removing rules, Rationale, Discussion, Pattern authors
- Example screenshots detected at source: 6
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 17 words on source page
- Example: 110 words on source page
- Usage: 85 words on source page
- Solution: 284 words on source page
- Any or all: 63 words on source page
- Treat each rule type differently?: 95 words on source page
- Adding and removing rules: 81 words on source page
- Rationale: 82 words on source page
- Discussion: 23 words on source page
- Pattern authors: 4 words on source page

## Source Navigation

- Previous source navigation: Pull to refresh
- Next source navigation: Halo Effect


<!-- ===== ui-patterns/wiki/concepts/patterns/scarcity.md ===== -->

---
title: "Scarcity"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Scarcity"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Scarcity"
source_slug: "Scarcity"
track: "Persuasive Design Patterns"
group: "Cognition"
subgroup: "Scarcity"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Time-based scarcity"
  - "Stock scarcity"
  - "Restrictions on information (or merely scarce)"
  - "Rationale"
  - "Our weakness for shortcuts"
  - "We hate to loose the freedoms we already have"
  - "Discussion"
  - "Optimal conditions for scarcity to work"
  - "Make a decision today or loose out forever"
  - "Origins of the term Scarcity"
example_count: 7
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Scarcity

> Catalog pointer for the UI Patterns source page: [Scarcity](https://ui-patterns.com/patterns/Scarcity).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Cognition
- Subgroup: Scarcity
- Source breadcrumb: Design Patterns > Cognition > Scarcity > Scarcity

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Scarcity
- Page title: Scarcity design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Time-based scarcity, Stock scarcity, Restrictions on information (or merely scarce), Rationale, Our weakness for shortcuts, We hate to loose the freedoms we already have, Discussion, Optimal conditions for scarcity to work, Make a decision today or loose out forever, Origins of the term Scarcity
- Example screenshots detected at source: 7
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 16 words on source page
- Example: 73 words on source page
- Usage: 63 words on source page
- Solution: 297 words on source page
- Time-based scarcity: 111 words on source page
- Stock scarcity: 92 words on source page
- Restrictions on information (or merely scarce): 76 words on source page
- Rationale: 257 words on source page
- Our weakness for shortcuts: 46 words on source page
- We hate to loose the freedoms we already have: 66 words on source page
- Discussion: 544 words on source page
- Optimal conditions for scarcity to work: 174 words on source page
- Make a decision today or loose out forever: 223 words on source page
- Origins of the term Scarcity: 45 words on source page

## Source Navigation

- Previous source navigation: Storytelling
- Next source navigation: Peak-end rule


<!-- ===== ui-patterns/wiki/concepts/patterns/search-filters.md ===== -->

---
title: "Search Filters"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/LiveFilter"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/LiveFilter"
source_slug: "LiveFilter"
track: "User Interface Design Patterns"
group: "Dealing with data"
subgroup: "Search"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 10
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Search Filters

> Catalog pointer for the UI Patterns source page: [Search Filters](https://ui-patterns.com/patterns/LiveFilter).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Dealing with data
- Subgroup: Search
- Source breadcrumb: Design Patterns > Dealing with data > Search > Search Filters

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/LiveFilter
- Page title: Search Filters design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 10
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 15 words on source page
- Example: 56 words on source page
- Usage: 45 words on source page
- Solution: 105 words on source page
- Rationale: 121 words on source page

## Source Navigation

- Previous source navigation: Archive
- Next source navigation: Wiki


<!-- ===== ui-patterns/wiki/concepts/patterns/self-expression.md ===== -->

---
title: "Self-Expression"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Self-expression"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Self-expression"
source_slug: "Self-expression"
track: "Persuasive Design Patterns"
group: "Social"
subgroup: "Social biases"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Self-Expression

> Catalog pointer for the UI Patterns source page: [Self-Expression](https://ui-patterns.com/patterns/Self-expression).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Social
- Subgroup: Social biases
- Source breadcrumb: Design Patterns > Social > Social biases > Self-Expression

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Self-expression
- Page title: Self-Expression design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 29 words on source page
- Usage: 18 words on source page
- Solution: 191 words on source page
- Rationale: 194 words on source page

## Source Navigation

- Previous source navigation: Value Attribution
- Next source navigation: Trigger


<!-- ===== ui-patterns/wiki/concepts/patterns/self-monitoring.md ===== -->

---
title: "Self-Monitoring"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/self-monitoring"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/self-monitoring"
source_slug: "self-monitoring"
track: "Persuasive Design Patterns"
group: "Game mechanics"
subgroup: "Gameplay design"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
  - "Discussion"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Self-Monitoring

> Catalog pointer for the UI Patterns source page: [Self-Monitoring](https://ui-patterns.com/patterns/self-monitoring).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Game mechanics
- Subgroup: Gameplay design
- Source breadcrumb: Design Patterns > Game mechanics > Gameplay design > Self-Monitoring

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/self-monitoring
- Page title: Self-Monitoring design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale, Discussion
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 28 words on source page
- Usage: 17 words on source page
- Solution: 102 words on source page
- Rationale: 66 words on source page
- Discussion: 147 words on source page

## Source Navigation

- Previous source navigation: Cards
- Next source navigation: Delighters


<!-- ===== ui-patterns/wiki/concepts/patterns/sequencing.md ===== -->

---
title: "Sequencing"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Sequencing"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Sequencing"
source_slug: "Sequencing"
track: "Persuasive Design Patterns"
group: "Perception and memory"
subgroup: "Comprehension"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Sequencing

> Catalog pointer for the UI Patterns source page: [Sequencing](https://ui-patterns.com/patterns/Sequencing).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Perception and memory
- Subgroup: Comprehension
- Source breadcrumb: Design Patterns > Perception and memory > Comprehension > Sequencing

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Sequencing
- Page title: Sequencing design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 44 words on source page
- Usage: 33 words on source page
- Solution: 165 words on source page
- Rationale: 145 words on source page

## Source Navigation

- Previous source navigation: Pattern Recognition
- Next source navigation: Competition


<!-- ===== ui-patterns/wiki/concepts/patterns/serial-positioning-effect.md ===== -->

---
title: "Serial Positioning Effect"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Serial-positioning-effect"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Serial-positioning-effect"
source_slug: "Serial-positioning-effect"
track: "Persuasive Design Patterns"
group: "Perception and memory"
subgroup: "Comprehension"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
  - "Discussion"
example_count: 1
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Serial Positioning Effect

> Catalog pointer for the UI Patterns source page: [Serial Positioning Effect](https://ui-patterns.com/patterns/Serial-positioning-effect).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Perception and memory
- Subgroup: Comprehension
- Source breadcrumb: Design Patterns > Perception and memory > Comprehension > Serial Positioning Effect

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Serial-positioning-effect
- Page title: Serial Positioning Effect design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale, Discussion
- Example screenshots detected at source: 1
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 16 words on source page
- Example: 53 words on source page
- Usage: 30 words on source page
- Solution: 266 words on source page
- Rationale: 170 words on source page
- Discussion: 166 words on source page

## Source Navigation

- Previous source navigation: Pattern Recognition
- Next source navigation: Competition


<!-- ===== ui-patterns/wiki/concepts/patterns/set-completion.md ===== -->

---
title: "Set Completion"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/set-completion"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/set-completion"
source_slug: "set-completion"
track: "Persuasive Design Patterns"
group: "Cognition"
subgroup: "Other cognitive biases"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Set Completion

> Catalog pointer for the UI Patterns source page: [Set Completion](https://ui-patterns.com/patterns/set-completion).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Cognition
- Subgroup: Other cognitive biases
- Source breadcrumb: Design Patterns > Cognition > Other cognitive biases > Set Completion

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/set-completion
- Page title: Set Completion design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 53 words on source page
- Usage: 36 words on source page
- Solution: 98 words on source page
- Rationale: 225 words on source page

## Source Navigation

- Previous source navigation: Cards
- Next source navigation: Delighters


<!-- ===== ui-patterns/wiki/concepts/patterns/settings.md ===== -->

---
title: "Settings"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/settings"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/settings"
source_slug: "settings"
track: "User Interface Design Patterns"
group: "Getting input"
subgroup: "Forms"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Provide an overview"
  - "Good Defaults"
  - "When to group"
example_count: 2
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Settings

> Catalog pointer for the UI Patterns source page: [Settings](https://ui-patterns.com/patterns/settings).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Getting input
- Subgroup: Forms
- Source breadcrumb: Design Patterns > Getting input > Forms > Settings

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/settings
- Page title: Settings design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Provide an overview, Good Defaults, When to group
- Example screenshots detected at source: 2
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 15 words on source page
- Example: 83 words on source page
- Usage: 64 words on source page
- Solution: 193 words on source page
- Provide an overview: 39 words on source page
- Good Defaults: 20 words on source page
- When to group: 69 words on source page

## Source Navigation

- Previous source navigation: Flagging & Reporting
- Next source navigation: Morphing Controls


<!-- ===== ui-patterns/wiki/concepts/patterns/shaping.md ===== -->

---
title: "Shaping"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/shaping"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/shaping"
source_slug: "shaping"
track: "Persuasive Design Patterns"
group: "Game mechanics"
subgroup: "Fundamentals of rewards"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Shaping

> Catalog pointer for the UI Patterns source page: [Shaping](https://ui-patterns.com/patterns/shaping).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Game mechanics
- Subgroup: Fundamentals of rewards
- Source breadcrumb: Design Patterns > Game mechanics > Fundamentals of rewards > Shaping

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/shaping
- Page title: Shaping design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 33 words on source page
- Usage: 25 words on source page
- Solution: 127 words on source page
- Rationale: 160 words on source page

## Source Navigation

- Previous source navigation: Temptation Bundling
- Next source navigation: Hedonic Adaptation


<!-- ===== ui-patterns/wiki/concepts/patterns/shopping-cart.md ===== -->

---
title: "Shopping Cart"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/ShoppingCart"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/ShoppingCart"
source_slug: "ShoppingCart"
track: "User Interface Design Patterns"
group: "Miscellaneous"
subgroup: "Shopping"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 13
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Shopping Cart

> Catalog pointer for the UI Patterns source page: [Shopping Cart](https://ui-patterns.com/patterns/ShoppingCart).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Miscellaneous
- Subgroup: Shopping
- Source breadcrumb: Design Patterns > Miscellaneous > Shopping > Shopping Cart

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/ShoppingCart
- Page title: Shopping Cart design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 13
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 13 words on source page
- Example: 109 words on source page
- Usage: 108 words on source page
- Solution: 166 words on source page
- Rationale: 103 words on source page

## Source Navigation

- Previous source navigation: Table Filter
- Next source navigation: Coupon


<!-- ===== ui-patterns/wiki/concepts/patterns/shortcut-dropdown.md ===== -->

---
title: "Shortcut Dropdown"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/ShortcutDropdown"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/ShortcutDropdown"
source_slug: "ShortcutDropdown"
track: "User Interface Design Patterns"
group: "Navigation"
subgroup: "Jumping in hierarchy"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 1
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Shortcut Dropdown

> Catalog pointer for the UI Patterns source page: [Shortcut Dropdown](https://ui-patterns.com/patterns/ShortcutDropdown).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Navigation
- Subgroup: Jumping in hierarchy
- Source breadcrumb: Design Patterns > Navigation > Jumping in hierarchy > Shortcut Dropdown

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/ShortcutDropdown
- Page title: Shortcut Dropdown design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 1
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 20 words on source page
- Example: 79 words on source page
- Usage: 78 words on source page
- Solution: 62 words on source page
- Rationale: 55 words on source page

## Source Navigation

- Previous source navigation: Breadcrumbs
- Next source navigation: Home Link


<!-- ===== ui-patterns/wiki/concepts/patterns/simulation.md ===== -->

---
title: "Simulation"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Simulation"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Simulation"
source_slug: "Simulation"
track: "Persuasive Design Patterns"
group: "Feedback"
subgroup: "Timing"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Simulation

> Catalog pointer for the UI Patterns source page: [Simulation](https://ui-patterns.com/patterns/Simulation).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Feedback
- Subgroup: Timing
- Source breadcrumb: Design Patterns > Feedback > Timing > Simulation

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Simulation
- Page title: Simulation design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 46 words on source page
- Usage: 34 words on source page
- Solution: 115 words on source page
- Rationale: 157 words on source page

## Source Navigation

- Previous source navigation: Negativity bias
- Next source navigation: Reciprocation


<!-- ===== ui-patterns/wiki/concepts/patterns/slideshow.md ===== -->

---
title: "Slideshow"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Slideshow"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Slideshow"
source_slug: "Slideshow"
track: "User Interface Design Patterns"
group: "Dealing with data"
subgroup: "Images"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Transitions"
  - "Numbers, bullets, or thumbnails"
  - "Focus attention"
  - "Buttons and good callout texts"
  - "Navigation"
  - "Full image or tabs with title"
  - "Rationale"
example_count: 13
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Slideshow

> Catalog pointer for the UI Patterns source page: [Slideshow](https://ui-patterns.com/patterns/Slideshow).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Dealing with data
- Subgroup: Images
- Source breadcrumb: Design Patterns > Dealing with data > Images > Slideshow

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Slideshow
- Page title: Slideshow design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Transitions, Numbers, bullets, or thumbnails, Focus attention, Buttons and good callout texts, Navigation, Full image or tabs with title, Rationale
- Example screenshots detected at source: 13
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 17 words on source page
- Example: 97 words on source page
- Usage: 91 words on source page
- Solution: 564 words on source page
- Transitions: 51 words on source page
- Numbers, bullets, or thumbnails: 94 words on source page
- Focus attention: 107 words on source page
- Buttons and good callout texts: 83 words on source page
- Navigation: 69 words on source page
- Full image or tabs with title: 114 words on source page
- Rationale: 71 words on source page

## Source Navigation

- Previous source navigation: Gallery
- Next source navigation: Paywall


<!-- ===== ui-patterns/wiki/concepts/patterns/social-proof.md ===== -->

---
title: "Social Proof"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Social-proof"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Social-proof"
source_slug: "Social-proof"
track: "Persuasive Design Patterns"
group: "Social"
subgroup: "Social biases"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "6 ways to use Social Proof"
  - "Appeal to logic, emotions, and to ethical character"
  - "Rationale"
  - "Related studies"
  - "Discussion"
  - "Getting social proof right"
  - "Keeping a balance: social proof boosters and killers"
example_count: 13
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Social Proof

> Catalog pointer for the UI Patterns source page: [Social Proof](https://ui-patterns.com/patterns/Social-proof).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Social
- Subgroup: Social biases
- Source breadcrumb: Design Patterns > Social > Social biases > Social Proof

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Social-proof
- Page title: Social Proof design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, 6 ways to use Social Proof, Appeal to logic, emotions, and to ethical character, Rationale, Related studies, Discussion, Getting social proof right, Keeping a balance: social proof boosters and killers
- Example screenshots detected at source: 13
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 11 words on source page
- Example: 53 words on source page
- Usage: 52 words on source page
- Solution: 553 words on source page
- 6 ways to use Social Proof: 123 words on source page
- Appeal to logic, emotions, and to ethical character: 350 words on source page
- Rationale: 315 words on source page
- Related studies: 86 words on source page
- Discussion: 469 words on source page
- Getting social proof right: 199 words on source page
- Keeping a balance: social proof boosters and killers: 133 words on source page

## Source Navigation

- Previous source navigation: Peak-end rule
- Next source navigation: Kairos


<!-- ===== ui-patterns/wiki/concepts/patterns/sort-by-column.md ===== -->

---
title: "Sort By Column"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/SortByColumn"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/SortByColumn"
source_slug: "SortByColumn"
track: "User Interface Design Patterns"
group: "Dealing with data"
subgroup: "Tables"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 2
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Sort By Column

> Catalog pointer for the UI Patterns source page: [Sort By Column](https://ui-patterns.com/patterns/SortByColumn).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Dealing with data
- Subgroup: Tables
- Source breadcrumb: Design Patterns > Dealing with data > Tables > Sort By Column

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/SortByColumn
- Page title: Sort By Column design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 2
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 20 words on source page
- Example: 72 words on source page
- Usage: 71 words on source page
- Solution: 112 words on source page
- Rationale: 39 words on source page

## Source Navigation

- Previous source navigation: Inplace Editor
- Next source navigation: Alternating Row Colors


<!-- ===== ui-patterns/wiki/concepts/patterns/status-quo-bias.md ===== -->

---
title: "Status-Quo Bias"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Statusquo-bias"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Statusquo-bias"
source_slug: "Statusquo-bias"
track: "Persuasive Design Patterns"
group: "Cognition"
subgroup: "Loss Aversion"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Apply the status-quo bias"
  - "Rationale"
  - "Discussion"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Status-Quo Bias

> Catalog pointer for the UI Patterns source page: [Status-Quo Bias](https://ui-patterns.com/patterns/Statusquo-bias).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Cognition
- Subgroup: Loss Aversion
- Source breadcrumb: Design Patterns > Cognition > Loss Aversion > Status-Quo Bias

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Statusquo-bias
- Page title: Status-Quo Bias design pattern
- Section headings available at source: Problem summary, Usage, Solution, Apply the status-quo bias, Rationale, Discussion
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 50 words on source page
- Usage: 32 words on source page
- Solution: 388 words on source page
- Apply the status-quo bias: 150 words on source page
- Rationale: 159 words on source page
- Discussion: 308 words on source page

## Source Navigation

- Previous source navigation: Storytelling
- Next source navigation: Peak-end rule


<!-- ===== ui-patterns/wiki/concepts/patterns/status.md ===== -->

---
title: "Status"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Status"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Status"
source_slug: "Status"
track: "Persuasive Design Patterns"
group: "Social"
subgroup: "Social biases"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Status

> Catalog pointer for the UI Patterns source page: [Status](https://ui-patterns.com/patterns/Status).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Social
- Subgroup: Social biases
- Source breadcrumb: Design Patterns > Social > Social biases > Status

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Status
- Page title: Status design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 32 words on source page
- Usage: 17 words on source page
- Solution: 194 words on source page
- Rationale: 118 words on source page

## Source Navigation

- Previous source navigation: Goal-Gradient Effect
- Next source navigation: Tailoring


<!-- ===== ui-patterns/wiki/concepts/patterns/steps-left.md ===== -->

---
title: "Steps Left"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/StepsLeft"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/StepsLeft"
source_slug: "StepsLeft"
track: "User Interface Design Patterns"
group: "Getting input"
subgroup: "Explaining the process"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 13
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Steps Left

> Catalog pointer for the UI Patterns source page: [Steps Left](https://ui-patterns.com/patterns/StepsLeft).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Getting input
- Subgroup: Explaining the process
- Source breadcrumb: Design Patterns > Getting input > Explaining the process > Steps Left

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/StepsLeft
- Page title: Steps Left design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 13
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 22 words on source page
- Example: 96 words on source page
- Usage: 79 words on source page
- Solution: 70 words on source page
- Rationale: 137 words on source page

## Source Navigation

- Previous source navigation: Shopping Cart
- Next source navigation: Continuous Scrolling


<!-- ===== ui-patterns/wiki/concepts/patterns/storytelling.md ===== -->

---
title: "Storytelling"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Storytelling"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Storytelling"
source_slug: "Storytelling"
track: "Persuasive Design Patterns"
group: "Game mechanics"
subgroup: "Gameplay design"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
  - "Discussion"
  - "Aristotle’s Poetics"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Storytelling

> Catalog pointer for the UI Patterns source page: [Storytelling](https://ui-patterns.com/patterns/Storytelling).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Game mechanics
- Subgroup: Gameplay design
- Source breadcrumb: Design Patterns > Game mechanics > Gameplay design > Storytelling

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Storytelling
- Page title: Storytelling design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale, Discussion, Aristotle’s Poetics
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 15 words on source page
- Solution: 156 words on source page
- Rationale: 70 words on source page
- Discussion: 718 words on source page
- Aristotle’s Poetics: 575 words on source page

## Source Navigation

- Previous source navigation: Event Calendar
- Next source navigation: Loss Aversion


<!-- ===== ui-patterns/wiki/concepts/patterns/structured-format.md ===== -->

---
title: "Structured Format"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/StructuredFormat"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/StructuredFormat"
source_slug: "StructuredFormat"
track: "User Interface Design Patterns"
group: "Getting input"
subgroup: "Forms"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 2
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Structured Format

> Catalog pointer for the UI Patterns source page: [Structured Format](https://ui-patterns.com/patterns/StructuredFormat).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Getting input
- Subgroup: Forms
- Source breadcrumb: Design Patterns > Getting input > Forms > Structured Format

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/StructuredFormat
- Page title: Structured Format design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 2
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 22 words on source page
- Example: 112 words on source page
- Usage: 111 words on source page
- Solution: 110 words on source page
- Rationale: 136 words on source page

## Source Navigation

- Previous source navigation: Forgiving Format
- Next source navigation: Fill in the Blanks


<!-- ===== ui-patterns/wiki/concepts/patterns/sunk-cost-effect.md ===== -->

---
title: "Sunk Cost Effect"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/sunk-cost-effect"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/sunk-cost-effect"
source_slug: "sunk-cost-effect"
track: "Persuasive Design Patterns"
group: "Cognition"
subgroup: "Loss Aversion"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Sunk Cost Effect

> Catalog pointer for the UI Patterns source page: [Sunk Cost Effect](https://ui-patterns.com/patterns/sunk-cost-effect).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Cognition
- Subgroup: Loss Aversion
- Source breadcrumb: Design Patterns > Cognition > Loss Aversion > Sunk Cost Effect

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/sunk-cost-effect
- Page title: Sunk Cost Effect design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 45 words on source page
- Usage: 31 words on source page
- Solution: 123 words on source page
- Rationale: 275 words on source page

## Source Navigation

- Previous source navigation: Halo Effect
- Next source navigation: Autonomy


<!-- ===== ui-patterns/wiki/concepts/patterns/table-filter.md ===== -->

---
title: "Table Filter"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/TableFilter"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/TableFilter"
source_slug: "TableFilter"
track: "User Interface Design Patterns"
group: "Dealing with data"
subgroup: "Tables"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 6
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Table Filter

> Catalog pointer for the UI Patterns source page: [Table Filter](https://ui-patterns.com/patterns/TableFilter).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Dealing with data
- Subgroup: Tables
- Source breadcrumb: Design Patterns > Dealing with data > Tables > Table Filter

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/TableFilter
- Page title: Table Filter design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 6
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 14 words on source page
- Example: 37 words on source page
- Usage: 36 words on source page
- Solution: 89 words on source page
- Rationale: 37 words on source page

## Source Navigation

- Previous source navigation: Sort By Column
- Next source navigation: Copy Box


<!-- ===== ui-patterns/wiki/concepts/patterns/tag-cloud.md ===== -->

---
title: "Tag Cloud"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/TagCloud"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/TagCloud"
source_slug: "TagCloud"
track: "User Interface Design Patterns"
group: "Navigation"
subgroup: "Content"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 13
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Tag Cloud

> Catalog pointer for the UI Patterns source page: [Tag Cloud](https://ui-patterns.com/patterns/TagCloud).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Navigation
- Subgroup: Content
- Source breadcrumb: Design Patterns > Navigation > Content > Tag Cloud

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/TagCloud
- Page title: Tag Cloud design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 13
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 13 words on source page
- Example: 43 words on source page
- Usage: 42 words on source page
- Solution: 141 words on source page
- Rationale: 57 words on source page

## Source Navigation

- Previous source navigation: Preview
- Next source navigation: Inline Help Box


<!-- ===== ui-patterns/wiki/concepts/patterns/tagging.md ===== -->

---
title: "Tagging"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Tag"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Tag"
source_slug: "Tag"
track: "User Interface Design Patterns"
group: "Navigation"
subgroup: "Content"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 13
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Tagging

> Catalog pointer for the UI Patterns source page: [Tagging](https://ui-patterns.com/patterns/Tag).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Navigation
- Subgroup: Content
- Source breadcrumb: Design Patterns > Navigation > Content > Tagging

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Tag
- Page title: Tagging design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 13
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 13 words on source page
- Example: 78 words on source page
- Usage: 42 words on source page
- Solution: 100 words on source page
- Rationale: 112 words on source page

## Source Navigation

- Previous source navigation: Preview
- Next source navigation: Inline Help Box


<!-- ===== ui-patterns/wiki/concepts/patterns/tailoring.md ===== -->

---
title: "Tailoring"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Tailoring"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Tailoring"
source_slug: "Tailoring"
track: "Persuasive Design Patterns"
group: "Feedback"
subgroup: "Timing"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
  - "Discussion"
  - "Cultural differences"
  - "Harmony strategy"
  - "Group Opinion strategy"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Tailoring

> Catalog pointer for the UI Patterns source page: [Tailoring](https://ui-patterns.com/patterns/Tailoring).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Feedback
- Subgroup: Timing
- Source breadcrumb: Design Patterns > Feedback > Timing > Tailoring

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Tailoring
- Page title: Tailoring design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale, Discussion, Cultural differences, Harmony strategy, Group Opinion strategy
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 14 words on source page
- Solution: 123 words on source page
- Rationale: 61 words on source page
- Discussion: 154 words on source page
- Cultural differences: 10 words on source page
- Harmony strategy: 17 words on source page
- Group Opinion strategy: 18 words on source page

## Source Navigation

- Previous source navigation: Limited Choice
- Next source navigation: Anchoring


<!-- ===== ui-patterns/wiki/concepts/patterns/temptation-bundling.md ===== -->

---
title: "Temptation Bundling"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/temptation-bundling"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/temptation-bundling"
source_slug: "temptation-bundling"
track: "Persuasive Design Patterns"
group: "Cognition"
subgroup: "Other cognitive biases"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Temptation Bundling

> Catalog pointer for the UI Patterns source page: [Temptation Bundling](https://ui-patterns.com/patterns/temptation-bundling).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Cognition
- Subgroup: Other cognitive biases
- Source breadcrumb: Design Patterns > Cognition > Other cognitive biases > Temptation Bundling

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/temptation-bundling
- Page title: Temptation Bundling design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 34 words on source page
- Usage: 21 words on source page
- Solution: 146 words on source page
- Rationale: 187 words on source page

## Source Navigation

- Previous source navigation: Zeigarnik Effect
- Next source navigation: Picture Superiority Effect


<!-- ===== ui-patterns/wiki/concepts/patterns/testimonials.md ===== -->

---
title: "Testimonials"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/testimonials"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/testimonials"
source_slug: "testimonials"
track: "User Interface Design Patterns"
group: "Social"
subgroup: "Reputation"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 13
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Testimonials

> Catalog pointer for the UI Patterns source page: [Testimonials](https://ui-patterns.com/patterns/testimonials).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Social
- Subgroup: Reputation
- Source breadcrumb: Design Patterns > Social > Reputation > Testimonials

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/testimonials
- Page title: Testimonials design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 13
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Example: 9 words on source page
- Solution: 12 words on source page
- Rationale: 44 words on source page

## Source Navigation

- Previous source navigation: Paywall
- Next source navigation: Auto-sharing


<!-- ===== ui-patterns/wiki/concepts/patterns/thumbnail.md ===== -->

---
title: "Thumbnail"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Thumbnail"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Thumbnail"
source_slug: "Thumbnail"
track: "User Interface Design Patterns"
group: "Navigation"
subgroup: "Content"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 13
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Thumbnail

> Catalog pointer for the UI Patterns source page: [Thumbnail](https://ui-patterns.com/patterns/Thumbnail).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Navigation
- Subgroup: Content
- Source breadcrumb: Design Patterns > Navigation > Content > Thumbnail

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Thumbnail
- Page title: Thumbnail design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 13
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 20 words on source page
- Example: 94 words on source page
- Usage: 93 words on source page
- Solution: 105 words on source page
- Rationale: 66 words on source page

## Source Navigation

- Previous source navigation: Table Filter
- Next source navigation: Coupon


<!-- ===== ui-patterns/wiki/concepts/patterns/tip-a-friend.md ===== -->

---
title: "Tip A Friend"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/TipAFriend"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/TipAFriend"
source_slug: "TipAFriend"
track: "User Interface Design Patterns"
group: "Miscellaneous"
subgroup: "Increasing frequency"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 4
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Tip A Friend

> Catalog pointer for the UI Patterns source page: [Tip A Friend](https://ui-patterns.com/patterns/TipAFriend).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Miscellaneous
- Subgroup: Increasing frequency
- Source breadcrumb: Design Patterns > Miscellaneous > Increasing frequency > Tip A Friend

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/TipAFriend
- Page title: Tip A Friend design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 4
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 11 words on source page
- Example: 48 words on source page
- Usage: 47 words on source page
- Solution: 73 words on source page
- Rationale: 112 words on source page

## Source Navigation

- Previous source navigation: Shopping Cart
- Next source navigation: Continuous Scrolling


<!-- ===== ui-patterns/wiki/concepts/patterns/trigger.md ===== -->

---
title: "Trigger"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Trigger"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Trigger"
source_slug: "Trigger"
track: "Persuasive Design Patterns"
group: "Feedback"
subgroup: "Timing"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Trigger

> Catalog pointer for the UI Patterns source page: [Trigger](https://ui-patterns.com/patterns/Trigger).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Feedback
- Subgroup: Timing
- Source breadcrumb: Design Patterns > Feedback > Timing > Trigger

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Trigger
- Page title: Trigger design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 24 words on source page
- Usage: 9 words on source page
- Solution: 154 words on source page
- Rationale: 255 words on source page

## Source Navigation

- Previous source navigation: Goal-Gradient Effect
- Next source navigation: Tailoring


<!-- ===== ui-patterns/wiki/concepts/patterns/tunnelling.md ===== -->

---
title: "Tunnelling"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Tunnelling"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Tunnelling"
source_slug: "Tunnelling"
track: "Persuasive Design Patterns"
group: "Perception and memory"
subgroup: "Attention"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 3
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Tunnelling

> Catalog pointer for the UI Patterns source page: [Tunnelling](https://ui-patterns.com/patterns/Tunnelling).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Perception and memory
- Subgroup: Attention
- Source breadcrumb: Design Patterns > Perception and memory > Attention > Tunnelling

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Tunnelling
- Page title: Tunnelling design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 3
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 14 words on source page
- Example: 126 words on source page
- Usage: 73 words on source page
- Solution: 239 words on source page
- Rationale: 167 words on source page

## Source Navigation

- Previous source navigation: Limited Choice
- Next source navigation: Anchoring


<!-- ===== ui-patterns/wiki/concepts/patterns/undo.md ===== -->

---
title: "Undo"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/undo"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/undo"
source_slug: "undo"
track: "User Interface Design Patterns"
group: "Getting input"
subgroup: "Forms"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
  - "Discussion"
example_count: 1
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Undo

> Catalog pointer for the UI Patterns source page: [Undo](https://ui-patterns.com/patterns/undo).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Getting input
- Subgroup: Forms
- Source breadcrumb: Design Patterns > Getting input > Forms > Undo

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/undo
- Page title: Undo design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale, Discussion
- Example screenshots detected at source: 1
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 8 words on source page
- Example: 80 words on source page
- Usage: 53 words on source page
- Solution: 8 words on source page
- Rationale: 55 words on source page
- Discussion: 94 words on source page

## Source Navigation

- Previous source navigation: Chat
- Next source navigation: Modal


<!-- ===== ui-patterns/wiki/concepts/patterns/unlock-features.md ===== -->

---
title: "Unlock Features"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Unlock-features"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Unlock-features"
source_slug: "Unlock-features"
track: "Persuasive Design Patterns"
group: "Game mechanics"
subgroup: "Gameplay rewards"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Example: Karma points at Hacker News"
  - "Other ways of quantifying the criteria for unlocking features"
  - "Rationale"
  - "Discussion"
  - "Gaming the system"
  - "Drowning out new users"
  - "Acclimation to rewards"
  - "The end of the road"
example_count: 3
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Unlock Features

> Catalog pointer for the UI Patterns source page: [Unlock Features](https://ui-patterns.com/patterns/Unlock-features).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Game mechanics
- Subgroup: Gameplay rewards
- Source breadcrumb: Design Patterns > Game mechanics > Gameplay rewards > Unlock Features

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Unlock-features
- Page title: Unlock Features design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Example: Karma points at Hacker News, Other ways of quantifying the criteria for unlocking features, Rationale, Discussion, Gaming the system, Drowning out new users, Acclimation to rewards, The end of the road
- Example screenshots detected at source: 3
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 17 words on source page
- Example: 82 words on source page
- Usage: 55 words on source page
- Solution: 538 words on source page
- Example: Karma points at Hacker News: 131 words on source page
- Other ways of quantifying the criteria for unlocking features: 95 words on source page
- Rationale: 197 words on source page
- Discussion: 591 words on source page
- Gaming the system: 94 words on source page
- Drowning out new users: 69 words on source page
- Acclimation to rewards: 114 words on source page
- The end of the road: 120 words on source page

## Source Navigation

- Previous source navigation: Value Attribution
- Next source navigation: Trigger


<!-- ===== ui-patterns/wiki/concepts/patterns/value-attribution.md ===== -->

---
title: "Value Attribution"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Value-attribution"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Value-attribution"
source_slug: "Value-attribution"
track: "Persuasive Design Patterns"
group: "Cognition"
subgroup: "Other cognitive biases"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
  - "Discussion"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Value Attribution

> Catalog pointer for the UI Patterns source page: [Value Attribution](https://ui-patterns.com/patterns/Value-attribution).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Cognition
- Subgroup: Other cognitive biases
- Source breadcrumb: Design Patterns > Cognition > Other cognitive biases > Value Attribution

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Value-attribution
- Page title: Value Attribution design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale, Discussion
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 28 words on source page
- Usage: 16 words on source page
- Solution: 145 words on source page
- Rationale: 67 words on source page
- Discussion: 313 words on source page

## Source Navigation

- Previous source navigation: Variable Rewards
- Next source navigation: Self-Expression


<!-- ===== ui-patterns/wiki/concepts/patterns/variable-rewards.md ===== -->

---
title: "Variable Rewards"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Variable-rewards"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Variable-rewards"
source_slug: "Variable-rewards"
track: "Persuasive Design Patterns"
group: "Game mechanics"
subgroup: "Fundamentals of rewards"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Example: Lomography.com"
  - "Rationale"
  - "Fixed vs variable ratios"
  - "Fixed vs variable intervals"
  - "Discussion"
  - "Extinction"
  - "Avoidance"
example_count: 2
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Variable Rewards

> Catalog pointer for the UI Patterns source page: [Variable Rewards](https://ui-patterns.com/patterns/Variable-rewards).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Game mechanics
- Subgroup: Fundamentals of rewards
- Source breadcrumb: Design Patterns > Game mechanics > Fundamentals of rewards > Variable Rewards

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Variable-rewards
- Page title: Variable Rewards design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Example: Lomography.com, Rationale, Fixed vs variable ratios, Fixed vs variable intervals, Discussion, Extinction, Avoidance
- Example screenshots detected at source: 2
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 19 words on source page
- Example: 66 words on source page
- Usage: 25 words on source page
- Solution: 412 words on source page
- Example: Lomography.com: 155 words on source page
- Rationale: 566 words on source page
- Fixed vs variable ratios: 277 words on source page
- Fixed vs variable intervals: 184 words on source page
- Discussion: 296 words on source page
- Extinction: 61 words on source page
- Avoidance: 46 words on source page

## Source Navigation

- Previous source navigation: Reciprocation
- Next source navigation: Limited duration


<!-- ===== ui-patterns/wiki/concepts/patterns/vertical-dropdown-menu.md ===== -->

---
title: "Vertical Dropdown Menu"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/VerticalDropdownMenu"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/VerticalDropdownMenu"
source_slug: "VerticalDropdownMenu"
track: "User Interface Design Patterns"
group: "Navigation"
subgroup: "Menus"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Other issues you want to take notice of:"
  - "Rationale"
example_count: 13
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Vertical Dropdown Menu

> Catalog pointer for the UI Patterns source page: [Vertical Dropdown Menu](https://ui-patterns.com/patterns/VerticalDropdownMenu).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Navigation
- Subgroup: Menus
- Source breadcrumb: Design Patterns > Navigation > Menus > Vertical Dropdown Menu

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/VerticalDropdownMenu
- Page title: Vertical Dropdown Menu design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Other issues you want to take notice of:, Rationale
- Example screenshots detected at source: 13
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 18 words on source page
- Example: 55 words on source page
- Usage: 54 words on source page
- Solution: 285 words on source page
- Other issues you want to take notice of:: 1 words on source page
- Rationale: 70 words on source page

## Source Navigation

- Previous source navigation: Home Link
- Next source navigation: Accordion Menu


<!-- ===== ui-patterns/wiki/concepts/patterns/vote-to-promote.md ===== -->

---
title: "Vote To Promote"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/VoteToPromote"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/VoteToPromote"
source_slug: "VoteToPromote"
track: "User Interface Design Patterns"
group: "Getting input"
subgroup: "Community driven"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "4 Mechanisms working together"
  - "Let users submit"
  - "Make voting embeddable"
  - "Rationale"
  - "Discussion"
  - "Wisdom of crowds"
example_count: 13
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Vote To Promote

> Catalog pointer for the UI Patterns source page: [Vote To Promote](https://ui-patterns.com/patterns/VoteToPromote).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Getting input
- Subgroup: Community driven
- Source breadcrumb: Design Patterns > Getting input > Community driven > Vote To Promote

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/VoteToPromote
- Page title: Vote To Promote design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, 4 Mechanisms working together, Let users submit, Make voting embeddable, Rationale, Discussion, Wisdom of crowds
- Example screenshots detected at source: 13
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 21 words on source page
- Example: 113 words on source page
- Usage: 72 words on source page
- Solution: 354 words on source page
- 4 Mechanisms working together: 156 words on source page
- Let users submit: 45 words on source page
- Make voting embeddable: 78 words on source page
- Rationale: 41 words on source page
- Discussion: 452 words on source page
- Wisdom of crowds: 138 words on source page

## Source Navigation

- Previous source navigation: Lazy Registration
- Next source navigation: Account Registration


<!-- ===== ui-patterns/wiki/concepts/patterns/walkthrough.md ===== -->

---
title: "Walkthrough"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Tour"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Tour"
source_slug: "Tour"
track: "User Interface Design Patterns"
group: "Onboarding"
subgroup: "Guidance"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Focus on users’ tasks"
  - "Provide visual references"
  - "Include direct links"
  - "Address issues or concerns up front"
  - "Rationale"
example_count: 13
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Walkthrough

> Catalog pointer for the UI Patterns source page: [Walkthrough](https://ui-patterns.com/patterns/Tour).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Onboarding
- Subgroup: Guidance
- Source breadcrumb: Design Patterns > Onboarding > Guidance > Walkthrough

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Tour
- Page title: Walkthrough design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Focus on users’ tasks, Provide visual references, Include direct links, Address issues or concerns up front, Rationale
- Example screenshots detected at source: 13
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 25 words on source page
- Example: 96 words on source page
- Usage: 76 words on source page
- Solution: 425 words on source page
- Focus on users’ tasks: 123 words on source page
- Provide visual references: 57 words on source page
- Include direct links: 52 words on source page
- Address issues or concerns up front: 60 words on source page
- Rationale: 119 words on source page

## Source Navigation

- Previous source navigation: Liking
- Next source navigation: Gallery


<!-- ===== ui-patterns/wiki/concepts/patterns/wiki.md ===== -->

---
title: "Wiki"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Wiki"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Wiki"
source_slug: "Wiki"
track: "User Interface Design Patterns"
group: "Getting input"
subgroup: "Community driven"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 4
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Wiki

> Catalog pointer for the UI Patterns source page: [Wiki](https://ui-patterns.com/patterns/Wiki).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Getting input
- Subgroup: Community driven
- Source breadcrumb: Design Patterns > Getting input > Community driven > Wiki

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Wiki
- Page title: Wiki design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 4
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 23 words on source page
- Example: 97 words on source page
- Usage: 96 words on source page
- Solution: 147 words on source page
- Rationale: 42 words on source page

## Source Navigation

- Previous source navigation: Search Filters
- Next source navigation: WYSIWYG


<!-- ===== ui-patterns/wiki/concepts/patterns/wizard.md ===== -->

---
title: "Wizard"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/Wizard"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/Wizard"
source_slug: "Wizard"
track: "User Interface Design Patterns"
group: "Getting input"
subgroup: "Explaining the process"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Buttons"
  - "Keep the purpose clear: explain"
  - "Use plain language"
  - "Summarize choices"
  - "Good defaults"
  - "Rationale"
  - "Minimum of training"
  - "Discussion"
  - "Keep the amount of screens low"
  - "Be careful not to make each step too long"
  - "Allow alternatives to using the wizard"
  - "Sources"
example_count: 13
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Wizard

> Catalog pointer for the UI Patterns source page: [Wizard](https://ui-patterns.com/patterns/Wizard).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Getting input
- Subgroup: Explaining the process
- Source breadcrumb: Design Patterns > Getting input > Explaining the process > Wizard

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/Wizard
- Page title: Wizard design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Buttons, Keep the purpose clear: explain, Use plain language, Summarize choices, Good defaults, Rationale, Minimum of training, Discussion, Keep the amount of screens low, Be careful not to make each step too long, Allow alternatives to using the wizard, Sources
- Example screenshots detected at source: 13
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 17 words on source page
- Example: 243 words on source page
- Usage: 161 words on source page
- Solution: 614 words on source page
- Buttons: 221 words on source page
- Keep the purpose clear: explain: 59 words on source page
- Use plain language: 33 words on source page
- Summarize choices: 100 words on source page
- Good defaults: 37 words on source page
- Rationale: 256 words on source page
- Minimum of training: 40 words on source page
- Discussion: 498 words on source page
- Keep the amount of screens low: 39 words on source page
- Be careful not to make each step too long: 128 words on source page
- Allow alternatives to using the wizard: 152 words on source page
- Sources: 50 words on source page

## Source Navigation

- Previous source navigation: Adaptable View
- Next source navigation: Completeness meter


<!-- ===== ui-patterns/wiki/concepts/patterns/wysiwyg.md ===== -->

---
title: "WYSIWYG"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/WYSIWYG"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/WYSIWYG"
source_slug: "WYSIWYG"
track: "User Interface Design Patterns"
group: "Getting input"
subgroup: "Forms"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 1
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# WYSIWYG

> Catalog pointer for the UI Patterns source page: [WYSIWYG](https://ui-patterns.com/patterns/WYSIWYG).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Getting input
- Subgroup: Forms
- Source breadcrumb: Design Patterns > Getting input > Forms > WYSIWYG

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/WYSIWYG
- Page title: WYSIWYG design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Rationale
- Example screenshots detected at source: 1
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 23 words on source page
- Example: 203 words on source page
- Usage: 202 words on source page
- Solution: 86 words on source page
- Rationale: 89 words on source page

## Source Navigation

- Previous source navigation: Wiki
- Next source navigation: Tagging


<!-- ===== ui-patterns/wiki/concepts/patterns/zeigarnik-effect.md ===== -->

---
title: "Zeigarnik Effect"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/zeigarnik-effect"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/zeigarnik-effect"
source_slug: "zeigarnik-effect"
track: "Persuasive Design Patterns"
group: "Perception and memory"
subgroup: "Attention"
section_headings:
  - "Problem summary"
  - "Usage"
  - "Solution"
  - "Rationale"
example_count: 0
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Zeigarnik Effect

> Catalog pointer for the UI Patterns source page: [Zeigarnik Effect](https://ui-patterns.com/patterns/zeigarnik-effect).

## Taxonomy

- Track: Persuasive Design Patterns
- Group: Perception and memory
- Subgroup: Attention
- Source breadcrumb: Design Patterns > Perception and memory > Attention > Zeigarnik Effect

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/zeigarnik-effect
- Page title: Zeigarnik Effect design pattern
- Section headings available at source: Problem summary, Usage, Solution, Rationale
- Example screenshots detected at source: 0
- Primary example image detected: no

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 63 words on source page
- Usage: 52 words on source page
- Solution: 98 words on source page
- Rationale: 147 words on source page

## Source Navigation

- Previous source navigation: Fresh Start Effect
- Next source navigation: Inaction Inertia Effect


<!-- ===== ui-patterns/wiki/entities/categories/persuasive-design-patterns-cognition.md ===== -->

---
title: "Cognition — Persuasive Design Patterns"
created: "2026-07-02"
updated: "2026-07-02"
type: "entity"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns"
source_site: "UI Patterns"
track: "Persuasive Design Patterns"
group: "Cognition"
pattern_count: 25
confidence: "medium"
---
# Cognition — Persuasive Design Patterns

> Category map imported from [UI Patterns](https://ui-patterns.com/patterns).

## Scope

This category groups 25 cataloged source pages under `Cognition` / `Persuasive Design Patterns`. It is a navigation layer, not a copy of the source site.

## Patterns

### Loss Aversion

- [[decoy-effect|Decoy Effect]] — [source](https://ui-patterns.com/patterns/decoy-effect)
- [[endowment-effect|Endowment Effect]] — [source](https://ui-patterns.com/patterns/Endowment-effect)
- [[framing|Framing]] — [source](https://ui-patterns.com/patterns/framing)
- [[ikea-effect|IKEA effect]] — [source](https://ui-patterns.com/patterns/ikea-effect)
- [[loss-aversion|Loss Aversion]] — [source](https://ui-patterns.com/patterns/Loss-aversion)
- [[negativity-bias|Negativity bias]] — [source](https://ui-patterns.com/patterns/Negativity-bias)
- [[optimism-bias|Optimism Bias]] — [source](https://ui-patterns.com/patterns/optimism-bias)
- [[status-quo-bias|Status-Quo Bias]] — [source](https://ui-patterns.com/patterns/Statusquo-bias)
- [[sunk-cost-effect|Sunk Cost Effect]] — [source](https://ui-patterns.com/patterns/sunk-cost-effect)
### Other cognitive biases

- [[cashless-effect|Cashless Effect]] — [source](https://ui-patterns.com/patterns/cashless-effect)
- [[choice-closure|Choice Closure]] — [source](https://ui-patterns.com/patterns/choice-closure)
- [[curiosity|Curiosity]] — [source](https://ui-patterns.com/patterns/curiosity)
- [[delay-discounting|Delay Discounting]] — [source](https://ui-patterns.com/patterns/delay-discounting)
- [[illusion-of-control|Illusion of control]] — [source](https://ui-patterns.com/patterns/Illusion-of-control)
- [[inaction-inertia-effect|Inaction Inertia Effect]] — [source](https://ui-patterns.com/patterns/inaction-inertia-effect)
- [[need-for-closure|Need for Closure]] — [source](https://ui-patterns.com/patterns/Need-for-closure)
- [[peak-end-rule|Peak-end rule]] — [source](https://ui-patterns.com/patterns/Peakend-rule)
- [[present-bias|Present Bias]] — [source](https://ui-patterns.com/patterns/present-bias)
- [[priming-effect|Priming Effect]] — [source](https://ui-patterns.com/patterns/priming-effect)
- [[set-completion|Set Completion]] — [source](https://ui-patterns.com/patterns/set-completion)
- [[temptation-bundling|Temptation Bundling]] — [source](https://ui-patterns.com/patterns/temptation-bundling)
- [[value-attribution|Value Attribution]] — [source](https://ui-patterns.com/patterns/Value-attribution)
### Scarcity

- [[limited-choice|Limited Choice]] — [source](https://ui-patterns.com/patterns/Limited-choice)
- [[limited-duration|Limited duration]] — [source](https://ui-patterns.com/patterns/Limited-duration)
- [[scarcity|Scarcity]] — [source](https://ui-patterns.com/patterns/Scarcity)


<!-- ===== ui-patterns/wiki/entities/categories/persuasive-design-patterns-feedback.md ===== -->

---
title: "Feedback — Persuasive Design Patterns"
created: "2026-07-02"
updated: "2026-07-02"
type: "entity"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns"
source_site: "UI Patterns"
track: "Persuasive Design Patterns"
group: "Feedback"
pattern_count: 6
confidence: "medium"
---
# Feedback — Persuasive Design Patterns

> Category map imported from [UI Patterns](https://ui-patterns.com/patterns).

## Scope

This category groups 6 cataloged source pages under `Feedback` / `Persuasive Design Patterns`. It is a navigation layer, not a copy of the source site.

## Patterns

### Timing

- [[feedback-loops|Feedback Loops]] — [source](https://ui-patterns.com/patterns/Feedback-loops)
- [[fresh-start-effect|Fresh Start Effect]] — [source](https://ui-patterns.com/patterns/fresh-start-effect)
- [[kairos|Kairos]] — [source](https://ui-patterns.com/patterns/Kairos)
- [[simulation|Simulation]] — [source](https://ui-patterns.com/patterns/Simulation)
- [[tailoring|Tailoring]] — [source](https://ui-patterns.com/patterns/Tailoring)
- [[trigger|Trigger]] — [source](https://ui-patterns.com/patterns/Trigger)


<!-- ===== ui-patterns/wiki/entities/categories/persuasive-design-patterns-game-mechanics.md ===== -->

---
title: "Game mechanics — Persuasive Design Patterns"
created: "2026-07-02"
updated: "2026-07-02"
type: "entity"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns"
source_site: "UI Patterns"
track: "Persuasive Design Patterns"
group: "Game mechanics"
pattern_count: 19
confidence: "medium"
---
# Game mechanics — Persuasive Design Patterns

> Category map imported from [UI Patterns](https://ui-patterns.com/patterns).

## Scope

This category groups 19 cataloged source pages under `Game mechanics` / `Persuasive Design Patterns`. It is a navigation layer, not a copy of the source site.

## Patterns

### Fundamentals of rewards

- [[fixed-rewards|Fixed rewards]] — [source](https://ui-patterns.com/patterns/Fixed-rewards)
- [[shaping|Shaping]] — [source](https://ui-patterns.com/patterns/shaping)
- [[variable-rewards|Variable Rewards]] — [source](https://ui-patterns.com/patterns/Variable-rewards)
### Gameplay design

- [[appropriate-challenge|Appropriate Challenge]] — [source](https://ui-patterns.com/patterns/Appropriate-challenge)
- [[hedonic-adaptation|Hedonic Adaptation]] — [source](https://ui-patterns.com/patterns/hedonic-adaptation)
- [[intentional-gaps|Intentional Gaps]] — [source](https://ui-patterns.com/patterns/Intentional-gaps)
- [[investment-loops|Investment Loops]] — [source](https://ui-patterns.com/patterns/investment-loops)
- [[levels|Levels]] — [source](https://ui-patterns.com/patterns/Levels)
- [[periodic-events|Periodic Events]] — [source](https://ui-patterns.com/patterns/periodic-events)
- [[self-monitoring|Self-Monitoring]] — [source](https://ui-patterns.com/patterns/self-monitoring)
- [[storytelling|Storytelling]] — [source](https://ui-patterns.com/patterns/Storytelling)
### Gameplay rewards

- [[achievements|Achievements]] — [source](https://ui-patterns.com/patterns/Achievements)
- [[appointment-dynamic|Appointment Dynamic]] — [source](https://ui-patterns.com/patterns/appointment-dynamic)
- [[delighters|Delighters]] — [source](https://ui-patterns.com/patterns/delighters)
- [[goal-gradient-effect|Goal-Gradient Effect]] — [source](https://ui-patterns.com/patterns/Completion)
- [[praise|Praise]] — [source](https://ui-patterns.com/patterns/Praise)
- [[privileges|Privileges]] — [source](https://ui-patterns.com/patterns/Powers)
- [[prolonged-play|Prolonged Play]] — [source](https://ui-patterns.com/patterns/Prolonged-play)
- [[unlock-features|Unlock Features]] — [source](https://ui-patterns.com/patterns/Unlock-features)


<!-- ===== ui-patterns/wiki/entities/categories/persuasive-design-patterns-perception-and-memory.md ===== -->

---
title: "Perception and memory — Persuasive Design Patterns"
created: "2026-07-02"
updated: "2026-07-02"
type: "entity"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns"
source_site: "UI Patterns"
track: "Persuasive Design Patterns"
group: "Perception and memory"
pattern_count: 12
confidence: "medium"
---
# Perception and memory — Persuasive Design Patterns

> Category map imported from [UI Patterns](https://ui-patterns.com/patterns).

## Scope

This category groups 12 cataloged source pages under `Perception and memory` / `Persuasive Design Patterns`. It is a navigation layer, not a copy of the source site.

## Patterns

### Attention

- [[isolation-effect|Isolation Effect]] — [source](https://ui-patterns.com/patterns/isolation-effect)
- [[picture-superiority-effect|Picture Superiority Effect]] — [source](https://ui-patterns.com/patterns/picture-superiority-effect)
- [[reduction|Reduction]] — [source](https://ui-patterns.com/patterns/Reduction)
- [[tunnelling|Tunnelling]] — [source](https://ui-patterns.com/patterns/Tunnelling)
- [[zeigarnik-effect|Zeigarnik Effect]] — [source](https://ui-patterns.com/patterns/zeigarnik-effect)
### Comprehension

- [[anchoring|Anchoring]] — [source](https://ui-patterns.com/patterns/Anchoring)
- [[chunking|Chunking]] — [source](https://ui-patterns.com/patterns/Chunking)
- [[conceptual-metaphor|Conceptual Metaphor]] — [source](https://ui-patterns.com/patterns/Conceptual-metaphor)
- [[pattern-recognition|Pattern Recognition]] — [source](https://ui-patterns.com/patterns/Pattern-recognition)
- [[recognition-over-recall|Recognition over Recall]] — [source](https://ui-patterns.com/patterns/Recognition-over-recall)
- [[sequencing|Sequencing]] — [source](https://ui-patterns.com/patterns/Sequencing)
- [[serial-positioning-effect|Serial Positioning Effect]] — [source](https://ui-patterns.com/patterns/Serial-positioning-effect)


<!-- ===== ui-patterns/wiki/entities/categories/persuasive-design-patterns-social.md ===== -->

---
title: "Social — Persuasive Design Patterns"
created: "2026-07-02"
updated: "2026-07-02"
type: "entity"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns"
source_site: "UI Patterns"
track: "Persuasive Design Patterns"
group: "Social"
pattern_count: 17
confidence: "medium"
---
# Social — Persuasive Design Patterns

> Category map imported from [UI Patterns](https://ui-patterns.com/patterns).

## Scope

This category groups 17 cataloged source pages under `Social` / `Persuasive Design Patterns`. It is a navigation layer, not a copy of the source site.

## Patterns

### Social biases

- [[authority-bias|Authority Bias]] — [source](https://ui-patterns.com/patterns/Authority)
- [[autonomy|Autonomy]] — [source](https://ui-patterns.com/patterns/autonomy)
- [[cognitive-dissonance|Cognitive Dissonance]] — [source](https://ui-patterns.com/patterns/cognitive-dissonance)
- [[commitment-and-consistency|Commitment & Consistency]] — [source](https://ui-patterns.com/patterns/Commitment-consistency)
- [[competition|Competition]] — [source](https://ui-patterns.com/patterns/Competition)
- [[halo-effect|Halo Effect]] — [source](https://ui-patterns.com/patterns/halo-effect)
- [[liking|Liking]] — [source](https://ui-patterns.com/patterns/Liking)
- [[noble-edge-effect|Noble Edge Effect]] — [source](https://ui-patterns.com/patterns/noble-edge-effect)
- [[nostalgia-effect|Nostalgia Effect]] — [source](https://ui-patterns.com/patterns/nostalgia-effect)
- [[positive-mimicry|Positive Mimicry]] — [source](https://ui-patterns.com/patterns/Positive-mimicry)
- [[reciprocation|Reciprocation]] — [source](https://ui-patterns.com/patterns/Reciprocation)
- [[reputation|Reputation]] — [source](https://ui-patterns.com/patterns/reputation)
- [[retaliation|Retaliation]] — [source](https://ui-patterns.com/patterns/revenge)
- [[role-playing|Role Playing]] — [source](https://ui-patterns.com/patterns/Roleplaying)
- [[self-expression|Self-Expression]] — [source](https://ui-patterns.com/patterns/Self-expression)
- [[social-proof|Social Proof]] — [source](https://ui-patterns.com/patterns/Social-proof)
- [[status|Status]] — [source](https://ui-patterns.com/patterns/Status)


<!-- ===== ui-patterns/wiki/entities/categories/user-interface-design-patterns-dealing-with-data.md ===== -->

---
title: "Dealing with data — User Interface Design Patterns"
created: "2026-07-02"
updated: "2026-07-02"
type: "entity"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns"
source_site: "UI Patterns"
track: "User Interface Design Patterns"
group: "Dealing with data"
pattern_count: 11
confidence: "medium"
---
# Dealing with data — User Interface Design Patterns

> Category map imported from [UI Patterns](https://ui-patterns.com/patterns).

## Scope

This category groups 11 cataloged source pages under `Dealing with data` / `User Interface Design Patterns`. It is a navigation layer, not a copy of the source site.

## Patterns

### Formatting data

- [[copy-box|Copy Box]] — [source](https://ui-patterns.com/patterns/CopyBox)
- [[dashboard|Dashboard]] — [source](https://ui-patterns.com/patterns/dashboard)
- [[frequently-asked-questions-faq|Frequently Asked Questions (FAQ)]] — [source](https://ui-patterns.com/patterns/frequently-asked-questions-faq)
### Images

- [[gallery|Gallery]] — [source](https://ui-patterns.com/patterns/Gallery)
- [[image-zoom|Image Zoom]] — [source](https://ui-patterns.com/patterns/ImageZoom)
- [[slideshow|Slideshow]] — [source](https://ui-patterns.com/patterns/Slideshow)
### Search

- [[autocomplete|Autocomplete]] — [source](https://ui-patterns.com/patterns/Autocomplete)
- [[search-filters|Search Filters]] — [source](https://ui-patterns.com/patterns/LiveFilter)
### Tables

- [[alternating-row-colors|Alternating Row Colors]] — [source](https://ui-patterns.com/patterns/AlternatingRowColors)
- [[sort-by-column|Sort By Column]] — [source](https://ui-patterns.com/patterns/SortByColumn)
- [[table-filter|Table Filter]] — [source](https://ui-patterns.com/patterns/TableFilter)


<!-- ===== ui-patterns/wiki/entities/categories/user-interface-design-patterns-getting-input.md ===== -->

---
title: "Getting input — User Interface Design Patterns"
created: "2026-07-02"
updated: "2026-07-02"
type: "entity"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns"
source_site: "UI Patterns"
track: "User Interface Design Patterns"
group: "Getting input"
pattern_count: 29
confidence: "medium"
---
# Getting input — User Interface Design Patterns

> Category map imported from [UI Patterns](https://ui-patterns.com/patterns).

## Scope

This category groups 29 cataloged source pages under `Getting input` / `User Interface Design Patterns`. It is a navigation layer, not a copy of the source site.

## Patterns

### Community driven

- [[flagging-and-reporting|Flagging & Reporting]] — [source](https://ui-patterns.com/patterns/flagging-and-reporting)
- [[pay-to-promote|Pay To Promote]] — [source](https://ui-patterns.com/patterns/pay-to-promote)
- [[rate-content|Rate Content]] — [source](https://ui-patterns.com/patterns/RateContent)
- [[vote-to-promote|Vote To Promote]] — [source](https://ui-patterns.com/patterns/VoteToPromote)
- [[wiki|Wiki]] — [source](https://ui-patterns.com/patterns/Wiki)
### Explaining the process

- [[completeness-meter|Completeness meter]] — [source](https://ui-patterns.com/patterns/CompletenessMeter)
- [[inline-help-box|Inline Help Box]] — [source](https://ui-patterns.com/patterns/InlineHelpBox)
- [[steps-left|Steps Left]] — [source](https://ui-patterns.com/patterns/StepsLeft)
- [[wizard|Wizard]] — [source](https://ui-patterns.com/patterns/Wizard)
### Forms

- [[autosave|Autosave]] — [source](https://ui-patterns.com/patterns/autosave)
- [[calendar-picker|Calendar Picker]] — [source](https://ui-patterns.com/patterns/CalendarPicker)
- [[captcha|Captcha]] — [source](https://ui-patterns.com/patterns/Captcha)
- [[drag-and-drop|Drag and drop]] — [source](https://ui-patterns.com/patterns/drag-and-drop)
- [[expandable-input|Expandable Input]] — [source](https://ui-patterns.com/patterns/expandable-input)
- [[fill-in-the-blanks|Fill in the Blanks]] — [source](https://ui-patterns.com/patterns/FillInTheBlanks)
- [[forgiving-format|Forgiving Format]] — [source](https://ui-patterns.com/patterns/ForgivingFormat)
- [[good-defaults|Good Defaults]] — [source](https://ui-patterns.com/patterns/GoodDefaults)
- [[inplace-editor|Inplace Editor]] — [source](https://ui-patterns.com/patterns/InplaceEditor)
- [[input-feedback|Input Feedback]] — [source](https://ui-patterns.com/patterns/InputFeedback)
- [[input-prompt|Input Prompt]] — [source](https://ui-patterns.com/patterns/InputPrompt)
- [[keyboard-shortcuts|Keyboard Shortcuts]] — [source](https://ui-patterns.com/patterns/keyboard-shortcuts)
- [[morphing-controls|Morphing Controls]] — [source](https://ui-patterns.com/patterns/morphing-controls)
- [[password-strength-meter|Password Strength Meter]] — [source](https://ui-patterns.com/patterns/PasswordStrengthMeter)
- [[preview|Preview]] — [source](https://ui-patterns.com/patterns/LivePreview)
- [[rule-builder|Rule Builder]] — [source](https://ui-patterns.com/patterns/rule-builder)
- [[settings|Settings]] — [source](https://ui-patterns.com/patterns/settings)
- [[structured-format|Structured Format]] — [source](https://ui-patterns.com/patterns/StructuredFormat)
- [[undo|Undo]] — [source](https://ui-patterns.com/patterns/undo)
- [[wysiwyg|WYSIWYG]] — [source](https://ui-patterns.com/patterns/WYSIWYG)


<!-- ===== ui-patterns/wiki/entities/categories/user-interface-design-patterns-miscellaneous.md ===== -->

---
title: "Miscellaneous — User Interface Design Patterns"
created: "2026-07-02"
updated: "2026-07-02"
type: "entity"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns"
source_site: "UI Patterns"
track: "User Interface Design Patterns"
group: "Miscellaneous"
pattern_count: 5
confidence: "medium"
---
# Miscellaneous — User Interface Design Patterns

> Category map imported from [UI Patterns](https://ui-patterns.com/patterns).

## Scope

This category groups 5 cataloged source pages under `Miscellaneous` / `User Interface Design Patterns`. It is a navigation layer, not a copy of the source site.

## Patterns

### Increasing frequency

- [[tip-a-friend|Tip A Friend]] — [source](https://ui-patterns.com/patterns/TipAFriend)
### Shopping

- [[coupon|Coupon]] — [source](https://ui-patterns.com/patterns/Coupon)
- [[pricing-table|Pricing table]] — [source](https://ui-patterns.com/patterns/PricingTable)
- [[product-page|Product page]] — [source](https://ui-patterns.com/patterns/ProductPage)
- [[shopping-cart|Shopping Cart]] — [source](https://ui-patterns.com/patterns/ShoppingCart)


<!-- ===== ui-patterns/wiki/entities/categories/user-interface-design-patterns-navigation.md ===== -->

---
title: "Navigation — User Interface Design Patterns"
created: "2026-07-02"
updated: "2026-07-02"
type: "entity"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns"
source_site: "UI Patterns"
track: "User Interface Design Patterns"
group: "Navigation"
pattern_count: 26
confidence: "medium"
---
# Navigation — User Interface Design Patterns

> Category map imported from [UI Patterns](https://ui-patterns.com/patterns).

## Scope

This category groups 26 cataloged source pages under `Navigation` / `User Interface Design Patterns`. It is a navigation layer, not a copy of the source site.

## Patterns

### Content

- [[adaptable-view|Adaptable View]] — [source](https://ui-patterns.com/patterns/AdaptableView)
- [[archive|Archive]] — [source](https://ui-patterns.com/patterns/Archive)
- [[article-list|Article List]] — [source](https://ui-patterns.com/patterns/ArticleList)
- [[cards|Cards]] — [source](https://ui-patterns.com/patterns/cards)
- [[carousel|Carousel]] — [source](https://ui-patterns.com/patterns/Carousel)
- [[categorization|Categorization]] — [source](https://ui-patterns.com/patterns/categorization)
- [[continuous-scrolling|Continuous Scrolling]] — [source](https://ui-patterns.com/patterns/ContinuousScrolling)
- [[event-calendar|Event Calendar]] — [source](https://ui-patterns.com/patterns/EventCalendar)
- [[favorites|Favorites]] — [source](https://ui-patterns.com/patterns/favorites)
- [[pagination|Pagination]] — [source](https://ui-patterns.com/patterns/Pagination)
- [[progressive-disclosure|Progressive Disclosure]] — [source](https://ui-patterns.com/patterns/ProgressiveDisclosure)
- [[tag-cloud|Tag Cloud]] — [source](https://ui-patterns.com/patterns/TagCloud)
- [[tagging|Tagging]] — [source](https://ui-patterns.com/patterns/Tag)
- [[thumbnail|Thumbnail]] — [source](https://ui-patterns.com/patterns/Thumbnail)
### Gestures

- [[pull-to-refresh|Pull to refresh]] — [source](https://ui-patterns.com/patterns/pull-to-refresh)
### Jumping in hierarchy

- [[breadcrumbs|Breadcrumbs]] — [source](https://ui-patterns.com/patterns/Breadcrumbs)
- [[fat-footer|Fat Footer]] — [source](https://ui-patterns.com/patterns/FatFooter)
- [[home-link|Home Link]] — [source](https://ui-patterns.com/patterns/HomeLink)
- [[modal|Modal]] — [source](https://ui-patterns.com/patterns/modal-windows)
- [[notifications|Notifications]] — [source](https://ui-patterns.com/patterns/notifications)
- [[shortcut-dropdown|Shortcut Dropdown]] — [source](https://ui-patterns.com/patterns/ShortcutDropdown)
### Menus

- [[accordion-menu|Accordion Menu]] — [source](https://ui-patterns.com/patterns/AccordionMenu)
- [[horizontal-dropdown-menu|Horizontal Dropdown Menu]] — [source](https://ui-patterns.com/patterns/HorizontalDropdownMenu)
- [[vertical-dropdown-menu|Vertical Dropdown Menu]] — [source](https://ui-patterns.com/patterns/VerticalDropdownMenu)
### Tabs

- [[module-tabs|Module Tabs]] — [source](https://ui-patterns.com/patterns/ModuleTabs)
- [[navigation-tabs|Navigation Tabs]] — [source](https://ui-patterns.com/patterns/NavigationTabs)


<!-- ===== ui-patterns/wiki/entities/categories/user-interface-design-patterns-onboarding.md ===== -->

---
title: "Onboarding — User Interface Design Patterns"
created: "2026-07-02"
updated: "2026-07-02"
type: "entity"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns"
source_site: "UI Patterns"
track: "User Interface Design Patterns"
group: "Onboarding"
pattern_count: 9
confidence: "medium"
---
# Onboarding — User Interface Design Patterns

> Category map imported from [UI Patterns](https://ui-patterns.com/patterns).

## Scope

This category groups 9 cataloged source pages under `Onboarding` / `User Interface Design Patterns`. It is a navigation layer, not a copy of the source site.

## Patterns

### Guidance

- [[blank-slate|Blank Slate]] — [source](https://ui-patterns.com/patterns/BlankSlate)
- [[coachmarks|Coachmarks]] — [source](https://ui-patterns.com/patterns/coachmarks)
- [[guided-tour|Guided Tour]] — [source](https://ui-patterns.com/patterns/Guided-tour)
- [[inline-hints|Inline Hints]] — [source](https://ui-patterns.com/patterns/inline-hints)
- [[playthrough|Playthrough]] — [source](https://ui-patterns.com/patterns/playthrough)
- [[walkthrough|Walkthrough]] — [source](https://ui-patterns.com/patterns/Tour)
### Registration

- [[account-registration|Account Registration]] — [source](https://ui-patterns.com/patterns/AccountRegistration)
- [[lazy-registration|Lazy Registration]] — [source](https://ui-patterns.com/patterns/LazyRegistration)
- [[paywall|Paywall]] — [source](https://ui-patterns.com/patterns/Paywall)


<!-- ===== ui-patterns/wiki/entities/categories/user-interface-design-patterns-social.md ===== -->

---
title: "Social — User Interface Design Patterns"
created: "2026-07-02"
updated: "2026-07-02"
type: "entity"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns"
source_site: "UI Patterns"
track: "User Interface Design Patterns"
group: "Social"
pattern_count: 11
confidence: "medium"
---
# Social — User Interface Design Patterns

> Category map imported from [UI Patterns](https://ui-patterns.com/patterns).

## Scope

This category groups 11 cataloged source pages under `Social` / `User Interface Design Patterns`. It is a navigation layer, not a copy of the source site.

## Patterns

### Reputation

- [[collectible-achievements|Collectible Achievements]] — [source](https://ui-patterns.com/patterns/CollectibleAchievements)
- [[leaderboard|Leaderboard]] — [source](https://ui-patterns.com/patterns/leaderboard)
- [[testimonials|Testimonials]] — [source](https://ui-patterns.com/patterns/testimonials)
### Social interactions

- [[activity-stream|Activity Stream]] — [source](https://ui-patterns.com/patterns/ActivityStream)
- [[auto-sharing|Auto-sharing]] — [source](https://ui-patterns.com/patterns/auto-sharing)
- [[chat|Chat]] — [source](https://ui-patterns.com/patterns/direct-messaging)
- [[follow|Follow]] — [source](https://ui-patterns.com/patterns/follow)
- [[friend|Friend]] — [source](https://ui-patterns.com/patterns/friend)
- [[friend-list|Friend list]] — [source](https://ui-patterns.com/patterns/friend-list)
- [[invite-friends|Invite friends]] — [source](https://ui-patterns.com/patterns/invite-friends)
- [[reaction|Reaction]] — [source](https://ui-patterns.com/patterns/reaction)


<!-- ===== ui-patterns/wiki/entities/source-site-ui-patterns.md ===== -->

---
title: "Source Site — UI Patterns"
created: "2026-07-02"
updated: "2026-07-02"
type: "entity"
status: "compiled"
category: "product-design"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com"
---
# Source Site — UI Patterns

UI Patterns is the source site for this namespace's catalog records.

## Source Facts Captured

- Base URL: https://ui-patterns.com
- Pattern index URL: https://ui-patterns.com/patterns
- Retrieved at: 2026-07-02T18:23:09+00:00
- Pattern pages cataloged: 170
- Tracks cataloged: Persuasive Design Patterns, User Interface Design Patterns

## Pixi Wiki Role

Pixi Wiki provides an agent-readable index, category map, and retrieval contract over the source site. It does not replace the source site.


<!-- ===== ui-patterns/wiki/index.md ===== -->

---
title: "UI Patterns KB — Master Index"
created: "2026-07-02"
updated: "2026-07-02"
type: "wiki"
status: "active"
category: "product-design"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns"
---
# UI Patterns KB — Master Index

## Start Here

- [[summaries/for-agents-ui-patterns-retrieval|For Agents — UI Patterns Retrieval]]
- [[summaries/provenance-and-copyright-boundary|Provenance and Copyright Boundary]]
- [[summaries/source-taxonomy|Source Taxonomy]]
- [[entities/source-site-ui-patterns|Source Site — UI Patterns]]

## Category Maps

- [[entities/categories/persuasive-design-patterns-cognition|Cognition — Persuasive Design Patterns]]
- [[entities/categories/persuasive-design-patterns-feedback|Feedback — Persuasive Design Patterns]]
- [[entities/categories/persuasive-design-patterns-game-mechanics|Game mechanics — Persuasive Design Patterns]]
- [[entities/categories/persuasive-design-patterns-perception-and-memory|Perception and memory — Persuasive Design Patterns]]
- [[entities/categories/persuasive-design-patterns-social|Social — Persuasive Design Patterns]]
- [[entities/categories/user-interface-design-patterns-dealing-with-data|Dealing with data — User Interface Design Patterns]]
- [[entities/categories/user-interface-design-patterns-getting-input|Getting input — User Interface Design Patterns]]
- [[entities/categories/user-interface-design-patterns-miscellaneous|Miscellaneous — User Interface Design Patterns]]
- [[entities/categories/user-interface-design-patterns-navigation|Navigation — User Interface Design Patterns]]
- [[entities/categories/user-interface-design-patterns-onboarding|Onboarding — User Interface Design Patterns]]
- [[entities/categories/user-interface-design-patterns-social|Social — User Interface Design Patterns]]

## Pattern Catalog

- [[concepts/patterns/accordion-menu|Accordion Menu]] — User Interface Design Patterns / Navigation / Menus
- [[concepts/patterns/account-registration|Account Registration]] — User Interface Design Patterns / Onboarding / Registration
- [[concepts/patterns/achievements|Achievements]] — Persuasive Design Patterns / Game mechanics / Gameplay rewards
- [[concepts/patterns/activity-stream|Activity Stream]] — User Interface Design Patterns / Social / Social interactions
- [[concepts/patterns/adaptable-view|Adaptable View]] — User Interface Design Patterns / Navigation / Content
- [[concepts/patterns/alternating-row-colors|Alternating Row Colors]] — User Interface Design Patterns / Dealing with data / Tables
- [[concepts/patterns/anchoring|Anchoring]] — Persuasive Design Patterns / Perception and memory / Comprehension
- [[concepts/patterns/appointment-dynamic|Appointment Dynamic]] — Persuasive Design Patterns / Game mechanics / Gameplay rewards
- [[concepts/patterns/appropriate-challenge|Appropriate Challenge]] — Persuasive Design Patterns / Game mechanics / Gameplay design
- [[concepts/patterns/archive|Archive]] — User Interface Design Patterns / Navigation / Content
- [[concepts/patterns/article-list|Article List]] — User Interface Design Patterns / Navigation / Content
- [[concepts/patterns/authority-bias|Authority Bias]] — Persuasive Design Patterns / Social / Social biases
- [[concepts/patterns/auto-sharing|Auto-sharing]] — User Interface Design Patterns / Social / Social interactions
- [[concepts/patterns/autocomplete|Autocomplete]] — User Interface Design Patterns / Dealing with data / Search
- [[concepts/patterns/autonomy|Autonomy]] — Persuasive Design Patterns / Social / Social biases
- [[concepts/patterns/autosave|Autosave]] — User Interface Design Patterns / Getting input / Forms
- [[concepts/patterns/blank-slate|Blank Slate]] — User Interface Design Patterns / Onboarding / Guidance
- [[concepts/patterns/breadcrumbs|Breadcrumbs]] — User Interface Design Patterns / Navigation / Jumping in hierarchy
- [[concepts/patterns/calendar-picker|Calendar Picker]] — User Interface Design Patterns / Getting input / Forms
- [[concepts/patterns/captcha|Captcha]] — User Interface Design Patterns / Getting input / Forms
- [[concepts/patterns/cards|Cards]] — User Interface Design Patterns / Navigation / Content
- [[concepts/patterns/carousel|Carousel]] — User Interface Design Patterns / Navigation / Content
- [[concepts/patterns/cashless-effect|Cashless Effect]] — Persuasive Design Patterns / Cognition / Other cognitive biases
- [[concepts/patterns/categorization|Categorization]] — User Interface Design Patterns / Navigation / Content
- [[concepts/patterns/chat|Chat]] — User Interface Design Patterns / Social / Social interactions
- [[concepts/patterns/choice-closure|Choice Closure]] — Persuasive Design Patterns / Cognition / Other cognitive biases
- [[concepts/patterns/chunking|Chunking]] — Persuasive Design Patterns / Perception and memory / Comprehension
- [[concepts/patterns/coachmarks|Coachmarks]] — User Interface Design Patterns / Onboarding / Guidance
- [[concepts/patterns/cognitive-dissonance|Cognitive Dissonance]] — Persuasive Design Patterns / Social / Social biases
- [[concepts/patterns/collectible-achievements|Collectible Achievements]] — User Interface Design Patterns / Social / Reputation
- [[concepts/patterns/commitment-and-consistency|Commitment & Consistency]] — Persuasive Design Patterns / Social / Social biases
- [[concepts/patterns/competition|Competition]] — Persuasive Design Patterns / Social / Social biases
- [[concepts/patterns/completeness-meter|Completeness meter]] — User Interface Design Patterns / Getting input / Explaining the process
- [[concepts/patterns/conceptual-metaphor|Conceptual Metaphor]] — Persuasive Design Patterns / Perception and memory / Comprehension
- [[concepts/patterns/continuous-scrolling|Continuous Scrolling]] — User Interface Design Patterns / Navigation / Content
- [[concepts/patterns/copy-box|Copy Box]] — User Interface Design Patterns / Dealing with data / Formatting data
- [[concepts/patterns/coupon|Coupon]] — User Interface Design Patterns / Miscellaneous / Shopping
- [[concepts/patterns/curiosity|Curiosity]] — Persuasive Design Patterns / Cognition / Other cognitive biases
- [[concepts/patterns/dashboard|Dashboard]] — User Interface Design Patterns / Dealing with data / Formatting data
- [[concepts/patterns/decoy-effect|Decoy Effect]] — Persuasive Design Patterns / Cognition / Loss Aversion
- [[concepts/patterns/delay-discounting|Delay Discounting]] — Persuasive Design Patterns / Cognition / Other cognitive biases
- [[concepts/patterns/delighters|Delighters]] — Persuasive Design Patterns / Game mechanics / Gameplay rewards
- [[concepts/patterns/drag-and-drop|Drag and drop]] — User Interface Design Patterns / Getting input / Forms
- [[concepts/patterns/endowment-effect|Endowment Effect]] — Persuasive Design Patterns / Cognition / Loss Aversion
- [[concepts/patterns/event-calendar|Event Calendar]] — User Interface Design Patterns / Navigation / Content
- [[concepts/patterns/expandable-input|Expandable Input]] — User Interface Design Patterns / Getting input / Forms
- [[concepts/patterns/fat-footer|Fat Footer]] — User Interface Design Patterns / Navigation / Jumping in hierarchy
- [[concepts/patterns/favorites|Favorites]] — User Interface Design Patterns / Navigation / Content
- [[concepts/patterns/feedback-loops|Feedback Loops]] — Persuasive Design Patterns / Feedback / Timing
- [[concepts/patterns/fill-in-the-blanks|Fill in the Blanks]] — User Interface Design Patterns / Getting input / Forms
- [[concepts/patterns/fixed-rewards|Fixed rewards]] — Persuasive Design Patterns / Game mechanics / Fundamentals of rewards
- [[concepts/patterns/flagging-and-reporting|Flagging & Reporting]] — User Interface Design Patterns / Getting input / Community driven
- [[concepts/patterns/follow|Follow]] — User Interface Design Patterns / Social / Social interactions
- [[concepts/patterns/forgiving-format|Forgiving Format]] — User Interface Design Patterns / Getting input / Forms
- [[concepts/patterns/framing|Framing]] — Persuasive Design Patterns / Cognition / Loss Aversion
- [[concepts/patterns/frequently-asked-questions-faq|Frequently Asked Questions (FAQ)]] — User Interface Design Patterns / Dealing with data / Formatting data
- [[concepts/patterns/fresh-start-effect|Fresh Start Effect]] — Persuasive Design Patterns / Feedback / Timing
- [[concepts/patterns/friend|Friend]] — User Interface Design Patterns / Social / Social interactions
- [[concepts/patterns/friend-list|Friend list]] — User Interface Design Patterns / Social / Social interactions
- [[concepts/patterns/gallery|Gallery]] — User Interface Design Patterns / Dealing with data / Images
- [[concepts/patterns/goal-gradient-effect|Goal-Gradient Effect]] — Persuasive Design Patterns / Game mechanics / Gameplay rewards
- [[concepts/patterns/good-defaults|Good Defaults]] — User Interface Design Patterns / Getting input / Forms
- [[concepts/patterns/guided-tour|Guided Tour]] — User Interface Design Patterns / Onboarding / Guidance
- [[concepts/patterns/halo-effect|Halo Effect]] — Persuasive Design Patterns / Social / Social biases
- [[concepts/patterns/hedonic-adaptation|Hedonic Adaptation]] — Persuasive Design Patterns / Game mechanics / Gameplay design
- [[concepts/patterns/home-link|Home Link]] — User Interface Design Patterns / Navigation / Jumping in hierarchy
- [[concepts/patterns/horizontal-dropdown-menu|Horizontal Dropdown Menu]] — User Interface Design Patterns / Navigation / Menus
- [[concepts/patterns/ikea-effect|IKEA effect]] — Persuasive Design Patterns / Cognition / Loss Aversion
- [[concepts/patterns/illusion-of-control|Illusion of control]] — Persuasive Design Patterns / Cognition / Other cognitive biases
- [[concepts/patterns/image-zoom|Image Zoom]] — User Interface Design Patterns / Dealing with data / Images
- [[concepts/patterns/inaction-inertia-effect|Inaction Inertia Effect]] — Persuasive Design Patterns / Cognition / Other cognitive biases
- [[concepts/patterns/inline-help-box|Inline Help Box]] — User Interface Design Patterns / Getting input / Explaining the process
- [[concepts/patterns/inline-hints|Inline Hints]] — User Interface Design Patterns / Onboarding / Guidance
- [[concepts/patterns/inplace-editor|Inplace Editor]] — User Interface Design Patterns / Getting input / Forms
- [[concepts/patterns/input-feedback|Input Feedback]] — User Interface Design Patterns / Getting input / Forms
- [[concepts/patterns/input-prompt|Input Prompt]] — User Interface Design Patterns / Getting input / Forms
- [[concepts/patterns/intentional-gaps|Intentional Gaps]] — Persuasive Design Patterns / Game mechanics / Gameplay design
- [[concepts/patterns/investment-loops|Investment Loops]] — Persuasive Design Patterns / Game mechanics / Gameplay design
- [[concepts/patterns/invite-friends|Invite friends]] — User Interface Design Patterns / Social / Social interactions
- [[concepts/patterns/isolation-effect|Isolation Effect]] — Persuasive Design Patterns / Perception and memory / Attention
- [[concepts/patterns/kairos|Kairos]] — Persuasive Design Patterns / Feedback / Timing
- [[concepts/patterns/keyboard-shortcuts|Keyboard Shortcuts]] — User Interface Design Patterns / Getting input / Forms
- [[concepts/patterns/lazy-registration|Lazy Registration]] — User Interface Design Patterns / Onboarding / Registration
- [[concepts/patterns/leaderboard|Leaderboard]] — User Interface Design Patterns / Social / Reputation
- [[concepts/patterns/levels|Levels]] — Persuasive Design Patterns / Game mechanics / Gameplay design
- [[concepts/patterns/liking|Liking]] — Persuasive Design Patterns / Social / Social biases
- [[concepts/patterns/limited-choice|Limited Choice]] — Persuasive Design Patterns / Cognition / Scarcity
- [[concepts/patterns/limited-duration|Limited duration]] — Persuasive Design Patterns / Cognition / Scarcity
- [[concepts/patterns/loss-aversion|Loss Aversion]] — Persuasive Design Patterns / Cognition / Loss Aversion
- [[concepts/patterns/modal|Modal]] — User Interface Design Patterns / Navigation / Jumping in hierarchy
- [[concepts/patterns/module-tabs|Module Tabs]] — User Interface Design Patterns / Navigation / Tabs
- [[concepts/patterns/morphing-controls|Morphing Controls]] — User Interface Design Patterns / Getting input / Forms
- [[concepts/patterns/navigation-tabs|Navigation Tabs]] — User Interface Design Patterns / Navigation / Tabs
- [[concepts/patterns/need-for-closure|Need for Closure]] — Persuasive Design Patterns / Cognition / Other cognitive biases
- [[concepts/patterns/negativity-bias|Negativity bias]] — Persuasive Design Patterns / Cognition / Loss Aversion
- [[concepts/patterns/noble-edge-effect|Noble Edge Effect]] — Persuasive Design Patterns / Social / Social biases
- [[concepts/patterns/nostalgia-effect|Nostalgia Effect]] — Persuasive Design Patterns / Social / Social biases
- [[concepts/patterns/notifications|Notifications]] — User Interface Design Patterns / Navigation / Jumping in hierarchy
- [[concepts/patterns/optimism-bias|Optimism Bias]] — Persuasive Design Patterns / Cognition / Loss Aversion
- [[concepts/patterns/pagination|Pagination]] — User Interface Design Patterns / Navigation / Content
- [[concepts/patterns/password-strength-meter|Password Strength Meter]] — User Interface Design Patterns / Getting input / Forms
- [[concepts/patterns/pattern-recognition|Pattern Recognition]] — Persuasive Design Patterns / Perception and memory / Comprehension
- [[concepts/patterns/pay-to-promote|Pay To Promote]] — User Interface Design Patterns / Getting input / Community driven
- [[concepts/patterns/paywall|Paywall]] — User Interface Design Patterns / Onboarding / Registration
- [[concepts/patterns/peak-end-rule|Peak-end rule]] — Persuasive Design Patterns / Cognition / Other cognitive biases
- [[concepts/patterns/periodic-events|Periodic Events]] — Persuasive Design Patterns / Game mechanics / Gameplay design
- [[concepts/patterns/picture-superiority-effect|Picture Superiority Effect]] — Persuasive Design Patterns / Perception and memory / Attention
- [[concepts/patterns/playthrough|Playthrough]] — User Interface Design Patterns / Onboarding / Guidance
- [[concepts/patterns/positive-mimicry|Positive Mimicry]] — Persuasive Design Patterns / Social / Social biases
- [[concepts/patterns/praise|Praise]] — Persuasive Design Patterns / Game mechanics / Gameplay rewards
- [[concepts/patterns/present-bias|Present Bias]] — Persuasive Design Patterns / Cognition / Other cognitive biases
- [[concepts/patterns/preview|Preview]] — User Interface Design Patterns / Getting input / Forms
- [[concepts/patterns/pricing-table|Pricing table]] — User Interface Design Patterns / Miscellaneous / Shopping
- [[concepts/patterns/priming-effect|Priming Effect]] — Persuasive Design Patterns / Cognition / Other cognitive biases
- [[concepts/patterns/privileges|Privileges]] — Persuasive Design Patterns / Game mechanics / Gameplay rewards
- [[concepts/patterns/product-page|Product page]] — User Interface Design Patterns / Miscellaneous / Shopping
- [[concepts/patterns/progressive-disclosure|Progressive Disclosure]] — User Interface Design Patterns / Navigation / Content
- [[concepts/patterns/prolonged-play|Prolonged Play]] — Persuasive Design Patterns / Game mechanics / Gameplay rewards
- [[concepts/patterns/pull-to-refresh|Pull to refresh]] — User Interface Design Patterns / Navigation / Gestures
- [[concepts/patterns/rate-content|Rate Content]] — User Interface Design Patterns / Getting input / Community driven
- [[concepts/patterns/reaction|Reaction]] — User Interface Design Patterns / Social / Social interactions
- [[concepts/patterns/reciprocation|Reciprocation]] — Persuasive Design Patterns / Social / Social biases
- [[concepts/patterns/recognition-over-recall|Recognition over Recall]] — Persuasive Design Patterns / Perception and memory / Comprehension
- [[concepts/patterns/reduction|Reduction]] — Persuasive Design Patterns / Perception and memory / Attention
- [[concepts/patterns/reputation|Reputation]] — Persuasive Design Patterns / Social / Social biases
- [[concepts/patterns/retaliation|Retaliation]] — Persuasive Design Patterns / Social / Social biases
- [[concepts/patterns/role-playing|Role Playing]] — Persuasive Design Patterns / Social / Social biases
- [[concepts/patterns/rule-builder|Rule Builder]] — User Interface Design Patterns / Getting input / Forms
- [[concepts/patterns/scarcity|Scarcity]] — Persuasive Design Patterns / Cognition / Scarcity
- [[concepts/patterns/search-filters|Search Filters]] — User Interface Design Patterns / Dealing with data / Search
- [[concepts/patterns/self-expression|Self-Expression]] — Persuasive Design Patterns / Social / Social biases
- [[concepts/patterns/self-monitoring|Self-Monitoring]] — Persuasive Design Patterns / Game mechanics / Gameplay design
- [[concepts/patterns/sequencing|Sequencing]] — Persuasive Design Patterns / Perception and memory / Comprehension
- [[concepts/patterns/serial-positioning-effect|Serial Positioning Effect]] — Persuasive Design Patterns / Perception and memory / Comprehension
- [[concepts/patterns/set-completion|Set Completion]] — Persuasive Design Patterns / Cognition / Other cognitive biases
- [[concepts/patterns/settings|Settings]] — User Interface Design Patterns / Getting input / Forms
- [[concepts/patterns/shaping|Shaping]] — Persuasive Design Patterns / Game mechanics / Fundamentals of rewards
- [[concepts/patterns/shopping-cart|Shopping Cart]] — User Interface Design Patterns / Miscellaneous / Shopping
- [[concepts/patterns/shortcut-dropdown|Shortcut Dropdown]] — User Interface Design Patterns / Navigation / Jumping in hierarchy
- [[concepts/patterns/simulation|Simulation]] — Persuasive Design Patterns / Feedback / Timing
- [[concepts/patterns/slideshow|Slideshow]] — User Interface Design Patterns / Dealing with data / Images
- [[concepts/patterns/social-proof|Social Proof]] — Persuasive Design Patterns / Social / Social biases
- [[concepts/patterns/sort-by-column|Sort By Column]] — User Interface Design Patterns / Dealing with data / Tables
- [[concepts/patterns/status|Status]] — Persuasive Design Patterns / Social / Social biases
- [[concepts/patterns/status-quo-bias|Status-Quo Bias]] — Persuasive Design Patterns / Cognition / Loss Aversion
- [[concepts/patterns/steps-left|Steps Left]] — User Interface Design Patterns / Getting input / Explaining the process
- [[concepts/patterns/storytelling|Storytelling]] — Persuasive Design Patterns / Game mechanics / Gameplay design
- [[concepts/patterns/structured-format|Structured Format]] — User Interface Design Patterns / Getting input / Forms
- [[concepts/patterns/sunk-cost-effect|Sunk Cost Effect]] — Persuasive Design Patterns / Cognition / Loss Aversion
- [[concepts/patterns/table-filter|Table Filter]] — User Interface Design Patterns / Dealing with data / Tables
- [[concepts/patterns/tag-cloud|Tag Cloud]] — User Interface Design Patterns / Navigation / Content
- [[concepts/patterns/tagging|Tagging]] — User Interface Design Patterns / Navigation / Content
- [[concepts/patterns/tailoring|Tailoring]] — Persuasive Design Patterns / Feedback / Timing
- [[concepts/patterns/temptation-bundling|Temptation Bundling]] — Persuasive Design Patterns / Cognition / Other cognitive biases
- [[concepts/patterns/testimonials|Testimonials]] — User Interface Design Patterns / Social / Reputation
- [[concepts/patterns/thumbnail|Thumbnail]] — User Interface Design Patterns / Navigation / Content
- [[concepts/patterns/tip-a-friend|Tip A Friend]] — User Interface Design Patterns / Miscellaneous / Increasing frequency
- [[concepts/patterns/trigger|Trigger]] — Persuasive Design Patterns / Feedback / Timing
- [[concepts/patterns/tunnelling|Tunnelling]] — Persuasive Design Patterns / Perception and memory / Attention
- [[concepts/patterns/undo|Undo]] — User Interface Design Patterns / Getting input / Forms
- [[concepts/patterns/unlock-features|Unlock Features]] — Persuasive Design Patterns / Game mechanics / Gameplay rewards
- [[concepts/patterns/value-attribution|Value Attribution]] — Persuasive Design Patterns / Cognition / Other cognitive biases
- [[concepts/patterns/variable-rewards|Variable Rewards]] — Persuasive Design Patterns / Game mechanics / Fundamentals of rewards
- [[concepts/patterns/vertical-dropdown-menu|Vertical Dropdown Menu]] — User Interface Design Patterns / Navigation / Menus
- [[concepts/patterns/vote-to-promote|Vote To Promote]] — User Interface Design Patterns / Getting input / Community driven
- [[concepts/patterns/walkthrough|Walkthrough]] — User Interface Design Patterns / Onboarding / Guidance
- [[concepts/patterns/wiki|Wiki]] — User Interface Design Patterns / Getting input / Community driven
- [[concepts/patterns/wizard|Wizard]] — User Interface Design Patterns / Getting input / Explaining the process
- [[concepts/patterns/wysiwyg|WYSIWYG]] — User Interface Design Patterns / Getting input / Forms
- [[concepts/patterns/zeigarnik-effect|Zeigarnik Effect]] — Persuasive Design Patterns / Perception and memory / Attention


<!-- ===== ui-patterns/wiki/log.md ===== -->

---
title: "UI Patterns — Activity Log"
created: "2026-07-02"
updated: "2026-07-02"
type: "wiki"
status: "active"
category: "product-design"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns"
---
# UI Patterns — Activity Log

## 2026-07-02

- Checked robots policy: `User-agent: *`, `Disallow: /search`.
- Imported the `/patterns` catalog as 170 pattern routing pages.
- Preserved taxonomy, source URLs, detected source sections, example counts, and provenance notes.
- Avoided republishing full source bodies/screenshots because the source site footer says all rights reserved.


<!-- ===== ui-patterns/wiki/summaries/for-agents-ui-patterns-retrieval.md ===== -->

---
title: "For Agents — UI Patterns Retrieval"
created: "2026-07-02"
updated: "2026-07-02"
type: "summaries"
status: "compiled"
category: "product-design"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns"
---
# For Agents — UI Patterns Retrieval

> Use this namespace to find candidate UI/product/persuasive design patterns, then retrieve the original source page for exact language and examples.

## Retrieval Loop

1. Identify the product moment: input, navigation, data display, social behavior, onboarding, persuasion, feedback, or game mechanic.
2. Search this namespace by track/group/subgroup/title.
3. Pull 3–8 nearby pattern pages rather than one isolated pattern.
4. Open the source URLs for the finalists before using exact claims, screenshots, or usage constraints.
5. Translate the pattern into product-specific guidance: trigger, user goal, risk, UI move, success/failure signal.
6. Cite pattern names plus source URLs in the recommendation.

## Good Uses

- Product critique and UX review.
- Generating design alternatives for a flow.
- Naming recurring interaction patterns in PRDs/specs.
- Checking persuasive mechanics for ethics/risk before implementation.

## Guardrails

- Do not imply the catalog is commercial-clean training data.
- Do not bulk-quote source pages into public docs.
- Do not treat persuasive patterns as default recommendations; apply Jamie's verb-first/product-urge lens and consider user trust.
- For screenshots, link to the source page instead of copying images.


<!-- ===== ui-patterns/wiki/summaries/provenance-and-copyright-boundary.md ===== -->

---
title: "Provenance and Copyright Boundary"
created: "2026-07-02"
updated: "2026-07-02"
type: "summaries"
status: "compiled"
category: "product-design"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns"
---
# Provenance and Copyright Boundary

## Source

- Site: [UI Patterns](https://ui-patterns.com)
- Pattern index: [Design patterns](https://ui-patterns.com/patterns)
- Robots policy: `/search` is disallowed; `/patterns` is not disallowed.
- Footer at retrieval time: `© 2007-2026 Learning Loop ApS. All rights reserved.`

## Boundary

This namespace is a public catalog and retrieval map. It keeps factual routing metadata: titles, taxonomy, URLs, detected section headings, example counts, and source-shape notes. It does not mirror full source explanations, screenshots, examples, comments, or paid product content.

## Allowed Agent Behavior

- Link to source pages.
- Use pattern names/taxonomy as retrieval handles.
- Paraphrase lessons after reading the source and applying them to a specific product context.
- Quote only short bounded snippets when the user explicitly needs exact wording.

## Avoid

- Republishing full pattern pages.
- Copying screenshots into Pixi Wiki.
- Presenting the corpus as a clean dataset for training or commercial redistribution.


<!-- ===== ui-patterns/wiki/summaries/source-taxonomy.md ===== -->

---
title: "Source Taxonomy"
created: "2026-07-02"
updated: "2026-07-02"
type: "summaries"
status: "compiled"
category: "product-design"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns"
---
# Source Taxonomy

> Imported taxonomy from the UI Patterns `/patterns` page.

## Persuasive Design Patterns

- Cognition: 25 patterns across 3 subgroups
- Feedback: 6 patterns across 1 subgroups
- Game mechanics: 19 patterns across 3 subgroups
- Perception and memory: 12 patterns across 2 subgroups
- Social: 17 patterns across 1 subgroups
## User Interface Design Patterns

- Dealing with data: 11 patterns across 4 subgroups
- Getting input: 29 patterns across 3 subgroups
- Miscellaneous: 5 patterns across 2 subgroups
- Navigation: 26 patterns across 5 subgroups
- Onboarding: 9 patterns across 2 subgroups
- Social: 11 patterns across 2 subgroups