Posts tagged “markdown”

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.