About UI Pattern Diagnostic.

01 · Purpose

Why this site exists

UI Pattern Diagnostic helps independent developers and coding-agent users turn ambiguous interface descriptions into a short list of reviewed patterns, decisive differences, implementation requirements, and observable checks. It is designed for the moment when a user knows what an interface should do but does not know the correct term or the behavior hidden behind that term.

02 · Scope

What the reference covers

The current release covers 20 English web UI concepts organized into six ambiguity clusters. It does not cover native mobile or desktop interfaces, screenshot recognition, full code generation, every design-system component, or every possible product context. A no-match result is valid when the evidence does not support the reviewed set.

03 · Editorial method

How content is maintained

Behavior claims prefer platform documentation, W3C accessibility guidance, and official first-party component documentation. Sources are attached to the claim they support. A source count is not treated as a confidence score, and component-library naming is not presented as a universal standard.

Corrections are welcome at tangjei414@gmail.com. Include the page, disputed statement, and a primary or first-party source when possible.

04 · Evidence boundary

What public availability does not prove

A working site does not prove market demand, search traffic, repeat use, ranking, or willingness to pay. Those remain separate validation questions. The reference should be judged by whether its distinctions and checks help users make and verify better implementation decisions.