Design reviews
Review the design as it’s built, on staging or production. Skyelight turns a design review into a list of threads, each pinned to an element and settled in its replies.
The problem
Things drift between the mockup and the build. Spacing is a little off. A hover state is missing. The font weight is wrong on mobile. The empty state never got designed.
Catching this is tedious. You open the build, take screenshots, mark them up, paste them somewhere and try to explain which pixel you mean. The engineer replies with a question. You reply with another screenshot. The exchange can take days over a 4px margin.
The reviews that matter most, where a stakeholder says “this doesn’t feel like us,” often happen in a meeting and are never written down.
Where Skyelight fits
Open the real build, on staging or production, and pin threads on it. Click the card with the wrong padding. Click the heading with the wrong weight. Each thread records the page, the element and its page context, including the styles that apply to it.
Designers point at the element they mean, so there are no screenshots to mark up and no “third button from the left.” Engineers open the thread and see the element in question.
A review flow
- Walk the build page by page. Pin every gap between the design and what shipped.
- Set each thread’s type. A bug means “this is wrong.” An idea means “this could be better.” Keeping them apart stops polish requests from blocking a launch.
- Assign each thread to the person who owns it. They’re notified the same way as for any assignment.
- Settle questions in the thread. The decision is written down in the replies, next to the element it’s about.
- When the fix ships, check it on the page and mark the thread resolved.
Turn decisions into rules
The same notes come up review after review: “Sentence case on buttons.” “Don’t flag contrast on the brand gray, it’s approved.”
Workspace owners and admins can save these as rules on the project, through a coding agent connected over MCP. Rules are stored in the project’s context. Skyelight’s classifier reads that context, and agents read the rules through the decision log, so a rule saved once applies to later threads.