Aashi

Aashi

Content @ Clueso Make vids at 10x speed
#101424312 followers15 following
🎉 6 day streak
>10,000All time
2 KP

About

Marketing at Clueso, an AI Content Engine. Give a prompt and Clueso turns it into a stunning video and a step-by-step guide, in minutes. Screen recordings, slide decks and documents work the same way. Every asset stays fully editable afterward.

Badges

Tastemaker
Tastemaker
Gone streaking 10
Gone streaking 10
Gone streaking
Gone streaking
Gone streaking 5
Gone streaking 5

Maker History

  • Clueso
    CluesoCreate stunning product videos in minutes with AI
    • 🎉
    Joined Product HuntAugust 17th, 2026

Forums

•

4d ago

I rewrote a page title for clicks and only later found it was my most AI cited page

Two weeks of Search Console data pushed me into a CTR experiment. Ranking was not my problem. Position improved from 41.1 to 27.6 over a month and the clicks did not follow, so I went after titles instead.

The first page I picked was a manufacturing cost post sitting at 1,342 impressions, 0 clicks, position 6.2. I retitled it to lead with the 4k to 30k price bands the page already contained. That one I still feel good about.

•

4d ago

Hello from DownUnder! My struggle "Why teams skip user interviews?"

Hi Product Hunt new here.

I am Samrendra. Lately I have been stuck on a problem that's bugged me for years: talking to users is one of the best ways to know what's actually true about a product, and almost nobody does enough of it. Recruiting takes days, running the interviews eats more time, and synthesizing what you learned takes longer than the interviews themselves.

Curious how this community actually handles it. Do you run structured user interviews regularly, or does it get skipped once things get busy? And if it gets skipped, what do you lean on instead to make product decisions?

•

6d ago

Vibecode is instant legacy

I keep coming back to this idea: vibe code is basically instant legacy code.

Not because AI-generated code is necessarily bad, but because it often puts us in a familiar situation: the system works, yet no one fully understands how it works. That makes me wonder whether some of the most useful techniques for vibe coding are actually techniques we already use for legacy systems. For example:

  • Snapshot / approval tests: capture the current output and require explicit approval when it changes.

  • Characterization tests: describe what the system actually does today, regardless of what it was originally intended to do.

  • Golden master tests: run known inputs through the system and compare the results with a trusted baseline.

  • Contract test: protect the boundaries between components, services, APIs, events, and data stores.

  • Differential testing: compare two implementations and detect where their behavior diverges.

  • Test carving: observe a larger execution and extract smaller, focused regression tests from it.

View more