jp·Málaga

Stack

The tools I use to build AI features and to keep sites running.

AI & Agents

08
  • Claude Code
  • Codex
  • Cursor
  • OpenAI
  • PythonRAG · evals
  • Gemini
  • OpenRoutermodel routing
  • MCP serverstool integrations

Code & Data

07
  • TypeScript / JavaScript
  • React / Next.js
  • HTML / CSSTailwind
  • PHP
  • SQL / MySQLInnoDB tuning
  • Supabaseauth · Postgres · pgvector
  • Git / REST APIs

Hosting & Infrastructure

07
  • Kinstamanaged WordPress
  • Cloudwaysmanaged cloud
  • DigitalOcean
  • AWSS3 · EC2
  • CloudflareDNS · R2 · CDN
  • Vercel
  • DNS / SSL / cachemigrations & debugging

WordPress & CMS

07
  • WordPresscore, multisite, debugging
  • WooCommerce
  • MemberMousemembership platforms
  • ACFcustom fields
  • Gravity Forms
  • Elementor
  • Custom pluginssmall plugins

Support Operations

06
  • Technical account management
  • SaaS implementation
  • Escalations / SLA
  • QA & bug reproduction
  • Docs & playbooks
  • Customer success

How I use AI

How I work with coding agents, and the AI I've already shipped.

01

Agentic coding

I write most code with Claude Code, Codex and Cursor. They read the repo, plan the change, write it and test it, and then I review it. Every repo has written instructions, so the agent follows the same architecture and commands I would.

02

AI in production

I've shipped custom AI chat on WordPress membership sites. It has to fit into the site the client already has, not the other way round.

03

AI systems engineering

What I care about is how a system behaves after launch. That means structured outputs, retrieval with citations, evals, tracing, cost and choosing the right model for each job.