Engineering teams
Engineers need feedback they can act on without a follow-up meeting. Skyelight connects each thread to the page and element it’s about, and with Skyelight Build, to the code that rendered it.
The problem
A vague ticket can cost more than a hard bug. “The pricing section looks broken” means opening the site, finding the section, guessing at the browser, pinging the reporter and waiting.
Even a good report is disconnected from the code. You know the problem is on the pricing page. You still have to find the component and the file, and check whether anyone else has reported it before you touch it.
When you fix it, telling the reporter is another task, so it often doesn’t happen.
Where Skyelight fits
Every Skyelight thread comes with the page URL, the element anchor and the page context captured when it was pinned. Engineers can read what the reporter saw without reproducing it first.
Skyelight Build adds more. The build plugin stamps each element with the source file, line and commit that rendered it, so a thread on a stamped element points to the code, such as PricingTable.tsx, line 42.
Let a coding agent work the queue
The Skyelight MCP server gives coding agents access to your threads. An agent can:
- List open threads, filtered by page, type, status or assignee.
- Read a full thread, including the replies, the element anchor, the screenshot and attached images.
- Find the code through the source file and line stamped by Skyelight Build.
- Make the change in your repository.
- Reply on the thread with what changed and a link to the pull request.
- Resolve the thread once the fix is in.
An agent can also read your project’s saved rules through the decision log, so team decisions such as “don’t flag contrast on the brand gray” inform its work.
Good to know: Agents post updates as replies on the original thread. The person who reported the issue sees the fix on the thread they started.