@tomkrcha — Design Mode for Cursor
Introducing Design Mode for Cursor! 🧑🎨🤖
Vibe code and vibe design in one place, stay in the flow. Uses the same existing AI agent that's in your favorite coding tool, same context, intertwined.
That's interesting because the design loop and the code loop have always been separate tabs, separate tools, separate context windows. Collapsing them into one agent with shared context is a bet that the friction isn't in switching apps — it's in the agent not knowing what the design looks like when it's writing markup.
@victorialslocum — MCP and function calling are complementary, not competing
MCP and Function Calling solve different problems.
One tells WHAT tool to use, the other standardizes HOW tools connect.
They're complementary technologies, not rivals.
Function Calling's core purpose: [...]
Smart take. The "MCP vs function calling" framing keeps popping up and it's a false dichotomy — function calling is how a model decides to invoke a tool at runtime, MCP is the protocol that describes and exposes the tool in the first place. One is LLM inference behavior, the other is a transport/discovery layer.
@tom_doerr — How Windsurf's agent actually operates
This is how Windsurf's agent operates. Interestingly, it writes prompts to edit files.
Honestly, this is the most revealing thing I've seen about how coding agents work internally. Instead of calling a structured file-edit API, it generates a natural language prompt to itself as an intermediate step. That's either a sign of flexible architecture or a hint that the underlying abstraction leaks everywhere.
@tiptap_editor — Tiptap 3.0 Beta is live
Tiptap 3.0 Beta is live! It's faster, simpler, and built for dev experience. Check the docs, test it out, and let us know your thoughts:
What's new docs: https://next.tiptap.dev/docs/resources/whats-new GitHub: https://github.com/ueberdosis/tiptap/tree/next
Thanks to ProseMirror for their amazing open-source work!
Tiptap is the editor framework I reach for when I need a rich text editor that doesn't make me fight the DOM. The jump to 3.0 is worth tracking — the "simpler" claim is the one I'd test first, because 2.x had some real setup overhead for extensions. Bookmarked to actually migrate something against it.
@benln — YC's notes on getting the most out of vibe coding
Notes from @ycombinator on how to get the most out of vibe coding: [link]
5,692 bookmarks on this one. That's a signal. YC writing docs on how to actually use AI coding tools effectively — not just "use AI" but specific workflow notes — is worth reading before you form strong opinions about what works. Saving this for the next time someone asks me how I set up Claude.
