Select
Open your running app through PixelSteer and click the element or region you want to change.
OpenCode visual feedback
Give OpenCode the missing visual context.
Select the exact part of your running interface, say what should change, and let your OpenCode workflow work from concrete browser context.
Visual intent, grounded in code
Point at the interface.
Keep control of the source.
PixelSteer sits in front of your existing dev server and adds a lightweight visual selection layer. Your feedback stays attached to the element, region, page, and styles you were looking at when you wrote it.
OpenCode remains responsible for understanding and editing the repository. PixelSteer makes the request less ambiguous and keeps the browser-to-source feedback loop short.
The PixelSteer loop
Three steps from feedback to frontend.
Describe
Add the result you want. PixelSteer keeps the note attached to the page and visual context.
Review
OpenCode edits the real source. Your existing dev server reloads the result for review.
Install once
Add the PixelSteer skill.
Run the install command from your frontend project, then invoke it in OpenCode.
npx skills add PixelSteer/pixelsteer-skillThen in OpenCodeUse the pixelsteer skill to start the visual feedback session for my frontend. Keep handling browser feedback until I ask you to stop.Open skill instructions Questions
What developers ask.
Does PixelSteer include OpenCode?
No. PixelSteer is the visual feedback layer used alongside your existing OpenCode installation and project.
Does it work with my current frontend dev server?
Yes. PixelSteer proxies the server you already run and preserves the existing HMR workflow.
Stop translating the screen into prose.