Pin, Item, Slug, Resolved: Markdown Bug Report Terms
A developer and an AI coding agent see the same markdown bug report. Here are the four words that keep both on the same page: pin, item, slug, and resolved.
A developer and an AI coding agent see the same markdown bug report. Here are the four words that keep both on the same page: pin, item, slug, and resolved.
Copy this three-part structure into one review: current state, intended state, and constraints. Each part becomes an item an agent can read and act on.
The crop rectangle decides which element an agent touches. Four defensible rules for what to keep, what to cut, and the failure mode when you get it wrong.
Frame, crop, pin, item, review link. Define the words you use to describe a screen so your prompt to an agent or a teammate points at the exact spot you mean.
You captured a bug. Do you send a still frame with notes or a screen recording? Here is how each one lands when an AI coding agent has to act on it.
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.
You built a screen, it is almost right, and you want an agent to finish it. Here is the handoff that gets the agent looking at the same pixels you are.
A procedural walkthrough: capture the screen, write the comment, pin the spot, export markdown, and hand your agent a prompt it can actually execute.
The precise vocabulary for bug reports a coding agent can fix without follow-up questions. Each term defined, with practical notes on when it matters.