Posts tagged “workflow”

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

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.

A step-by-step workflow for pulling key moments from recorded interviews into a single research review, then sharing one link the whole team can read.

You send a review tool to a client or stakeholder and it dies at the install screen. Here is why external reviewers refuse to set up an account, and how to route around it.

A three-part item structure for product reviews that a busy PM can read and act on in two minutes: one screenshot, one observation, one suggested next step.

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.

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.

Assemble captured screens from session replays plus spoken observations into a single review, then send your PM one link they can read, resolve, and export.

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.

A pinned screenshot and one dictated sentence beat a paragraph of description when you prompt Windsurf. Here is the step-by-step flow.

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.

A step-by-step walkthrough of publishing a review, collecting comments, and marking each one resolved, covering the lightweight tracking most people reach for a bug tracker to do.

The analytics page on a published review shows visit counts and visitor geography. Here is how to read those numbers before a launch, and what they can and cannot tell you.

Typing slows a review pass to a crawl and strips out context. Talking through each captured screen keeps you moving and preserves the why behind every note.

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.

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.