---
title: "Sandeep Virk (@sandeepvirk) | Hashnode"
description: "Figma plugins by Crafttor: PSD to Figma, Image to Figma, motion tools. Read the latest articles by Sandeep Virk on Hashnode."
url: "https://hashnode.com/@sandeepvirk"
---

@sandeepvirk

# Sandeep Virk

@sandeepvirk · Joined October 2026

Figma plugins by Crafttor: PSD to Figma, Image to Figma, motion tools.

### [Figma Code Layer Prototype: Build an Interactive Prototype That Runs Real Code, Starting From a Live Site](https://crafttor.hashnode.dev/figma-code-layer-prototype-build-an-interactive-prototype-that-runs-real-code-starting-from-a-live-site?utm_source=hashnode&utm_medium=feed)

Originally published on Crafttor. TL;DR: A Figma code layer prototype runs real HTML, CSS and JavaScript on the canvas, so inputs, toggles and state behave like a product. The fastest start is not a b

8 min read · [crafttor.hashnode.dev](https://crafttor.hashnode.dev/figma-code-layer-prototype-build-an-interactive-prototype-that-runs-real-code-starting-from-a-live-site?utm_source=hashnode&utm_medium=feed)

[14h ago](https://hashnode.com/posts/figma-code-layer-prototype-build-an-interactive-prototype-that-runs-real-code-starting-from-a-live-site/6affec16cf39810fd128383f)

### [Why AI UX Audits Work Better on a Recorded Flow](https://crafttor.hashnode.dev/why-ai-ux-audits-work-better-on-a-recorded-flow?utm_source=hashnode&utm_medium=feed)

Give an AI a recorded flow and it can review feedback, timing, layout shift and dead ends step by step.

4 min read · [crafttor.hashnode.dev](https://crafttor.hashnode.dev/why-ai-ux-audits-work-better-on-a-recorded-flow?utm_source=hashnode&utm_medium=feed)

[2d ago](https://hashnode.com/posts/why-ai-ux-audits-work-better-on-a-recorded-flow/6afd4546d8225d3992592973)

### [Record Flow vs Screen Recording: Why AI Needs Data, Not Video](https://crafttor.hashnode.dev/record-flow-vs-screen-recording-why-ai-needs-data-not-video?utm_source=hashnode&utm_medium=feed)

A screen recording gives an AI pixels. A recorded flow gives it names, boxes, styles and exact timings.

4 min read · [crafttor.hashnode.dev](https://crafttor.hashnode.dev/record-flow-vs-screen-recording-why-ai-needs-data-not-video?utm_source=hashnode&utm_medium=feed)

[2d ago](https://hashnode.com/posts/record-flow-vs-screen-recording-why-ai-needs-data-not-video/6afd44e1aeaa656efc3b4946)

### [Why Product Managers Should Record the Flow Before Writing the Ticket](https://crafttor.hashnode.dev/why-product-managers-should-record-the-flow-before-writing-the-ticket?utm_source=hashnode&utm_medium=feed)

Record the current flow once and get the ticket, acceptance criteria and a reviewable prototype.

4 min read · [crafttor.hashnode.dev](https://crafttor.hashnode.dev/why-product-managers-should-record-the-flow-before-writing-the-ticket?utm_source=hashnode&utm_medium=feed)

[2d ago](https://hashnode.com/posts/why-product-managers-should-record-the-flow-before-writing-the-ticket/6afd44821e8437c11647596e)

### [Why Developers Should Ask for a Recorded Flow, Not a Written Spec](https://crafttor.hashnode.dev/why-developers-should-ask-for-a-recorded-flow-not-a-written-spec?utm_source=hashnode&utm_medium=feed)

Written specs leave out timing and side effects. A recorded flow measures them in the browser.

4 min read · [crafttor.hashnode.dev](https://crafttor.hashnode.dev/why-developers-should-ask-for-a-recorded-flow-not-a-written-spec?utm_source=hashnode&utm_medium=feed)

[2d ago](https://hashnode.com/posts/why-developers-should-ask-for-a-recorded-flow-not-a-written-spec/6afd441dbedd4b1997655793)
