Original Summary

I'm a DevSecOps engineer who also does quite a bit of vibe coding. AI makes building incredibly fast, but I've found that architecture can easily become an afterthought. You start prompting for Next.js, Supabase, auth, Stripe, monitoring, AI etc. and suddenly you've created a whole stack without really designing it. So I built BuildBlueprint : https://buildblueprint-sepia.vercel.app/builder You can choose your frontend, backend, database, auth, AI, monitoring, CI/CD, deployment, security and more. The bit I wanted to make different is what happens afterwards. It generates a pack for coding agents with things like AGENTS.md , SECURITY.md , testing guidance and the actual stack definition. There's also in-browser AI , so you can discuss the architecture, question the choices and refine it before handing everything to Claude, Codex, Cursor etc. The workflow I'm aiming for is: idea → design the stack → refine it → give the AI proper context → build rather than: idea → massive prompt → hope the AI makes sensible decisions It's still early and I'd genuinely like developers and vibe coders to pull it apart. What am I missing? What would make you actually use this before starting a project?   submitted by   /u/Stiliajohny [link]   [comments]

  • 情报分类：技术学习与提效
  • 分类依据：内容涉及技术、AI、软件工具或工程实践
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/9/30 22:21:09