Posts tagged “workflow”

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

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 step-by-step accessibility pass that ends in a shareable doc: capture the problem screen, name the WCAG issue, point at the spot, and publish.

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 step-by-step procedure for reviewing a staging build and sending issues someone (or an agent) can fix without a follow-up call.

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.

Capture once, share twice. Walk through the exact steps to send a client the polished review link while your developer gets the same notes as markdown.

Walk through a design review from opening a browser tab to sending a public link. Each step has a clear outcome the team can act on.

Walk the build, narrate what you see, publish a link. A step-by-step workflow for sending a distributed team feedback that stands on its own without a call.

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.

Vibecoding stalls when the loop between seeing a problem and telling the agent about it is sloppy. Here is what breaks and how to fix it.

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.

Walk a signup flow as a first-time user, capture each friction point in order, and hand the team a review link they can act on the same day.

Walk through a competitor's signup, pricing, and core flow in one sitting, capture each screen with commentary, and hand the team a single link they can open.

A procedural walkthrough: capture the screen, write the comment, pin the spot, export markdown, and hand your agent a prompt it can actually execute.

Coding agents cannot watch your Loom. They need text with structure. Here is why video breaks the handoff and what actually lands as actionable input.

A practical walkthrough for reviewing the built product against the design: cropped stills, spoken comments, numbered pins, and a shareable link the team can act on.

A concrete pre-launch staging review walkthrough: what to check, how to capture it, and how to hand it off so the fixes actually ship before go-live.

Loom is great for talking heads and walkthroughs. For most feedback, a video forces the receiver to scrub, transcribe, and guess what to fix.