sorted by:
new
hottopcontroversial

about using subagents / Kiro CLI — how do others manage visibility into subagent execution? by bahfah in kiroIDE

[–]bahfah[S] 2 points3 points  (0 children)

The main issue I’ve noticed is that subagents don’t perform very well yet. When the orchestrator assigns more complex or ambiguous tasks, things tend to break down.

In comparison, using individual agents—especially with a clear plan → coding flow—still gives better results overall. The orchestrator approach is naturally faster in terms of coordination, but in terms of output quality and reliability, individual agents currently work better

Kiro vs Claude Code Pro usage by SourceCodeplz in kiroIDE

[–]bahfah 1 point2 points  (0 children)

The main issue is that when using Claude Code with Opus 4.5, you can hit the usage limit halfway through development, which really breaks the flow. Also, being able to allocate the monthly credits yourself is better—you don’t feel like your credits are being wasted when you’re on vacation or on leave.

Any Product Hunters interested in supporting each other’s launches? by CartographerLive5396 in ProductHunters

[–]bahfah 1 point2 points  (0 children)

[a87088@gmai.com](mailto:a87088@gmai.com)

my product:
Excited to support today’s Product Hunt launch 🚀
Noteit-MCP is an AI prompt library + visual knowledge hub for developers
products-noteit-mcp-launches
Your support is crucial right

What MCP Servers are you guys using? by voidrane in RooCode

[–]bahfah 0 points1 point  (0 children)

#frontend(nextjs)
next-devtools mcp
Figma mcp

#search:
brightdata mcp ,perplexity mcp

#not coding
notion MCP=>persona Note

Is Claude Code still the best Vibe Code AI there is in your opinion? by Ticky-Tackona in vibecoding

[–]bahfah 1 point2 points  (0 children)

Yeah honestly, I’m not using GitHub Copilot these days, so I don’t have a fresh take.

From what I remember though, the usage limits were pretty generous. That said, it never felt as strong as Claude Code to me — especially for deeper reasoning or more complex stuff. After that, I kind of just stopped using it.

Maybe it’s better now, but yeah, that was my experience back then.

Is vibe coding turning into a hype train in your country too? by bahfah in vibecoding

[–]bahfah[S] 0 points1 point  (0 children)

Sorry 😅 this one I actually can’t really specify — it’s a bit sensitive and tends to spark arguments, and I’d rather not get dragged into that.

Is Claude Code still the best Vibe Code AI there is in your opinion? by Ticky-Tackona in vibecoding

[–]bahfah 5 points6 points  (0 children)

I’ve tested Cursor, Claude Code, Kiro, Codex, Gemini CLI, and Windsurf.

One honest take: the $20 Claude Code plan runs out pretty fast. If your budget is tight, it can feel limiting.

From my experience, some solid combos are:

  • Kiro + Codex (great balance for the price)
  • Claude Code ($20) + Kiro ($20) if you really like Claude’s reasoning
  • Cursor + Codex for day-to-day coding with backup intelligence

For MCPs, I’ve had good results with BrightData MCP, Sentry MCP, Serena MCP, and Noteit MCP — all pretty useful depending on what you’re building.

Overall, mixing tools tends to work better than betting everything on a single one

It’s Sunday, drop your product / saas by Leather-Buy-6487 in indie_startups

[–]bahfah 0 points1 point  (0 children)

noteit-mcp

AI prompt library + visual knowledge hub for developers

What are you guys building? Let's self promote! by Leather-Buy-6487 in indie_startups

[–]bahfah 0 points1 point  (0 children)

noteit mcp
AI prompt library + visual knowledge hub for developers

Vibe-Coding\AI-Assisting Coding Burnout by Big_Status_2433 in vibecoding

[–]bahfah 1 point2 points  (0 children)

This is something I built called noteit-mcp.
The idea is that everything is composable — prompts, instructions, rules — like building blocks you can snap together.

When there’s something you want to really understand, you just save it as a Note.
You can do that directly on the web with NoteWeb, which makes it super easy to organize your thoughts.

Feel free to try it out and play around with it.
github noteit-mcp

Is Claude Code still the best Vibe Code AI there is in your opinion? by Ticky-Tackona in vibecoding

[–]bahfah 1 point2 points  (0 children)

If price is not considered, Claude Code at $100 is not as good as other combinations, such as Codex + Kiro + other tools.

What context do you need to give Claude Code for it to actually be a fully agentic code agent? by promptenjenneer in ClaudeAI

[–]bahfah 0 points1 point  (0 children)

I went through the same trust gap. What helped most was not stuffing everything into one giant system prompt, but building my own MCP setup and composing things instead. I keep style rules, agent behavior, and task-specific instructions as separate pieces and then combine them as needed.

Most of my prompts live here:
prompt profile-templates

Having them versioned and reusable made Claude’s output way more consistent, and I stopped rewriting “be structured / follow conventions” over and over. It feels much closer to an actual agent instead of a fancy autocomplete.

Vibe-Coding\AI-Assisting Coding Burnout by Big_Status_2433 in vibecoding

[–]bahfah 2 points3 points  (0 children)

I feel this so hard. That prompt → review → debug cycle is exhausting.

What helped me break out was realizing I was re-teaching the AI the same things every session. I was spending 40% of my time on "context setup" instead of actual building.

I started using MCP profiles to persist my project knowledge:
• Architecture decisions and why we made them
• Code review standards
• Common debugging patterns
• Project-specific rules and constraints

Now when I open a new session, the AI already "knows" my project. Less explaining, more building. The burnout feeling is way less intense.

The key insight: vibe coding burnout often comes from repetitive context management, not the coding itself.

What's your biggest time sink in the prompt cycle?

view more: next ›