Vibe Coding Forem

Cover image for I Vibe-Coded a "Cursor for Writers" on a $7 budget (Because Chat kills the flow)
Ricky FF
Ricky FF

Posted on

I Vibe-Coded a "Cursor for Writers" on a $7 budget (Because Chat kills the flow)

We talk a lot about "Vibe Coding"—using AI to stay in the flow state while building apps.

But what about "Vibe Writing"?

Every time I try to write a novel with ChatGPT, the vibe dies instantly.

I have to stop writing.

I have to explain the plot again.

I have to copy-paste text.

The Flow is gone.
Enter fullscreen mode Exit fullscreen mode

I’m 16. I don't have VC money. But I have $7 and some Supabase/Groq credits. So I built Minotauris.

It’s an Agentic IDE for fiction.
⚡ The Vibe Check (How it works)

Instead of chatting, you Command.

Stay in the Editor: You never leave the writing interface.

Async Agents: You type /refactor chapter 4 for pacing, and the agent runs in the background. It reads your Lore, checks your tone, and edits the text while you keep writing Chapter 5.

No Context Amnesia: I indexed the "Story Bible" so the AI actually remembers the villain's motivation from 20 chapters ago.
Enter fullscreen mode Exit fullscreen mode

🛠️ The "Broke" Stack

I vibe-coded the whole thing in 2 weeks:

Brain: deepseek-r1 (via Groq) for the hard logic.

Speed: llama-3-8b (via Groq) for the fast drafts.

Routing: Supabase Edge Functions (to throttle heavy users so I don't go bankrupt).
Enter fullscreen mode Exit fullscreen mode

I’m looking for people who want to test the "Command Mode" workflow. If you’re tired of the Chat Box killing your creative vibe, let’s talk.

Waitlist / Alpha:
 minotauris

(P.S. If you have any tips on optimizing RAG for 100k+ token stories without melting my credit card, let me know in the comments 👇)

Top comments (0)