Bug brief builder
Make the first message specific enough to act on.
Generated request
Common fixes
Small scopes with clear handoff.
Responsive CSS, overflow, tap targets, menu behavior, Safari/Chrome mobile checks, and before/after notes.
Broken state, button handlers, template behavior, conditional rendering, build errors, or browser console failures.
Request mapping, missing fields, failed submissions, response handling, auth boundary notes, and safe test payloads.
Find the likely cause, identify risk, propose the smallest patch, and document what should be tested next.
Use this if the bug is not ready to quote yet: collect URL, steps, screenshots, console errors, and expected result.
Safe intake
No private secrets needed up front.
The first pass can use public URLs, screenshots, browser console errors, redacted code, and reproduction steps. Passwords, API keys, customer lists, and payment data should stay out of the first request.
Payment path
Marketplace escrow or direct deposit.
If the work starts on Upwork or Freelancer, payment should stay inside that platform. Direct work can start after a clear scope and payment through paypal.me/AMEZQUITASALINAS or alejandro.amezquita@alumnos.udg.mx.