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.

External links

• ui-patterns.com/patterns