Using the diagnostic
Get a more useful UI pattern diagnosis.
Describe observable behavior, answer only the questions that change the decision, and verify the generated brief in the interface you actually ship.
01 · Describe
Write a useful field report
Include the trigger, placement, content, interactivity, dismissal, focus, keyboard behavior, background availability, persistence, and mobile expectation you can observe. Do not paste secrets, private source code, customer data, or internal URLs. The first release accepts English web UI descriptions up to 500 characters.
02 · Compare
Read candidates as alternatives
The leading candidate is not automatically correct. Read why each candidate fits and what boundary must be confirmed. Use the comparison matrix and answer a question only when its options reflect the real requirement. Choose “Not sure” instead of inventing evidence.
03 · Verify
Use the brief as a test contract
Copy the implementation brief into your coding workflow, then check the rendered result. Test the trigger, close path, keyboard behavior, focus movement and return, modality, interactive content, placement, narrow-screen adaptation, and the pattern-specific acceptance list. A copied brief does not prove the implementation is correct.
04 · Troubleshoot
When the result is weak or missing
If the site returns no match, add the behavior that distinguishes nearby patterns rather than adding more visual adjectives. If a recommendation appears wrong, compare the rejected alternative and review its source. Report reproducible content or site issues through the contact page.