Hello there 👋 I'm Juan Garcia
Full-stack engineer in constant growth — I focus on reliable APIs, validation-first backends, and modern React/Node apps. I like to ship things that are safe to change and easy to run.
Languages & runtime
Frontend
Backend & APIs
Data & auth
Tooling & DevOps
I use AI coding agents as a force multiplier in my daily work — not to replace thinking, but to extend it with clear instructions and guardrails.
| What I do | Why it matters |
|---|---|
| Structure tasks in phases | I break work into numbered steps (e.g. “0a. gather data; 1. produce report”) so the agent has a clear sequence and I can refine one phase without redoing everything. |
| Ask for evidence-based outputs | I prefer results grounded in the codebase (commits, dependencies, lockfiles) so reports, tech stacks, and impact summaries are defensible for reviews and leadership. |
| Inject context via skills and plans | I attach skills (e.g. OS context, conventions) and reference plans or specs so the agent follows my environment and standards instead of guessing. |
| Choose the right tool for the job | I explicitly say when to use the browser, the shell, or the repo (e.g. “use the browser” for live UX analysis) so outputs match the task. |
| Iterate until value is clear | I don’t stop at the first draft: I ask “does this make my contribution clear?” and request refinements (ownership matrix, noise filtering, value-by-project) until the artifact is usable. |
| Reuse one evidence chain | The same data (e.g. commit analysis) feeds contribution reports, tech stack lists, LinkedIn title, and this README — one source of truth, consistent story. |
| Design then implement | For bigger efforts I use the agent to brainstorm and document a plan (with options and trade-offs), then hand off the plan for implementation with todos and tests (including “how do I test in isolation?”). |
I also create skills and rules (e.g. OS-context discovery, browser-priority rules, project conventions) so agents behave consistently across sessions and workspaces. To stay current, I follow AI/Tecs trends mainly on X (Twitter) — I was an early adopter of Ralph loops and similar agentic patterns, and I keep an eye on emerging coding-agent workflows so I can evaluate and then adopt and adapt quickly.
In short: I treat agents as reliable teammates — I specify scope, provide context, ask for evidence and iteration, and reuse outputs across docs and automation so my profile and deliverables stay aligned with what I actually ship.
- Email: jamdeveloper0@gmail.com
- Phone: +55 11 94700-7927
- LinkedIn: Juan Garcia