UX TRIAGE
UX analysis → Markdown export → AI fixes issues. 30 seconds.
15 followers
UX analysis → Markdown export → AI fixes issues. 30 seconds.
15 followers
Vibe-coding creates UX debt. UX Triage catches what AI misses in 30 seconds. Upload screenshots, get Nielsen Norman heuristic analysis, export to Markdown, paste into your AI agent. From analysis to implementation instantly. 95% cheaper than consultants.
Free Options
Launch Team / Built With
Render: Get up to $100K in startup creditsCloud infrastructure for founders who want to move fast and NOT break things
Promoted
As a Product/UX Designer with 10+ years of experience, I've been deep in vibe-coding with Cursor and Claude this year.
The code generation? Lightning fast. The UX patterns? Often incomplete, inconsistent, or just... wrong.
So I built UX Triage to catch what AI misses—and honestly, I'm shocked at how well it works.
Every analysis finds 8-12 real issues I might have shipped otherwise. It's based on Nielsen Norman's proven heuristics, analyzes designs in 30 seconds, and exports findings as Markdown so you can feed them right back into your AI agent.
Try your first analysis—no signup needed.
I'd love your feedback! What UX issues are you seeing in your AI-generated code?
I think super super interesting. Can see huge utility for a product here that quickly guides development to optimise the UX.
Interesting questions to me are:
is it just Neilsen's framework or will you go beyond this?
could you continuously monitor a whole site?
Interesting the stat on conversion metrics
wonder if you could create fake user agents that actually mimic a cohort of users down the line.
@edward_challis1 Thanks Edward! Really appreciate the thoughtful questions.
is it just Neilsen's framework or will you go beyond this?
Starting with Nielsen Norman exclusively - it's the proven standard and covers 90% of usability issues. I've found trying to do too many frameworks dilutes the focus. That said, WCAG accessibility analysis is on the roadmap.
could you continuously monitor a whole site?
This is exactly where I want to go! Current version is screenshot-based, but I'm adding URL input in the next 2-3 weeks. After that, recurring monitoring (weekly/monthly) makes total sense - track UX improvements over time, catch regressions, etc. Would you find that valuable?
Interesting the stat on conversion metrics
The conversion impact is real but hard to attribute directly. Most of the issues we find (missing loading states, unclear CTAs, poor error handling) have documented conversion impacts in NN research. One user told me fixing 3 critical issues improved their signup flow by 40%, but that's anecdotal. Tracking before/after metrics would be amazing - maybe a future dashboard feature?
wonder if you could create fake user agents that actually mimic a cohort of users down the line
Love this idea. Like synthetic user testing / AI-powered user simulation? That's ambitious but fascinating. Right now we're focused on heuristic evaluation (expert review), but combining it with simulated user behavior would be powerful. Definitely thinking about this for the future.
Really appreciate the forward-thinking questions. This is exactly the kind of feedback I was hoping for!
As a PM watching the designers I work with vibe-code prototypes daily, this is going to be a godsend. So many issues that used to only get caught in internal reviews can be flagged way earlier now. Already sharing with the team!
@lara_silberklang Lara! This is amazing feedback - thank you!
The PM + designer workflow is actually something I hadn't fully considered. I've been so focused on solo developers catching their own issues, but the "flag issues earlier in the design process" use case makes total sense.
Quick question: When you share with your team, how do you typically hand off feedback? Are you exporting the Markdown and pasting into Slack/Notion/Linear, or would you want something more collaborative built in?
(I'm thinking about team features like shared history, comments on analyses, etc. but want to make sure I'm solving real problems, not inventing ones.)
Really appreciate you sharing this with your team - that's the best validation I could ask for! Let me know if you hit any friction or have ideas for making the PM → designer handoff smoother.
@macaya73 Right now it's pretty scattered. Slack for early vibe-coded stuff, Jira tickets once it hits the codebase. Honestly neither feels smooth.
What would actually be great is the ability to annotate and prioritize the feedback right in the tool before it goes to engineers, mark which issues are blockers vs. nice-to-haves before the handoff. That's usually where things get messy for us. Designers and engineers end up getting piecemeal feedback and don't know what actually matters for launch readiness. Plus it brings some objectivity into the conversation, which helps justify prioritization in scope calls.
Great job!
Love the markdown export to feed straight back into your AI agent.
I would like to see this taken further so that I can input more than one screenshot at a time or even documents in various formats such as Figma handover files and requirements documents to better convey the intended UI/UX and context for the tool to make a more informed decision.
@anbu_anthonysamy Stay tuned! Lot's more in the works. Thanks!
Just wanted to note that the examples in the images above are all 100% real, not altered in any way -- this is what the tool puts out.
the agent response is also exactly how it responds to receiving the markdown -- very useful!
I’ve been trying out UX TRIAGE, and it’s genuinely impressive. As someone who’s worked in UX/design teams and seen the “vibe-coding → QA → find surprises late” workflow too many times, this tool feels like the missing guardrail we all needed. Great work @macaya73 !
@danser001 Awesome feedback, thanks Dan, so glad to hear this! I'm using it myself and always amazed what it turns up that I'd missed.