Posts tagged “markdown”

A five-step workflow for cropping the exact subcomponent, dictating a single change, and sharing a markdown link v0 can read.

Region, element, and state words that keep their meaning when your feedback reaches Claude Code as markdown. Use these instead of vague pointing.

A step-by-step workflow: capture a screen, say what's wrong, publish, and hand Cursor a markdown URL it can read. All in one browser tab, in under a minute.

You captured a review of a broken screen. Here is how to hand it to Claude Code so each item becomes a discrete task it can work through.

Capture the built screens, comment on each one, publish, and paste the markdown export into Cursor as a task list. Here is the exact order to do it in.

Agent-readable feedback is a defined term. Here is what it means in practice, with a short example of a cropped still and the markdown that comes with it.

Walk through capturing a Lovable preview, pinning the exact spot, and pasting the markdown into the chat so the fix lands on the first try.

An agent will happily edit the wrong element if your markdown bug report is vague. Here are the specific mistakes that cause it and the concrete fix for each.

Aider works from the terminal and reads pasted text well. Here is a small, reusable template that pairs one cropped still with three bullets so the change lands right.

A worked example: the same bug report shown as a published review link for people and as clean markdown for Cline to read and fix.

The Replit Agent built the screen, the preview is broken, and you need to say exactly what and where. Here is the capture-comment-return loop, step by step.

Capture a rendered page, crop the broken region, and feed the markdown to Zed AI. Here is the exact input and the exact result, step by step.

A step-by-step way to send v0 a precise visual fix so it edits the component you already have instead of regenerating the whole screen.

Capture your Bolt preview, mark up what needs fixing, and hand Bolt a single markdown URL it can read. Here is the exact order of steps.

Go from a broken screen to a markdown link Aider can read in about two minutes. Here is the exact sequence, step by step.

Cursor can only act on what you actually tell it. Here are the feedback mistakes that send it guessing, and how to correct each one.

Take one messy note about a checkout bug and rewrite it into structured feedback an LLM can act on. The actual inputs and the actual markdown output, shown in full.

A precise glossary of markdown screenshots: what the term means, what a review item and a numbered pin are, and why agents read the format cleanly.

Vague feedback wastes an agent's time. Here is how to capture a screen, name the problem, and hand over text the agent can turn into a fix.

A short glossary for reviewers whose feedback ends up in an agent's context window. Define the artifact, the pin, the prompt, and what each one changes.

A concrete walkthrough from opening a tab to exporting markdown. No install, no extension, no signup. The output reads cleanly for people and for agents.

Agent feedback is not a vibe or a workflow buzzword. It is a specific artifact with a specific shape. Here is what it contains and why each piece is there.

Open a tab, capture a screen, talk through what you see, publish, and walk away with a markdown file a developer or coding agent can read straight away.

Loom is great for talking through a screen. It is bad for handing work to a coding agent. Here is how a recorded video stacks up against a markdown review on the axes that matter.