bitsocialnet/inspect-elements

Inspect Elements

Use this skill to jump from a concrete DOM node in the running Bitsocial Web app to the React file and component stack that produced it.

Prerequisites

• Dev server running at http://bitsocial.localhost:1355
• playwright-cli installed
• Use the local dev app, not production. The element-source helpers are exposed only in dev mode.

Quick Workflow

1. Open the target route with playwright-cli.
2. Run playwright-cli snapshot and choose the relevant element ref.
3. Resolve that ref through the app helper:

playwright-cli -s=inspect eval "async el => JSON.stringify(await window.__ELEMENT_SOURCE__.resolve(el))" e7

The result includes:

• source: the most useful file and line match for the element
• componentName: the nearest meaningful React component
• stack: ownership stack from the concrete node upward
• tagName: the underlying DOM tag

Session Setup

playwright-cli -s=inspect open http://bitsocial.localhost:1355
playwright-cli -s=inspect goto http://bitsocial.localhost:1355/
playwright-cli -s=inspect eval "window.__ELEMENT_SOURCE__?.ready ?? false"
playwright-cli -s=inspect snapshot

If ready is false, wait a moment and evaluate again. If window.__ELEMENT_SOURCE__?.error is set, report that error instead of continuing.

Resolve Strategies

Prefer snapshot refs because they target the exact live DOM node you just inspected.

Snapshot Ref

playwright-cli -s=inspect eval "async el => JSON.stringify(await window.__ELEMENT_SOURCE__.resolve(el))" e7

Selector

Use this only when the element is easy to target and a snapshot ref is not practical.

playwright-cli -s=inspect eval "JSON.stringify(await window.__ELEMENT_SOURCE__.resolveBySelector('[data-testid=\"hero-cta\"]'))"

Screen Coordinates

Useful when you have a screenshot or a visually obvious hotspot.

playwright-cli -s=inspect eval "JSON.stringify(await window.__ELEMENT_SOURCE__.resolveAtPoint(320, 420))"

Format the Ownership Stack

playwright-cli -s=inspect eval "async el => { const info = await window.__ELEMENT_SOURCE__.resolve(el); return JSON.stringify({ ...info, formattedStack: window.__ELEMENT_SOURCE__.formatStack(info.stack, 5) }); }" e7

Use formattedStack when you need a short, readable trace for the final report.

Profiling Follow-up

When $profile-browsing reports a hot route or rerender-heavy area:

1. Reopen the route in a fresh playwright session.
2. Snapshot the concrete card, section, button, modal, or navigation element that looks relevant.
3. Resolve it with window.__ELEMENT_SOURCE__.resolve(...).
4. Use source.filePath as the direct edit target and stack to understand parent ownership.

This complements react-scan. react-scan tells you which components rerender too often. inspect-elements tells you which exact source file produced the node you are looking at.

Rules

• Prefer snapshot refs over brittle selectors.
• Inspect the actual node the user cares about, not a distant wrapper, unless wrappers are the suspected problem.
• If source is null but stack exists, use the first useful stack frame rather than guessing.
• If both source and stack are empty, report that the node could not be resolved and pick a nearby parent element instead.