Review the result. Let AI keep editing.
Whether it is a fresh demo or an HTML page you are about to share, stop going back to chat to explain “this part.” Point at the exact element, leave a note, and Amarker carries its selector, location, and original HTML back into Claude Code, Cursor, or your AI coding tool.
Built from the review of a real static HTML prototype — read how it started
Once the page is visible, tell AI what to change on the result itself.
Demos, shared HTML pages, and interactive prototypes work the same way: point at a rendered button, heading, card, or form and keep the request with its DOM context.
says nothing
spacing
need this?
Turn visual feedback into change context AI can locate.
Every note binds to a real DOM element. Review it yourself or share the page with someone else—their feedback comes back with the context intact.
Point, don't describe
Every note binds to a real DOM element, capturing its selector, visible text, and surrounding structure.
Never leave the page
Write notes right where you are. Mark up a dozen things in one pass without switching tools.
Give AI executable context
Notes become Markdown with selectors and source HTML, so your AI can locate the change directly.
AI makes a version. You annotate a round. AI makes the next one.
The iteration loop for demos and shared HTML pages, in three steps.
Open the demo or shared page
Let AI build the first version, then launch "Page notes" from the side panel.
Pick an element and comment
Hover to highlight, click to capture. Buttons, headings, cards, and form fields all resolve cleanly.
Send it back to AI
Paste the structured notes into Claude Code, Cursor, or whichever assistant creates the next version.
The next version needs no re-explaining.
Point at what should change and send it back with the exact HTML context.