Website feedback to Markdown prompt
Copy the context. Paste the prompt. Keep moving.
Rochel turns selected website annotations into a structured Markdown file with the page, element, selector and viewport details your coding agent needs to find every requested change.
Interactive product demo
See the brief appear
Annotate the selected element, tick the sidebar card and press Export. The preview shows the technical context that travels with your request.
Make space
for the work.
One deliberately imperfect product page.
Click the blue-selected element
1 · Select
Select the useful notes
Review one page or several sources, then choose exactly which annotations belong in the next implementation pass.
Export technical context
The Markdown includes URLs, selectors, elements, rectangles, viewports and relevant HTML alongside the requested outcome.
Copy → paste → done
Your agent sees where each change belongs. You do not have to say ‘top-right beside X’ or manually map text A to text B.
Also in the extension
Numbers make a brief hard to misread.
A measured detail travels better than an impression. Inspect the page with Alt+C first, then write the annotation with the real value in it. The export carries your words verbatim, so being precise here is what pays off there.
AltCopens one control on the page · Escape stops inspecting
X-ray
Outlines every element boundary in place, so you can see the boxes a layout actually draws.
Text inspector
Hover any text to read its real size, line height, weight, family and colour.
Rulers & guides
Drag snapping guides in from the top or left edge to check spacing and alignment.
Frequently asked questions
How does Rochel build a coding-agent prompt?
What does a Rochel Markdown export contain?
It contains the requested changes plus source, page, element, selector, position, viewport and relevant HTML context for each selected annotation.
Can I paste the export directly into a coding agent?
Yes. The exported Markdown is structured as an implementation brief, so you can copy it and paste it directly into your coding workflow.
Does Rochel upload the exported prompt?
No. Rochel generates the Markdown locally in your browser. Copying or downloading it happens only when you choose to do so.
Is the export a proprietary Rochel format?
No. It is an ordinary, readable .md file. You can inspect it, edit it, keep it with a project, paste it anywhere or stop using Rochel without migrating data.
Does my coding agent need a Rochel integration?
No. The agent only receives concise Markdown and standard browser context. There is no MCP server, account handshake, SDK or agent-specific plugin to maintain.
What happens when source-code resolution is unavailable?
Nothing breaks. Rochel simply exports the same structural DOM context it can capture everywhere. Optional component and file hints enrich that baseline only when development metadata makes them reliable.
Does inspecting a page create annotations or exports?
No. X-ray, the text inspector and the rulers only change what you see. Nothing is captured, stored or added to a brief until you annotate. Use them to find the exact value, then put that value in the annotation your agent will read.
