Just think for a sec.
You've told different chat agents your role, your tech stack, your client preferences, your project constraints - hundreds of times across hundreds of conversations.

But where does all that live?

Scattered across chat histories. Fragmented across different platforms. Sometimes contradictory, & mostly out of date.

The problem is: ' .

Hi Product Hunt community, I m Artin, founder of SUN.

Ask me anything about how we got into a16z Speedrun, the product, fundraising, team building, or our Product Hunt launch.

Happy to chat and share what s worked (and what didn t).

You can call me JD, I ve spent the past several years building businesses in a few very different worlds: hospitality with Montrose Inn, consulting through ProLine, and now product-building with Provoke.

I wouldn t say I have it all figured out I just really enjoy building things, learning fast, and trying to create products and experiences that genuinely help people. Some of that has looked like running businesses in the real world, some of it has looked like solving messy problems for other companies, and some of it now looks like building new tools from scratch.

I wanted to share a couple of screen shots of creating post with the prompts, single post, multiple post and scheduling.

I ve been spending more time vibe coding recently, and I ve started to question something I initially took for granted. Most of the conversation around vibe coding is about speed. Like how quickly you can go from idea to prototype, or how fast you can iterate. And to be fair, that part is real. The barrier to building has clearly dropped.

But the more I use these tools, the more it feels like speed isn t the limiting factor anymore.

The real constraint seems to be taste.

• what do you choose to build?

• what do you keep vs discard?

• what actually feels right vs just working ?

• what is genuinely useful vs just impressive in a demo?