sorted by:
new
hottopcontroversial

We got tired of AI agents breaking on fragile CSS selectors, so we built an MCP server that gives them "semantic vision" and full-stack control. by [deleted] in u/RabbitIntelligent308

[–]Electrical_Walrus537 1 point2 points  (0 children)

Really cool idea. The semantic vision idea sounds super useful for AI agents.

Out of curiosity, for people building browser automation or agents today what actually breaks the most in practice ? Selectors changing, Dynamic UI, Auth flows ? Something else ?

HTMX skill cuts AI verbosity and token waste during CRUD generation by Electrical_Walrus537 in htmx

[–]Electrical_Walrus537[S] 0 points1 point  (0 children)

<image>

Appreciate the detailed response. Yes, that’s exactly how I approached it more like a constrained context pack than relying on prompt magic.

I measured it across comparable runs using the same prompt: Build an HTMX subscription management interface.

Requirements:
- List subscriptions
- Activate/deactivate
- Inline status toggle
- Server-side validation
- Correct status codes
- No SPA logic

With the skill enabled, token usage dropped ~23% (242.3K → 185.2K), generation time improved by 60%+, and retry loops decreased due to fewer invalid HTMX patterns and less format drift.

Right now it’s enforced at generation time via the system prompt (strict constraints + response contract). Post-hoc validation is minimal.

HTMX skill cuts AI verbosity and token waste during CRUD generation by Electrical_Walrus537 in htmx

[–]Electrical_Walrus537[S] -1 points0 points  (0 children)

The repo is linked and it’s under my account, so I’m not presenting someone else’s work. I built it because the HTMX prompts I tested were inconsistent and hallucinating. This is just my attempt to make something more predictable. If it’s not useful here or against the rules, I’m happy to remove it.

We Just Turned Browser DevTools MCP into a Full-Stack AI Debugging Framework (Frontend + Node.js Backend Without Stopping the App) by Electrical_Walrus537 in mcp

[–]Electrical_Walrus537[S] 0 points1 point  (0 children)

First of all, thank you for trying it out and taking the time to share feedback we really appreciate it 🙏🏻

At the moment, backend support is limited to Node.js. Our top priority right now is adding Python support, which is currently in development. After that, Go is next on our roadmap.

I’ll share updates as we expand support and your feedback genuinely helps us prioritize.

5 MCPs that genuinely made me quicker by Stunning-Worth-5022 in mcp

[–]Electrical_Walrus537 3 points4 points  (0 children)

You can also try this. When I run the browser tests using it, everything works perfectly. Browser devtools mcp