---
title: "Comment by Virse on \"How to Write Perfect Prompts for Flux Kontext\" | Hashnode"
description: "Helpful Kontext prompting patterns — especially the 'change X while keeping Y' edit style. We keep prompt recipes next to assets in Virse ( https://www.virse.ai"
url: "https://hashnode.com/posts/how-to-write-perfect-prompts-for-flux-kontext/687767d4fa441713fd1aafbe/comment/6ae8fbf34f9101c357146649"
---

[Discussion](https://hashnode.com/posts/how-to-write-perfect-prompts-for-flux-kontext/687767d4fa441713fd1aafbe)

Comment [How to Write Perfect Prompts for Flux Kontext](https://hashnode.com/posts/how-to-write-perfect-prompts-for-flux-kontext/687767d4fa441713fd1aafbe)

[Virse](https://hashnode.com/@virseai)

[Nov 2](https://hashnode.com/posts/how-to-write-perfect-prompts-for-flux-kontext/687767d4fa441713fd1aafbe/comment/6ae8fbf34f9101c357146649)

Helpful Kontext prompting patterns — especially the 'change X while keeping Y' edit style. We keep prompt recipes next to assets in Virse ([https://www.virse.ai/](https://www.virse.ai/)) so the same edit language survives handoff. Do you recommend different prompt length for Kontext vs plain FLUX Dev?