Pins & threads
A pin is a single comment anchored to a DOM element on a page. It is the core object in Skyelight: the thing you create, reply to, classify, assign, and resolve.
Anchoring
When you create a pin, Skyelight records which element you clicked and where on that element the pin sits. It stores enough about the element (its position in the page and the markup around it) to find the same spot again on the next visit. You can also select text first and pin the selection directly.
This is what separates a pin from a screenshot. The comment travels with the element. If the page reflows or someone opens it at a different screen size, the pin still points at the right thing instead of floating over empty space.
Anchoring is resilient, not magic. If an element is removed or rebuilt entirely, its pin can come loose. When that happens the pin is kept with the surface so the thread is never lost. It just needs re-placing.
Threads, mentions, and reactions
Every pin is a thread. The first comment opens it; replies stack underneath. Only the parent pin shows a marker on the page, so a busy thread never clutters the view. Because the thread is attached to the element, context never gets lost in a chat channel. Anyone who opens the pin sees the full history right where the discussion happened.
- @mention a teammate to pull them in. They are notified even if they have not opened the thread.
- React with an emoji to acknowledge or vote without adding noise.
- Reply to keep the conversation going; everyone on the thread is notified.
See Notifications for exactly who gets pinged and how to tune it.
Automatic classification
Shortly after a pin is created, a classifier reads its text and assigns a type:
- Feedback: a reaction or critique about something that exists.
- Idea: a suggestion for something new.
- Bug: a report that something is broken.
These three are the defaults; you can add your own types in workspace settings. The classifier infers context from the comment and the element it is attached to, and it learns from how your team labels things, so the more you correct it, the closer it lands. You can give it standing guidance in your workspace and project settings, and you can always change a pin’s type by hand with the type chip on any pin.
Classification runs once per pin, a moment after it is posted. Editing a pin or adding replies later will not reshuffle a type you have already set by hand.
Statuses
Pins carry a simple status you control as you work them:
| Status | Meaning |
|---|---|
| Open | Still live, not yet handled |
| Resolved | Done, kept on the surface for reference |
Resolving a thread (or reopening it) posts to the thread and notifies the people involved, so the history of how a piece of feedback was handled stays attached to it. To move work to a specific person, assign the pin to a teammate; it then shows up in their Assigned to me inbox in the dashboard.
Across a whole project, Skyelight also rolls pins up into decisions on the project synthesis dashboard, so you can see what has actually been settled. See the Dashboard for that view.