Kabir Salunkhe's profile on Product Hunt

About

I design, build and ship AI powered product experiences. As Lead UX UI Designer at CambrianEdge.ai, I work at the intersection of UX, frontend and AI, turning complex systems into intuitive, production ready interfaces. I go beyond design and ship code using AI native tools like Cursor and Claude, closing the gap between idea and execution. My work focuses on simplifying AI workflows, building scalable design systems, and crafting fast, accessible interfaces. I collaborate closely with engineers and ML teams to deliver real features. Previously, I spent 3 plus years working with global startups and enterprises, learning to navigate ambiguity and deliver meaningful outcomes. I believe the future belongs to designers who can execute.

Links

Twitter

Badges

Tastemaker

Tastemaker 10

Tastemaker 5

Gone streaking 10

View all badges

Forums

p/runevr

•

13d ago

👨‍💻 Building solo or with a team?

I m curious how other makers prefer to build.

There are obvious advantages to both.

Building solo can mean faster decisions, complete ownership, and no need to constantly align with someone else.

With a team, you get different perspectives, more skills, and someone to share the ups and downs with.

p/aisa-ai-skills-test-ai-leaderboard

•

16d ago

What is BAD vs. GOOD AI judgement?

Would love to hear thoughts.
Here's my perspective.
I'm against AI slop, but I'm not against AI. I believe AI is a great tool but it also needs greats pilots to use it well. This is what I'm working on. AI Fluency.

Biggest marker of AI fluency is AI judgement. Where and when to use AI and where and when not to.

BAD AI JUDGEMENT

p/runevr

•

16d ago

🗂️ Do users really want an all-in-one product?

We often hear that users want fewer tools, fewer tabs, and everything in one place.
But does that really mean they want an all-in-one product?

There s an interesting trade-off between all-in-one and best-in-class.

There s probably a line where an all-in-one product becomes too complicated.

Adding more features can mean fewer tools, less context switching, and a more connected workflow.