Skyelight Build
@skyelight/build is a plugin for your app’s build. It adds source locations
to the elements on your preview builds and puts the review badge on those
pages. Developers install it once, and every thread pinned on a stamped page
records the code behind the element.
The plugin does two separate jobs, and you can turn each one on or off:
- It adds stamps to each element: the source file and line that wrote it and the component it belongs to. The page also records the commit and branch it was built from.
- It adds the review badge script to your preview builds. Clients and reviewers use the badge to pin threads on the page without the Chrome extension.
What an agent gets
Without stamps, an agent reading a thread gets a URL and a CSS selector, and has to search your repository for the element. With stamps, the thread carries the file, line, component, commit and branch:
The file and line tell the agent where to look. The commit and branch tell it
which branch to open and whether the code has changed since the thread was
left. Over MCP, get_item returns this source
location with the thread.
How it behaves
- Setup turns on stamps and the badge for preview and local builds, and keeps production builds free of anything from Skyelight. See Options and environments.
- The plugin needs no key, token or project ID. The preview address you add to your project in Skyelight connects the site to that project.
- The plugin runs at build time and makes no network calls. It adds attributes and a script tag to your pages and sends none of your code anywhere.
- If a file doesn’t parse, or the transform fails for any other reason, the plugin returns the original source and the build continues.
The plugin supports Next.js, Vite, Remix, Astro and WXT. It is proprietary software, licensed for use with Skyelight under the Terms of Service.
A coding agent reads stamps through Skyelight MCP, so stamps are most useful when your team uses an agent. The review badge works without MCP.