Interesting concept, and I like the .lol domain. Here's my full walkthrough.
First impression: the landing page
The site is dark mode only, and you can tell it was built with AI. That's fine, but think about what feeling you want to give people, and whether dark mode fits it.
The headline ("Better prompts, proven across models...") could be clearer. The animation is below the fold, and on my phone it's cut in half. Check what's above the fold on mobile.
It's the standard AI layout: small tagline, big headline, smaller explainer text. I've seen it a million times. For every element, ask whether you actually need it. Look at Claude and ChatGPT: no landing page to read, you just start typing.
Sign-up wall
"Get started free" goes straight to sign-up, so you haven't shown me anything yet. AI tools like ChatGPT and Claude don't make you log in first. Google sign-in works well though.
Onboarding order is backwards
Right now it goes: landing page > sign up > Explore > leaderboard > dashboard > library. That's the slowest possible route to the core feature. At TestMyBuild our rule is: how fast can someone use the core feature? Hardly anyone watches the demo video. Put the prompt editor first, ideally on the public page before sign-in. Don't start people on Explore. It's not the main feature.
Test: Rough prompt + Enhance with AI
I wrote my prompt (a cold market study) and clicked Create Prompt. Wrong button: I should have clicked Enhance with AI, but nothing told me that, and it's your core feature. Tell me "You haven't enhanced this yet" or make enhancing the obvious first step.
Once I enhanced it, it worked really well. The red/green diff is very good and smooth. The list of changes is useful, but it reads like terms and conditions and nobody will read it at that length. Keep the content, make it shorter and easier to scan.
Test: Save a new version and restore the old one
I clicked Replace Original and saved V2. Versioning works: it keeps the old version and I can restore it. Good, but I wouldn't make it a headline feature.
Test: Run on 2-3 models side by side
I can pick models and set temperature and max answer length. Fine to have, but I don't think your audience wants that. I come to your platform so I don't have to deal with it. I want a simple way to improve my prompts.
Honestly, I don't see the value of running the models yet. It's basically just running the prompt without my real context. Comparing answers side by side is kind of nice (length etc.), but the value isn't clear. If I'm missing something, the platform should explain it.
Publishing
I published my prompt. Make sure publishing can't expose private data, because people will paste sensitive stuff into prompts.
Here's mine: https://www.intelliprompt.lol/p/26217535-4edd-4e20-8bb0-14623620d428
It came out pretty good. The core feature works, you just don't lead me to it.
Explore, Following and Dashboard
Explore loads slowly, and "Top this week" took a long time to respond. "Following" says "Nothing from people you follow yet." OK, then suggest people to follow.
The Dashboard with "New prompt" is where I should start. Put "New prompt" in the header on every page, since it's the main action. Dashboard isn't even in the top navigation right now. My Library and Favorite Prompts are good. A blog is nice to have, though I'm not sure how much people will use it.
The feature that would make this useful for me
Clarifying questions. Right now "enhance" is very general. A prompt can go a thousand directions, so you get a different result every time. If it asked me a few quick questions ("What's the goal? What's the outcome? What does this refer to?"), it could write a much better prompt and save me tokens in my other tools.
Don't make it a long form, because people hate forms. Use a few quick selectable options, e.g. Goal: create an artifact / just give a response / write code. My prompt never said I wanted an artifact, but I was hoping for one. If I could pick that, you'd build it into the prompt and I'd get the right output. That's what would make me come back.
Overall
The core feature (enhance + diff) is genuinely good, and I think our audience will like it. The problem is getting people to it. Fix the order: editor first, enhance as the obvious first step, everything else later.

