Frontend engineer in Sevilla. I care about component architecture that survives a second team touching it, accessibility that isn't retrofitted, and performance work that holds up once real content lands. Most of my working code sits in private repositories — what's public here is side work, deliberate framework study, and the occasional detour well below the browser.

khanos.github.io · Portfolio · LinkedIn · X · HackerRank

Python · GTK 4 · libadwaita · hwmon

Reads /sys/class/hwmon and cpufreq directly, with no monitoring daemon in between, and tracks per-sensor session minimums and maximums. Picks up the active Omarchy palette live. The design rule is that a value the kernel doesn't expose gets reported as missing rather than inferred, and the test suite runs against a synthetic sysfs tree so it never touches system files. The fan and voltage research behind it is written up in SENSOR_SUPPORT_RESEARCH.md, including why blind sensors-detect probing is a bad idea.

Node.js · Express · MongoDB · Jest

Controllers, services and models in separate layers, behind helmet, CORS, rate limiting and one central error-handling middleware. Endpoints for GitHub commit search, a Mongoose-backed URL shortener, and Gemini text, chat and image prompts. Ten test files cover controllers, services, models, middleware and utils; CI lints and runs them on every push and pull request.

Next.js · TypeScript · tRPC · Drizzle · PostgreSQL · React Three Fiber

An interview challenge where the interesting constraints were the optional ones. tRPC and Drizzle were listed as bonus points, so that's the version I built: a React Three Fiber model viewer, likes and comment CRUD, and types that hold from the Postgres schema through to the component.

Astro · TypeScript · Tailwind

Angular, then Vue, then vanilla JS, then Next.js, now Astro with React islands. Roughly the same content each time — the rewrites were the point. Ships image optimization, HTML compression, a generated sitemap and robots.txt.

HTML · CSS · Vanilla JS

Semantic markup, CSS custom properties, mobile-first, and a typewriter intro that steps aside for prefers-reduced-motion. It's here to keep me honest about doing this without a build step.

TypeScript · JavaScript · Jest

Algorithm practice with ts-jest, a shared ESLint config and a test file per solution, on the theory that a kata you can't re-run isn't practice.

I keep a scratch repo for each technology I want to understand rather than skim: React, Vue, Angular, Next.js, Ionic, Socket.IO, Docker.

They are deliberately rough. It's where a framework gets taken apart before it goes anywhere near production code, and it's most of the reason I don't have strong feelings about which one a team has already picked.

_{epilef is felipe backwards. It's still the first thing people ask.}