Hey everyone, Wanted to share a huge frustration I’ve been having while building with Claude Code/Desktop, and a solution I’ve been messing around with for the past few weeks. Whenever I try to pass a complex feature or an entire architecture workflow from my head to the AI, I always hit a wall. Translating logic, data flows, and layout components into a single text prompt just feels broken. It takes forever to type, ends up being a super unorganized wall of text, and Claude often gets confused or misinterprets things, which leads to annoying hallucinations. Basically, the “text bottleneck” is killing my velocity. So I thought: Why are we still using text prompts for visual architecture? Why not use a component-based, visual approach? I ended up building a simple web tool to scratch my own itch. It lets you map out your system design and logic using visual components. As you build and drag things around visually, a clean, structured specification (the actual PRD and architecture breakdown) updates automatically in the background. To make it actually useful for coding, I integrated the Model Context Protocol (MCP) . This way, you can pull this visual specification directly into Claude Code or Cursor, giving the AI a rock-solid, structured source of truth to build from. I originally just made this for fun and for my own projects, and it’s currently live. But before I waste time trying to promote it or add features to a problem that maybe only I have… what do you guys think? Does this sound like a real pain point for you too when dealing with complex prompts? Would you actually use something like this? I didn’t include the link because I don’t want to spam, but if anyone wants to check it out and give some brutal feedback, let me know and I’ll drop it in the comments. Thanks! submitted by /u/Previous-Growth-9919
Originally posted by u/Previous-Growth-9919 on r/ClaudeCode