Rapid prototyping
Skyelight collects reactions to a prototype as threads on the screens they’re about, so each round of feedback becomes the input for the next version.
The problem
Teams share prototypes constantly: a clickable Figma link, a Vercel preview someone spun up over lunch, a vibe-coded demo built in an afternoon. They get posted in a channel, sent to a client or shown in a meeting.
People react, and the reactions scatter:
- “Love it, but can we see more on the pricing step?” lands in an email.
- “The nav feels heavy” lands in a Slack thread.
- “What happens when there’s no data?” gets said out loud on a call and never written down.
The client wants to go deeper and parts need to be fleshed out. Now you’re building a to-do list from five places, and half of it is your best guess at what someone meant.
Where Skyelight fits
With the Chrome extension, Skyelight needs no code changes or embed. It works on any web page you can open in Chrome, including prototypes you didn’t build and previews that will be gone next week.
People click the part they’re reacting to and write their comment. The thread is pinned to the element, with page context captured at that moment. When the prototype changes tomorrow, you can still see what they were looking at today.
The iteration loop
Each round’s feedback is the input to the next one.
- Share the prototype link. Reviewers open it and start pinning.
- Sort what came in. Check each thread’s type (bug, idea or feedback) and correct it where needed. Defer the “good idea, not now” threads so they stay on the list without blocking the round.
- Connect your coding agent to Skyelight through the MCP server. The agent reads the open threads, with their page context and any screenshots, and works through them one by one.
- When a change lands, the agent replies on the original thread with what changed and a link to the pull request. The person who asked sees the answer on the thread they started.
- Ship the next version. Reviewers come back, check the fixes and pin the next round.
Each round’s threads and replies stay on the project as a record of what changed and why.