trending
fmerian

2mo ago

Domscribe - Give your AI coding agent eyes on your running frontend

AI coding agents edit your files blind; they can't see your running frontend. Domscribe closes the gap. Code → UI: Query any source location via MCP, get back live DOM, props, and state. No screenshots, no guessing. UI → Code: Click any element, describe what you want in plain English. Domscribe resolves the exact file:line:col and your agent edits it. Build-time stable IDs. React, Vue, Next.js, Nuxt. Vite, Webpack, Turbopack. Any coding agent. MIT licensed. Zero production impact.

How many tokens does your AI agent burn just finding the right file?

I've been tracking this and it's kind of wild.

Every time I ask an agent to change something on the frontend: "fix the padding on that card," "make the CTA button blue"; the actual edit takes maybe 200 tokens. But before that happens, the agent:

  1. Greps the codebase for matching components

  2. Reads 5-10 candidate files to build context

  3. Asks me to confirm which one it should edit

  4. Sometimes still picks the wrong one and has to backtrack