BigmintsPoint to the change. Keep the idea moving.
Good feedback starts with a shared view. Starcraft keeps the working preview beside the conversation, so a design decision can refer to the exact thing that needs to change.
StarcraftFeedback that stays attached to the work.
- 01See it
- 02Point to it
- 03Review it
When words lose the detail
Describing a visual change in chat can take more effort than spotting it. Which heading? Which gap? Which version of the page? A screenshot helps, but a detached image still leaves someone to find the element and understand the surrounding design.
Starcraft is our macOS-first design workspace for bringing that context together. A local project, its working preview and an AI conversation share one place to review and refine the experience.
Make the reference part of the request
A designer can navigate the preview, select an element and leave a numbered comment. Annotations can be edited and reordered before sending. Viewport and element screenshots provide visual context, and attachments remain visible and removable in the conversation.
That makes a request such as tightening a navigation bar concrete: the selected element and the comment travel together. The next review happens against the working preview, so the designer can judge the result in context and continue from there. Supported Figma connections can bring selected design context into the same conversation.
A shorter distance from intent to review
The useful change is in the feedback loop. Instead of repeatedly describing where to look, the designer can point, explain and review. The conversation carries visual references alongside the words.
Starcraft keeps project sessions and annotations so work can be picked up again. Explicit preview controls and permission requests keep the person involved as changes are made. The designer can return to the work with its conversation and visual references together.