namethatui
Installation
SKILL.md
namethatui
Turn “I know it when I see it” into precise UI vocabulary, evidence-backed links, and wording the user can paste into a coding-agent prompt.
Route the evidence
Choose the strongest available input. Combine routes when the user supplies more than one.
- Plain-language description — extract behavior before guessing from appearance.
- Screenshot or mockup — read visual intake; use it to separate observed geometry from behavior that an image cannot prove.
- Live page or user-supplied URL — inspect read-only with the active browser tool. If using agent-browser, load its current core instructions first, then inspect the accessibility tree, visible state, and relevant DOM without submitting forms or changing data.
- DOM, code, or accessibility clues — inspect native elements, roles, ARIA relationships, event behavior, and library component names. Treat them as evidence, not truth: implementations can be mislabeled.
Use component families when two or more nearby patterns could fit; use it to identify the behavior that separates them. Use research and sources whenever links need live discovery or verification.
Complete when: observed facts and inferred behavior are clearly separated, and the evidence is strong enough to form candidates or is explicitly marked insufficient.