Jonathan

Been landing up in contextual limbo when I multi-task too aggressively. Managing context requires a lot of intention to keep up.

I’ve been using GPT-5 Codex to critique its own outputs with a recursive feedback loop.

With mistle.dev side threads, I run critique → reflection → revision cycles.

It actually works pretty well.

Vibed out a Chrome Extension that helps to write X replies in less than an hour.

The vibing is the easy part.

The hard part is writing the prompts to generate responses that reflects my style and thinking.

Relaunching Zapi as mistle.dev

Mistle is Cursor for non-technical builders.

We built Mistle to help non-technical builders learn, understand, and get better as they build.

We've got a few early users who jumped from Cursor to Mistle.

If you're non-technical, give Mistle a try.

We're launching Zapi as an AI Copilot for Product Teams.
With Zapi - Write and turn PRDs into prototypes in minutes.

How it works:
1. Prompt your idea.
2. Iterate till you get a working PRD
3. Zapi builds a hi-fi prototype according to your specs
4. Publish and share with your team

It feels like the DaisyUI 5 is closer in style to ShadCN and tailwind UI components. For people coming from ShadCN, DaisyUI5 probably looks better.

Before building an app, it's important to determine an initial direction and requirement.

But writing a doc is boring and time-consuming. So we built Zapi to one-shot a comprehensive product requirements document (PRD).

UX often breaks not because it was bad but because the product grew.

Zapi started with 1 view mode. As we added more, we used a dropdown.

It worked until it didn’t.

Now with 7 modes, we moved to a sidebar for clarity.

UX isn’t set and forget. Revisit what used to work.

Curious - what worked previously? What was the hypothesis?

We're looking for beta testers!

Zapi turns your ideas into a specifications doc and then follows the plan to build your idea.

As a beta tester, you get 100 free messages.

Join in 2 easy steps:
1. Join our discord: discord.com/invite/2RQ2g...
2. Post in #general channel with your Zapi user id

Thanks. I agree, I’m a big fan of keyboard vi-style. I think it makes sense that at some point, power users have an alternative to get to areas quickly.

I’m relieved to hear that. 😅
The top version is what we are iterating towards. More explicit and clearer in terms of design.

Tackling usability issues with navigation.

Which is more UX friendly?

Top version - collapsible sidebar menu
Bottom version - dropdown menu

#buildinpublic

Made improvements to the UX selection around agent outputs in a chat interface.

How does this look?

Through talking to users, it became clear that a chat interface doesn’t make site-building intuitive for non-technical folks.

Dev terms aren't part of a layperson's vocab. That’s why we're releasing Specifications Mode, where a PM agent translates your ideas into specs.

Just released Secrets Management in Zapi:

- Build integrations safely without exposing sensitive configurations to AI or in the codebase
- Use a separate set of secrets for preview vs live environments

Got it. Thanks for sharing!

Every now and then, I switch between calendar apps just to jolt my life a bit. Just recently switched to Notion Cal from Google Cal from Apple Cal. Pretty sure I’ll switch back to Apple Cal when the next iOS is out.

The future will be AI vs AI. 😅

Any details on how one can get verified?

Every single day is not the same. It's always a different problem to solve and that's what keeps things fun and engaging.

With that said, this assumes that one's basic needs are met, whether it's through a job that pays, other projects or with external funding.

A changelog is a great forcing function to stay accountable.

Each week at Zapi (heyzapi.com), we:
1️⃣ Prioritize changes that move the needle
2️⃣ Build
3️⃣ Publish updates

If we didn't make a good update or missed one - we reflect and do better.

What's your forcing function?

Love @posthog.com as a brand and product. These days, it is so rare to see truth in advertising.

The only time a prompt worked was when I copied out the specific doc snippets and provided a small set of precise instructions.

Have you experienced the vibe coding death loop?

Vibe coding sucks for implementing editors.

We used MDXEditor which is built on top of CodeMirror, Lexical and MDAST.

Cursor Agent tried implementing it and went into a death loop trying to fix its own implementation over and over again. Gemini Pro did no better.

Shipped a markdown editor in Zapi. No more prompting to edit content.

Seems like LLMs also suffer from the Justin Case syndrome when left to their own devices. iykyk

Got it. Thanks!

Wow! Super blown away by animejs docs. Using animation as nav is so intuitive and so good!

100% will always review it. Not for security reasons though. Just have to make sure the backend logic works.