WalkMe jQuery Selector Assistant

WalkMe's Deep UI recognises most elements on its own. When it doesn't — iframe-heavy screens like SAP S/4HANA, or checkboxes, where it can't work at all — you have to write a jQuery selector by hand. The hard part isn't producing one that works. It's producing the right one. This adds a panel to Chrome DevTools. Inspect an element, and it gives you ranked selectors, tells you how many elements each one actually matches on the live page, and explains why it picked what it picked. WHAT IT DOES • Ranks candidate selectors by how well they'll hold up, using WalkMe's own cheatsheet rules: a stable ID, then a stable class, then element-plus-attribute, then a wildcard on the steady part of a name, then a path. • Counts matches against the real page. This is the thing a paste-in web tool structurally cannot do. If you asked for one element and the selector hits forty, you find out here rather than in the editor. • Warns about names the page invents as it loads. A class like css-1x7fj3k or Button-a3f9c2d1 will be different after the next release, and the panel says so instead of handing you a selector that breaks next week. • Handles the three cases that actually go wrong: matching many when you need one, matching one when you need all forty, and auto-steps, where WalkMe usually needs the element one level up. • Gives you both forms every time — the bare selector for the WalkMe editor, and the wmjQuery("...") form for testing in the console. Mixing those two up is a common trip-up, so they are always shown side by side and labelled. • Reads nested iframes and builds the frame context for you, at any depth. • Includes the WalkMe Player component table, searchable, with your WalkMe ID substituted in before you copy. BUILT TO TEACH Every selector comes with the reasoning in plain English, and a reference panel explains the syntax as you go — what . and # and [ ] mean, and what :first, :eq(n), :contains() and :visible do. You should not have to learn HTML and WalkMe at the same time. PRIVACY No analytics. No tracking. No server. The page you're inspecting never leaves your browser. There is an optional AI feature, off by default, that lets you describe what you want in a sentence instead of picking an option. If you switch it on and supply your own Anthropic API key, that sentence goes to Anthropic's API — nothing else does, and the selector work never involves AI at all. The extension is completely functional with it off, which is how it ships. PERMISSIONS One: "storage", to remember your settings. No host permissions. No content scripts. It cannot touch pages you are not actively inspecting.